Using a token

Tokens authorize reusable public names. For the hosted service, clients connect to https://edge.routeup.dev and receive a namespace under routeup.dev.

You only need a token for reusable named public URLs such as https://example-app.your-name.routeup.dev. Local-only routes do not need one. The public address can be claimed again between runs, but it is reachable only while a tunnel is connected.

Request a hosted token

Hosted tokens are currently issued manually. Email tokens@routeup.dev with:

• the namespace you would like, such as your-name.routeup.dev, and
• a short note about what you are building.

The token will be returned privately. Store it in a password manager: the server keeps only its hash and cannot show the secret again.

Save a server and token

terminal

routeup setup --server https://edge.routeup.dev --token sk_routeup_xxx

After that, routeup serve --expose can use the saved values.

On an interactive re-run, setup represents the saved token with a masked value. Press Enter to keep it, or clear credentials explicitly:

terminal

routeup setup --token none   # keep the server, clear only the token
routeup setup --server none  # clear both

Use environment variables instead

terminal

export ROUTEUP_SERVER=https://edge.routeup.dev
export ROUTEUP_TOKEN=sk_routeup_xxx

Expose with the token

terminal

routeup serve example-app --port 8080 --expose

If the token allows *.mukul.routeup.dev, the server can grant:

https://example-app.mukul.routeup.dev

The token secret is not recoverable from the server after it is created.

Without a token

For token-less temporary URLs, see Exposing publicly.