routeup docs
routeup gives local services stable HTTPS names and can expose those same routes publicly when needed.
Local use is the default: run routeup setup once, then serve a local app at a trusted https://<name>.localhost URL without DNS, accounts, or network access. Public exposure is available through a configured routeup server when an outside service needs to reach your machine.
Where to start
Section titled “Where to start”- New here? Start with Install and Your first route.
- Using a coding agent? Install the Routeup Agent Skill.
- Need to see what reached your app? Observe and debug requests.
- Building a specific workflow? Start with the Recipes.
- Want to understand the model? Read Concepts › Routes.
- Want one live view? Open the terminal dashboard.
- Looking for a specific command? Jump to the CLI Reference.
- Running your own server? See Self-Hosting.
- Common questions? Check the FAQ.
What these docs cover
Section titled “What these docs cover”These docs cover local HTTPS, public route claims, streaming/WebSockets/SSE, path routing, process running, request logs and inspection, the read-only terminal dashboard, automation, and self-hosting.