What is RouteSeam?

RouteSeam is managed infrastructure for domain redirects. You point a domain at RouteSeam with one DNS record, and RouteSeam handles HTTPS certificates and redirects traffic to wherever you say.

The problem

Redirecting a domain sounds trivial until you do it properly. A real redirect setup means running a web server that listens on ports 80 and 443, obtaining and renewing TLS certificates, writing nginx or Apache configuration, keeping the machine patched, and doing it again for every domain you own. Most teams that rebrand or consolidate domains end up babysitting a tiny VPS whose entire job is to answer with a 301.

That server is pure liability. It has no application logic, but it can still fail, get hacked, or let a certificate expire — and when it does, your old domain silently stops working.

RouteSeam removes all of it. There is no server to run, no nginx config to write, and no certificate to renew. You add a domain, add one DNS record, and RouteSeam does the rest.

How it works

The flow is deliberately short:

1. Add your source domain and destination URL.
2. RouteSeam shows you exactly one DNS record to create.
3. You add it at your DNS provider and click Check DNS.
4. RouteSeam verifies the record, provisions a TLS certificate automatically, and activates the redirect.

From then on, every request to your domain is answered over HTTPS with the redirect status code you chose — 301, 302, 307, or 308 — with path and query-string preservation available per domain. Certificates issue and renew automatically via Let’s Encrypt, so there is nothing to maintain after setup.

HTTPS is mandatory. RouteSeam never serves an HTTP-only redirect.

Who it’s for

Developers and founders. You renamed your product and want oldstartup.com to permanently redirect to newstartup.com. You don’t want to deploy and maintain a server just to return a redirect. RouteSeam takes you from “I own this domain” to “it securely redirects” in about five minutes.

Agencies. You manage 50–500 client domains and need one place to see and control all of their redirects, with clear status indicators you can screenshot for a client. No per-client servers, no per-client certificate renewals.

SaaS companies. Rebrands, acquisitions, and product consolidations all produce domains that must keep redirecting reliably for years. RouteSeam gives you permanent, monitored HTTPS redirects without adding infrastructure to your on-call rotation.

What you need before starting

• A domain you own and want to redirect from (the source).
• Access to its DNS provider — the registrar or DNS host where you can add records.
• A destination URL — the full https:// address traffic should be sent to.

That’s the entire list. You do not need a server, hosting account, or certificate.

Where to go next

• Follow the quickstart to get your first redirect live.
• Read DNS setup if you’re unsure which record to create for apex domains vs. subdomains.
• See redirect types for help choosing between 301, 302, 307, and 308.
• Learn how a domain moves through its lifecycle from DNS Pending to Active.