Deterministic redirects
Normalize each public URL once, resolve an exact definition, and return a deliberate redirect response.
Small redirect infrastructure
Compactor
Make the redirect. Keep the machinery small.
Compactor resolves configured public URLs, returns precise redirects, and emits bounded request events—without becoming a link-management product.
Focused by design
One request-time responsibility
Compactor owns redirect resolution and a bounded account of the completed request. Everything else stays with the systems built for it.
Adapters stay independent
Redirect definitions and request events cross separate ports, keeping configuration and analysis replaceable.
Privacy has bounds
Capture only allowlisted request metadata, truncate it predictably, and keep credentials out of events.
Why it exists
Infrastructure, not a link-management product
No dashboard, campaigns, accounts, mutation API, or analytics engine. Redirect definitions come from configuration; events go to an external collector. Compactor keeps the boundary visible and the runtime ordinary.
Guides & reference
Choose your path
Learn, do, understand, or look up without mixing those jobs together.
Tutorial
Run Compactor locally and make your first redirect.
Open tutorialHow-to
Deploy, configure, operate, and publish Compactor.
Open how-toExplanation
Understand the adapter model and deliberately narrow product boundary.
Open explanationReference
Look up configuration, source, event, and URL contracts.
Open referenceWhere it fits
Stable URLs at the edge of change
Retired routes
Move durable public URLs without carrying an application framework into the redirect tier.
Service migrations
Route old hosts and paths to their new homes with exact, reviewable definitions.
Campaign handoffs
Forward stable entry points while leaving campaign management and analysis in their own systems.