Redirections

What is Redirections?

Redirections is an HTTP redirect management platform for creating and deploying redirect rules at scale. You manage rules in a web dashboard, deploy them to a global edge network, and query them through a simple HTTP API.

The platform is designed for redirect lookup performance with edge-based resolution and consistently low latency. It also supports exporting redirect configurations to common server and proxy formats so you can keep infrastructure deployments in sync.

Key Features

• Sub-50ms edge redirect lookups (global): Redirects are resolved via an edge API with global lookup performance targeted to under 50ms.
• Deployment across 300+ edge locations / PoPs: Rules can be deployed broadly so redirect resolution is available close to users and infrastructure.
• Edge API with full CRUD and batch operations: Manage redirect rules programmatically using a plain HTTP API, including creating, updating, deleting, and handling rules in bulk.
• Export redirect configurations to multiple platforms: Generate production-ready configurations for CSV, Nginx (including map-file variants), and HAProxy (including map-file variants).
• Redirect chain detection and loop reporting: Automatically scan the rule set to find multi-hop redirect chains and circular loops, and report the hop path and hop count so chains can be collapsed.
• Team access controls and auditing: Provide role-based access, audit trails, and project isolation for teams managing rules across environments.

How to Use Redirections

1. Start with the free tier: Create a project and add redirect rules using the web dashboard.
2. Deploy rules to the edge: Publish your rule set so the edge network can resolve redirects for incoming requests.
3. Query via the Edge API: Call the provided HTTP GET endpoint from your infrastructure to perform redirect lookups; the website notes you can integrate without an SDK using a standard HTTP client.
4. Export configurations when needed: If you need server-specific rule files, export the rules to CSV, Nginx, or HAProxy formats (including map-file variants).
5. Review redirect chains: Use the chain detection capability to identify multi-hop chains and loops, then simplify rules to reduce unnecessary hops.

Use Cases

• Centralized redirect management across services: Manage redirect rules in one place and deploy them to edge locations while querying via API from multiple infrastructure components.
• Keeping infrastructure in sync: Export the same redirect rule set to Nginx or HAProxy configuration outputs so different servers stay aligned with a single source of truth.
• Migration from older URLs: Create redirects from legacy paths (e.g., old blog post URLs) to updated destinations while validating redirect behavior through chain detection.
• Programmatic rule updates: Use the API’s CRUD and batch operations to update large rule sets without manually editing dashboard entries.
• Enterprise team governance: Use role-based access and audit trails to control who can modify rules and to track changes across projects.

FAQ

What is the API interface for redirect lookups? The site describes the Edge API as a plain HTTP GET endpoint for sub-50ms global lookups, intended to be called from infrastructure without an SDK.

How fast are lookups? The website states that edge API lookups resolve in under 50 milliseconds worldwide, with edge workers described as always warm and having zero cold starts.

Can I export redirect rules to server configurations? Yes. Redirections supports exporting redirect configurations to CSV, Nginx (including map-file variants), and HAProxy (including map-file variants).

Does Redirections detect redirect chains? Yes. It includes a chain detection engine that scans for multi-hop chains and circular loops, reporting the hop path and hop count.

Is there a free plan? Yes. The free tier is described as including 1,000 redirect rules, 1 project, 10K API requests per month, and 1 API key (no credit card required).

Alternatives

• Self-hosted redirect handling (e.g., Nginx rewrite rules or map-based setups): Useful if you want to manage redirects entirely within your own infrastructure, but configuration management and consistency across fleets can be more manual.
• DNS-based redirects: Can handle some redirection use cases at the resolver level, but it typically won’t provide the same rule management workflow and API-driven lookup behavior described by Redirections.
• Application-level routing (framework routing rules): Routing redirects inside an application gives code-level control, but it usually requires deploying to each application instance and can add latency compared to edge resolution.
• General edge routing/CDN worker scripting: Implementing redirect logic directly in an edge environment may work for smaller rule sets, but centralized CRUD, exports to server/proxy formats, and chain detection may require additional tooling.