These are the features actively planned for Route Entry - not vaporware, not a marketing slide. Each item below represents a real direction with a clear rationale. No ETAs, because shipping half-baked beats shipping on schedule.
Serve redirect links from a domain you control.
Instead of routing visitors through domains provided by routeentry.com, you'll be able to attach a custom domain to your route entries. Visitors see your brand in the address bar. Full HTTPS, automatic certificate provisioning, and zero configuration on the DNS side beyond a single CNAME record.
Attach several domains to a single redirect pipeline.
Route a single gated link through multiple vanity domains simultaneously - useful for A/B testing domain names, running regional variants from one configuration, or migrating a domain without rebuilding your gate setup. All domains share the same gate pipeline, analytics, and management dashboard.
Point several URLs at the same gate pipeline and destination.
A single route entry can have more than one URL behind it - different domains, different slugs, same pipeline. Every path hits the same gates, collects analytics into the same session log, and lands visitors at the same destination. Useful for running parallel vanity links without duplicating your configuration, migrating an old URL alongside a new one, or testing which slug performs better under identical conditions.
Group and manage all your routes from one place.
Right now, each route entry is a standalone artifact managed with a token. Accounts will let you view all your routes in one dashboard, rotate tokens centrally, and set default configurations for new route entries. It's opt-in - the no-account flow stays. No mandatory sign-up.
Control exactly how long visitor data is kept.
Today, session data lives for 30 days with a hard cap of 10,000 sessions per route. Configurable retention will let you shorten the window for privacy-sensitive deployments or extend it when you need longer historical views. Route-level overrides for both the day limit and session cap.
Manage routes and query analytics programmatically.
A fully documented REST API for creating route entries, updating gate configuration, querying visitor sessions, and reading analytics - all the operations currently available only through the UI. Token-authenticated, JSON responses, and OpenAPI spec included.
Timelines get published and then missed. We don't do that. Features ship when they're right, not when a date arrives. The roadmap is a direction, not a contract.
Everything on this list has a clear, concrete use case. If a feature would make Route Entry harder to understand or slower to use, it doesn't ship - even if it would look good on a pricing page.
Existing routes, management tokens, and gate configurations will continue working as new features land. Backward compatibility is a constraint we take seriously.
If you have a use case that isn't covered by what's listed here - or if you want to push a planned feature higher up the list - reach out. Feature requests that come with a concrete use case get taken seriously.
