Tokens & ownership
Understand flypod account sessions, per-site manage tokens, claim tokens, and how each credential changes ownership and expiry.
A site is either anonymous and ephemeral or owned by an account with no expiry. Three credentials appear in that lifecycle.
Credential map
| Credential | Scope | Used for |
|---|---|---|
| Account session token | One account | Owned deploys, account site listing, and managing sites owned by that account. Created by the flypod login device flow. |
manage_token | One site | Reading metadata, adding versions, rolling back, and proving control during login auto-attach. |
claim_token | One anonymous site | Cross-machine fallback for attaching an anonymous site to an account. |
Account session token
flypod login obtains a Better Auth session token after you approve a device in
the browser. The CLI saves it outside the project and sends it as a bearer token.
For stateless automation, FLYPOD_TOKEN can supply an existing session directly.
Treat this token like a password: it represents the whole account. The old
custom fk_ API-key system and its key-creation subcommand are retired.
FLYPOD_API_KEY remains only as a legacy environment-variable fallback.
manage_token
Every deploy returns a manage_token. It authorizes the version loop for that
specific site. Anonymous CLI deploys store it in projects.json so
flypod update and flypod rollback work without flags.
If you use the HTTP API directly, save the token yourself. The server stores only its hash and cannot recover it later.
claim_token
Anonymous deploys also return a claim_token. Use it with
flypod claim <site_id> <claim_token> when you want to attach a deploy from a
different machine. The normal same-machine login path uses the locally stored
manage_token instead.
Anonymous vs owned
| Anonymous | Owned | |
|---|---|---|
| Created by | Deploy with no account session | Deploy with a saved login or FLYPOD_TOKEN |
| Managed via | manage_token | Account session or manage_token |
| Expiry | 14 days | None |
| Search indexing | noindex | Indexable |
Ephemerality & TTL
Anonymous deploys expire 14 days after deploy and are swept by a garbage collector; deploying while logged in or claiming a site makes it permanent.
Comments
Anonymous, anchored comments on flypod sites, including visitor identity, access modes, threaded replies, and current hosted limitations.