Skip to content

Tokens and allow patterns

Tokens authorize reusable public route claims on a routeup server. They are created by the server operator and handed to clients out-of-band. A token lets a client request the same address again, but the address serves traffic only while a tunnel is connected.

For the hosted routeup.dev server, request a token by email. Self-hosted operators create tokens with the routeup token commands.

Token secrets use the sk_routeup_ prefix and are shown once when created. The server stores a hash, not the plaintext secret.

An allow pattern grants exactly one public label under a suffix:

*.routeup.dev
*.alice.routeup.dev

The first pattern matches example-app.routeup.dev; the second matches example-app.alice.routeup.dev. A * grants exactly one label, not the suffix itself or a deeper hostname.

Pass the dotted route api.example-app normally. routeup automatically requests the public label api-example-app when exposing it.