Available integrations

Of course, our goal is to make redirection.io usable with most of the platforms out there. There are currently several available integrations which are actively maintained by the redirection.io team:

Integration Pros Cons
Apache module
  • Performance
  • Official packages available for several distributions
  • Open Source
  • Requires an Apache2 server
  • Ability to install a native module
nginx module
  • Performance
  • Official packages available for several distributions
  • Open Source
  • Requires a nginx server
  • Ability to install a native module
Standalone reverse proxy
  • Performance
  • Official packages available
  • Single binary, easier to integrate in many environments
  • Ability to install a server software
Clouflare workers
  • Easy to install
  • No technical skills required
  • Requires the use of Cloudflare
Fastly Compte@Edge
  • Easy to install
  • No technical skills required
  • Requires the use of Fastly

nginx integration

This integration is perfectly suited for websites that run the nginx Web server. It provides a native nginx module, developed in C, that listens to all the HTTP requests and applies rules on the fly.

an incoming request is catched by redirection.io's nginx module

You may choose this integration if:

  • you want to use your existing nginx installation / VirtualHost to proxify all the requests, and simply add a native module to nginx to perform redirections;
  • you are able to load a nginx native module on your hosting platform.

Read more about the redirection.io nginx integration on its dedicated documentation page.

Apache integration

Very similar to the nginx integration, we propose a native Apache module, also developed in C, that allows to apply redirection.io rules at the server level, using an existing Apache VistualHost.

In this layout, the native redirection.io Apache module is loaded by Apache at startup time, and can be configured in VirtualHosts to listen all the requests and apply rules on the fly.

an incoming request is catched by redirection.io's Apache module

You may choose this integration if:

  • you want to use your existing Apache VirtualHosts to proxify all the requests, and simply add a native module to Apache to perform redirections;
  • you are able to load a Apache native module on your hosting platform.

Read more about the redirection.io Apache integration on its dedicated documentation page.

Standalone reverse proxy

In many hosting layouts, a Web server like nginx or Apache is not available. It can either be because you want to install redirection.io in front of caching reverse proxies like Varnish or HAProxy, or because your web application server does not require a Web server to be installed (node environments, for example).

In this case, you can still use redirection.io without the need for installing Apache or nginx. Indeed, the redirection.io agent software itself can be executed as a (very performant) reverse proxy, which can scale along with your infrastructure (think scalability):

Using the redirection.io agent as a reverse proxy

This integration mode can be preferred if:

  • you do not have a Web server available, like for example nginx or Apache;
  • you are not able to add custom dynamic modules to your Web server;
  • you want to be easily able to scale your infrastructure.

Installing the redirection.io agent as a reverse proxy is covered in the agent configuration reference.

Cloudflare Workers

Using the Cloudflare workers is an easy and straightforward way to integrate redirection.io in your website.

Using redirection.io with Cloudflare workers

This solution can be chosen if:

  • your website uses Cloudflare. In particular, running workers requires that your DNS is hosted by Cloudflare;
  • you have an access to the Cloudflare management console;
  • you do not want or are not able to install software on your hosting platform.

You may read more about the redirection.io Cloudflare integration on its dedicated doc page.

Fastly Workers

All Fastly customers can benefit of redirection.io by using Compute@Edge, the serverless edge computing solution provided by Fastly.

This solution can be chosen if:

  • your website uses Fastly, or you intend to use Fastly;
  • you have an access to the Fastly management console;
  • you do not want or are not able to install software on your hosting platform.

You may read more about our Fastly integration.

This page has been updated on March 4th, 2022.
Can't find your answer?