Rediray redirect management software

Redirect management software for domain migrations, domain forwarding, and runtime routing.

Manage redirects, attach domains to worker infrastructure, validate DNS, publish exact and prefix rules, and inspect redirect hits from a single control plane built for operations teams.

Join beta Sign in

Workspace scoped

multi-tenant ownership

Zone attached

DNS points to workers

Exact + prefix

deterministic matching

Hit visibility

dashboard and API analytics

Control plane preview

Deployment preview

Ready to configure

Ownership

Tenant-aware

Ingress

Zone-backed

Runtime

Rule-driven

Activation flow

Create your first domain

Every domain starts inside a workspace project before runtime routing is enabled.

Step 1

Select deployment zones

Rediray maps those zones to active workers and generates the DNS records each hostname must use.

Step 2

Validate DNS, then publish rules

Runtime resolution stays gated until the hostname resolves to Rediray worker infrastructure.

Step 3

Activation states

Draft Added to a project

Pending DNS Waiting for A records

Active Eligible for runtime

Failed DNS mismatch detected

/_r/<hostname>/<path> Runtime unlocks after DNS validation Workspace scoped from day one

Start with tenant ownership

Workspaces and projects organize every domain and redirect rule.

Attach domains to workers

Assign zones and generate the worker IPs a domain must resolve to.

Publish redirect rules

Configure exact or prefix behavior, status codes, and priorities.

Inspect runtime traffic

Use hit analytics to see which domains and rules carry the load.

Use cases

Built for redirect management, domain forwarding, and migration cutovers.

Rediray is optimized for the operational jobs teams actually search for: redirect management software, domain migration redirects, and DNS-attached routing across worker regions.

Domain migrations

Cut over domains without losing traffic

Coordinate redirect rules, DNS validation, and worker assignments before you flip traffic from legacy domains to the new destination.

migration redirects launch cutovers

Domain forwarding

Replace ad hoc forwarding setups

Move domain forwarding out of registrar panels and scattered server configs into a product with auditability and analytics.

domain forwarding redirect governance

Routing operations

Run redirect infrastructure from one dashboard

Control exact and prefix redirects, attach domains to regions, and inspect runtime behavior without dropping to manual edge config.

edge routing regional workers

Platform

Redirect management infrastructure with domain attachment and rule operations built in.

The product is built around the operational model that matters for SEO migrations and redirect programs: ownership, domain onboarding, rule resolution, and analytics.

Workspaces

Tenant-aware ownership

Membership-based scoping keeps products, environments, and clients separated without splitting the product into disconnected tools.

workspace-scoped access default project bootstrap

Domain to worker attachment illustration

Domains

Zone-backed attachment

Domains are assigned to active zones and worker nodes before runtime resolution is even considered.

zone selection worker assignments

Rules

Deterministic redirect engine

Exact and prefix rules support 301, 302, 307, and 308 responses, optional query preservation, and priority-based tie breaking.

exact before prefix priority tie-breaks

Analytics

Runtime hit visibility

Matched traffic captures rule, domain, path, query string, referer, user agent, and IP details for reporting and debugging.

hit logging included dashboard + API

Built for operations

Designed for teams shipping migrations, cleanups, and redirect programs at scale.

The product is not just a rule table. It coordinates tenant ownership, DNS validation, runtime matching, cache invalidation, and hit tracking in one system.

DNS lifecycle built in

Domains move through draft, pending DNS, validating, active, and failed states based on resolver results.

Runtime changes reflect immediately

Domain and rule updates clear cache so published redirect behavior is visible without manual cleanup.

Traffic becomes reportable

Matched requests create hit records that feed analytics, recent activity, top domains, and top rules.

Domain lifecycle

DraftCreated

Pending DNSPoint records

ValidatingRun checks

ActiveRuntime enabled

FailedFix DNS

Resolution guarantees

Only active domains and active rules are eligible for matching.

Exact matches win before prefix matches.

The longest matching prefix wins when multiple prefixes apply.

Priority and id ordering break ties deterministically.

Runtime

Resolve redirects by API or browser path.

The runtime can answer directly through an API or through the public redirect route.

POST /api/runtime/resolve
{
  "hostname": "docs.example.com",
  "path": "/blog/legacy-post",
  "query_string": "utm_source=launch"
}

{
  "matched": true,
  "target_url": "https://www.example.com/journal/legacy-post?utm_source=launch",
  "status_code": 301,
  "rule_id": 3
}

/_r/<hostname>/<path> POST /api/runtime/resolve Query preserve optional

How it works

From workspace creation to matched hit.

Create a workspace and project

This defines the ownership boundary for every domain, rule, and hit query in the app.

Attach a domain to zones

The backend selects active workers in each zone and generates the DNS values the hostname must use.

Validate DNS

Resolver checks determine whether the domain is pending, active, validating, or failed.

Publish redirect rules

Rules define exact or prefix behavior, target URLs, status codes, and optional query preservation.

Resolve traffic and record hits

Matched requests produce analytics records that surface recent activity and top-performing routes.

API

Automatable from day one.

The app already exposes the core surfaces needed to manage tenants, domains, rules, and runtime insight programmatically.

GET|POST

/api/workspaces/

Create and list the tenant roots of the system.

GET|POST

/api/projects/

Organize redirect programs under each workspace.

GET|POST

/api/domains/

Create domains, inspect assignments, and read expected DNS records.

POST

/api/domains/<id>/validate-dns/

Re-run DNS checks and update domain plus assignment states.

GET|POST

/api/rules/

Manage redirect targets, priorities, match types, and activity state.

GET

/api/stats/overview

Return scoped counts, top rules, and recent hits for signed-in users.

Next step

Get access now, while the product is still free in alpha and beta.

We will announce pricing when Rediray reaches v1. A generous free plan will remain part of the product long term.

Join beta See pricing

Pricing

Free during alpha release.

Alpha release

Free

Full product access while we refine the platform and learn from real traffic workflows.

v1 Pricing

Later

We will communicate paid plans when Rediray reaches v1 and the packaging is stable enough to publish.

Always free

Guaranteed

A generous free plan will remain part of the product even after paid plans are introduced.

Join beta