Web apps

A web app is a Service that answers HTTP requests. Tokay keeps it available at HTTPS, checks updates before traffic moves, and can protect it without app login code.

Last updated October 14, 2026

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. Use the URL shown on the Service page rather than assembling one. See Custom domains for your own domain.

Updates move traffic after they work

A new version starts beside the current one and receives no traffic until health checks pass. A failed update leaves the current version serving. See Deploys, updates, and rollback.

Status explains whether the app is serving

The Service page separates serving, starting, paused, unhealthy, and offline states. Events keep the timeline and Logs show process output.

Access belongs to the Service

Each web Service is Public or Private. Public turns Tokay sign in off. Private admits the union of its reusable project Groups, exact-email People, company domains, and project Machines. Groups contain People, domains, and Machines but not Groups.

New Projects start Public. The Project setting only chooses whether Services created later start Public or Private. It does not change existing Services.

Tokay owns magic link sign in at the platform boundary. A Private web Service can add public routes, specific paths that open without sign in for webhooks or callbacks, and those requests are always anonymous. There is no way to require sign in on part of a Public Service. See Who can open your app.

Persist files the app owns

Files outside persistent storage reset during deploys and restarts. Put durable data in /tokay/data or declare the app's natural write directory. See Files and persistent storage.