User documentation
  1. What is redirection.io?
  2. Starter's guide
  3. What are organizations and projects?
  4. Invite new collaborators
  5. User account and preferences
  6. Using traffic logs
  7. Create a rule
  8. Triggers and markers reference
  9. Actions reference
  10. How to bulk-import or export redirection rules?
  11. Managing instances
  12. Project notifications
  13. Project segmentation
  14. How much does it cost?
  15. Can I use redirection.io for free?
  16. About us

Developer documentation
  1. TL;DR; Fast track
  2. Available integrations
  3. nginx module
  4. Apache module
  5. Upsun integration
  6. Clever Cloud integration
  7. Cloudflare Workers integration
  8. Fastly Compute@Edge integration
  9. Vercel Middleware Integration
  10. Using redirection.io with Docker
  11. How fast is it?
  12. Public API

Agent documentation
  1. Installing the agent
  2. Upgrading the agent
  3. Agent command line options
  4. The agent as a reverse proxy
  5. Agent configuration reference
  6. Minimal configuration
  7. Listening for requests
  8. Forwarding requests to the backend
  9. Virtualhosts
  10. Trusted proxies
  11. GeoIP database
  12. Response compression
  13. Performance tweaks
  14. Access logs
  15. Persisting data in a s3 bucket
  16. Monitoring the agent
  17. Using the agent behind a HTTPS proxy
  18. Agent configuration examples

Managed instances
  1. What are managed instances?
  2. Add a domain to your project
  3. Managed instances limits and quota
  4. Frequently asked questions

Crawler
  1. What is the redirection.io crawler?
  2. Start a crawl
  3. Schedule a crawl
  4. Analyzing the results of a crawl
  5. The crawls list
  6. Crawl credits and pricing
  7. Crawl Errors
  8. Crawler metrics reference
  9. Crawler columns reference

Knowledge base
  1. Create your first redirections
  2. redirection.io rules cookbook
  3. Setting up a redirection server on Azure Cloud
  4. Structured data and Rich Snippets
  5. What is a URL redirection?
  6. Why use URL redirections and how to setup

Legacy versions
  1. Agent 1.x configuration reference
  2. Agent 2.x configuration reference
  3. Legacy integrations
  4. Legacy Cloudflare Workers integration

Changelogs
  1. redirectionio-agent
  2. libnginx-mod-redirectionio
  3. libapache2-mod-redirectionio

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
Can't find your answer?