Search first
Find redirects, destinations, and application actions from one keyboard- and touch-friendly workspace.
A calm, focused place to create, find, change, and review redirects.
Focused by design
Beacon concentrates on management workflows and leaves persistence and execution with the systems that own them.
Find redirects, destinations, and application actions from one keyboard- and touch-friendly workspace.
Durable records remain tenant-scoped in Drift while Beacon keeps only rebuildable read projections.
Beacon manages definitions and events without pretending to own redirect traffic or cache policy.
Why it exists
Redirects need deliberate editing, reusable destinations, lifecycle controls, and enough operational history to understand changes. The management application does not need to become the traffic engine or the system of record.
Guides & reference
Learn, operate, look up, or understand Beacon without mixing those jobs together.
Connect Drift, run Beacon locally, and create a first redirect.
Open tutorialDeploy the complete stack and operate its credentials and projections.
Open how-toUnderstand authority, caching, authentication, and disposable read models.
Open explanationCheck management routes, Compactor contracts, and environment variables.
Open referenceWhat it fits
Manage branded paths, reuse destinations deliberately, and preserve explicit lifecycle choices.
Export a redirect as a QR code without introducing a second source of redirect truth.
Review management changes and best-effort redirect events as operational history, not billing data.