Clever Cloud integration - Developer documentation | Documentation

Clever Cloud integration

Clever Cloud is a sovereign PaaS (Platform as a Service) that automates application deployment, scaling, and infrastructure management. By integrating redirection.io into your Clever Cloud environment, you can manage complex HTTP redirections, SEO optimizations, and traffic logs without requiring constant developer intervention for every URL change.

How it works: Request Flow

The integration relies on Request Flow, Clever Cloud's automatic middleware chaining mechanism. Request Flow automatically configures reverse proxies between the public port (8080) and your application, managing all port allocations transparently.

Request Flow handles the internal networking chain for you:

One middleware: redirection.io listens on 8080 and forwards traffic to your application on port 9000
Multiple middleware: If you use both Varnish and redirection.io, Request Flow chains them (e.g., port 8080 → 8081 → 9000)

In runtimes where Clever Cloud manages port configuration (such as FrankenPHP, Java, PHP, or Static), this process is entirely transparent.

Setup instructions

To link any Clever Cloud application to a redirection.io project, you only need to configure one environment variable, the CC_REDIRECTIONIO_PROJECT_KEY, with your redirection.io project key. This key can be found in the "instances" screen of the manager (click on the "Setup on your infrastructure" button).

Add the following variable to your Clever Cloud application settings:

Name	Description	Default
`CC_REDIRECTIONIO_PROJECT_KEY`	Required. Your unique project key, copied from the manager	None
`CC_REDIRECTIONIO_INSTANCE_NAME`	Optional. The name for this instance as it appears in your logs and in the manager	None

Advanced configuration

Application listening port

If your runtime allows manual port control (like Node.js, Go, or Python with uv), ensure your application listens on port 9000 once the redirection.io project key is set.

Customizing the middleware order

By default, if multiple services are active, the order is Otoroshi Challenge first, then Varnish, then redirection.io. You can explicitly control this sequence using the CC_REQUEST_FLOW variable.

For example, to expose redirection.io first, before Varnish:

CC_REQUEST_FLOW="redirectionio,varnish"

In this configuration, redirection.io listens on port 8080 and forwards to Varnish on port 8081.

This page has been updated on Apr 14, 2026.