Roadmap

RouteSeam’s long-term direction is programmable traffic routing: every request to a connected domain is evaluated against routing rules before it reaches a destination. Managed HTTPS redirects are the shipped foundation; this page describes what comes after.

Caution

Everything on this page is planned or under consideration — none of it is available today. Shipped functionality is documented in the rest of these docs. Do not build against anything listed here.

Branded short links

Short links on your own domain, treated as just another routing rule:

go.company.com/docs → https://docs.company.com

Planned capabilities include custom and random slugs, vanity URLs, expiring links, password-protected links, and link folders. Short links would sit alongside domain redirects in the same dashboard and API.

Smart routing

Rules that pick a destination from request attributes instead of redirecting every request the same way. Under consideration:

• Country — send NG visitors to company.ng, US visitors to us.company.com.
• Device — route mobile, desktop, and tablet traffic to different destinations.
• Browser — branch on Safari, Chrome, Firefox, and others.
• Language, time, and query parameters — for example, routing utm_campaign=summer traffic to a campaign landing page.

Smart routing builds on the same edge that already evaluates redirects today; see Architecture.

QR codes

Generate a QR code for any route in PNG, SVG, or EPS. Because the QR code points at a RouteSeam-managed route, it keeps working when you change the destination — update the route, not the printed code.

Traffic splitting

Send a percentage of traffic to one destination and the rest to another. This is the foundation for A/B testing, blue/green deployments, canary releases, and maintenance modes — all driven by routing rules rather than application code. Traffic splitting is the furthest-out item on this page and the most likely to change shape before it ships.

SDKs and Terraform provider

Official SDKs for Go, Ruby, JavaScript/TypeScript, Python, and PHP, plus a Terraform provider for managing domains and routes as code. Both will be generated from the OpenAPI spec rather than hand-written — openapi.yaml is the declared source of truth for the API, so generated clients can never drift from what the API actually does. See API conventions for how the spec is maintained today.

Feedback

Priorities on this page are not fixed. If one of these capabilities would unblock you, say so through the support channel on your plan — demand directly shapes ordering. For current plan limits while you wait, see Plans and billing.