⇄ Rediray
Redirect management for domain migrations. Attach a domain to edge workers, publish exact and prefix rules from one control plane, and see every hit as it happens — so a site move doesn't quietly bleed traffic and SEO.
the problem
Migrations lose links in the dark
Redirects live in ten different config files nobody owns.
A domain move scatters redirect rules across nginx configs, CDN dashboards and someone's memory. Rediray puts every rule in one place, running at the edge, with a live view of what's actually being hit — and what's 404ing.
rules ● published edge: 12 pops
/blog/* → new.example.com/articles/* 301
/pricing → new.example.com/plans 301
/old-faq → no rule — 404 ×14
› 2,481 hits today · 1 gap flagged
features
What it does
One control plane for every redirect you own.
// edge
Runs at the edge
Attach a domain and rules deploy to edge workers worldwide — fast redirects with no origin server to keep alive.
// rules
Exact & prefix rules
Map single paths or whole trees with wildcards and capture groups. 301, 302 or 307 — your choice, per rule.
// import
Bulk import
Paste a CSV or an existing rewrite map and Rediray turns it into managed rules — no hand-migration.
// analytics
Hit analytics
See every redirect that fires, top paths, and — crucially — the 404 gaps where you're losing visitors.
// preview
Test before publish
Dry-run any URL against your ruleset to see where it lands, before it goes live for real traffic.
// audit
Versioned & audited
Every publish is versioned. Roll back a bad ruleset instantly, and see who changed what and when.
spec
At a glance
execution
Edge workers · global PoPs · sub-10ms redirects
rule types
Exact · prefix / wildcard · regex capture 301 · 302 · 307
import
CSV · nginx / Apache rewrite maps
observability
Per-rule hit counts · 404 gap detection
operated by
OPERACK — same team, same on-call
Move the domain. Keep the traffic.
Rediray is in public beta. Attach a domain, import your rules, and watch every redirect from one place.