Web apps
A web app is a Service that answers HTTP requests. Tokay keeps it running at an HTTPS URL and protects each update with health checks, whether the code serves a website, dashboard, API, or static files.
Last updated
AI agent? Start with llms.txt.
Every web app gets a stable address
A Service receives a URL such as my-blog-r4k7x2m9.tokay.app. The readable name comes from the Service, and the short ID identifies that Service permanently.
HTTPS certificates are issued and renewed automatically. Renaming the Service changes the readable part of the URL, and Tokay redirects earlier names to the new address. Because each rename creates another address, a web app can be renamed up to three times.
Use the URL shown on the Service page rather than constructing one from a name. See Custom domains when the app should use a domain you control.
Updates take traffic only after they work
A new version starts beside the current version and receives no traffic until it passes health checks. When the checks succeed, Tokay moves traffic to it. When they fail, the current version keeps serving.
This is the normal deployment path rather than a special release mode. See Deploys, updates, and rollback for the pipeline and version history.
Status explains whether the app is serving
The Service page tells you whether the app is serving, still starting, intentionally paused, or needs attention because it is unhealthy or offline. The Events tab keeps the timeline of these changes so you can separate an intentional stop from an incident.
Access can be public or protected
New Projects are public, so anyone with a web app's URL can open it. When the app is for coworkers, clients, or invited visitors, use the Project's Access tab to make the Project Private and choose which Services should require access.
Every restricted Service in the Project uses one audience. Tokay provides magic link sign in at the platform boundary, so the app does not need its own login code. A selected web path or whole Service can still be public when outside systems need to reach it. See Who can open your app for how these choices work together.
Persist files the app owns
Files written outside persistent storage reset when the Service deploys or restarts. Put uploads and application data in /tokay/data or mark the existing directory as persistent. See Files and persistent storage.
Live process output appears on the Logs tab. See Logs and debugging for incident evidence and debugging tools.