# routeup docs

> Stable HTTPS routes for local services. Public when you need it.

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

- New here? Start with [Install](/docs/getting-started/install) and [Your first route](/docs/getting-started/first-route).
- Using a coding agent? Install the [Routeup Agent Skill](/docs/getting-started/agent-skill).
- Need to see what reached your app? [Observe and debug requests](/docs/getting-started/observe-and-debug).
- Building a specific workflow? Start with the [Recipes](/docs/recipes/webhook-development).
- Want to understand the model? Read [Concepts › Routes](/docs/concepts/routes).
- Want one live view? Open the [terminal dashboard](/docs/cli-reference/dashboard).
- Looking for a specific command? Jump to the [CLI Reference](/docs/cli-reference/routeup).
- Running your own server? See [Self-Hosting](/docs/self-hosting/running-the-server).
- Common questions? Check the [FAQ](/docs/faq).

## 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.