Reserved Subdomains
Keep a stable address for previews, webhooks, and callbacks.
A reserved subdomain belongs to your organization and can be reused across tunnel sessions. Reservation keeps an address available to you; it does not keep your application running.
Reserve the name
Select your organization in the console, then open Tunnels → Subdomains at /<org-slug>/tunnel/subdomains. Add an available name using lowercase letters, numbers, and hyphens.
Reservations count toward your organization's plan limit. An address reserved by another organization cannot be used by yours.
Open the tunnel
outray 3000 --subdomain my-appUse the public URL printed by the CLI. Restart with the same subdomain to reuse the address.
--subdomain requests a name; it does not permanently reserve every name you happen to use. Reserve important webhook or OAuth callback names in the console first.
Share it with your team
Members opening tunnels for the same organization can use its reserved names. Only one active tunnel can occupy an address at a time. If it is already in use, stop the other session or choose another name.
To select the organization for a browser-authenticated CLI session:
outray switch my-team
outray 3000 --subdomain my-appRelease an address
Remove the reservation from Subdomains when you no longer need it. Update any webhook destinations, callback allowlists, or saved links before releasing a name.
For a hostname you own, see Custom domains.