Account & tokens
Checking your identity, minting tokens for CI, upgrading plans, and the canonical tier-limits table both the API and the Worker enforce.
Checking your account
Prints:
- Email and username
- Org (if any) and your role within it
- Current tier (free, pro, pro_unlimited, team, enterprise)
- Storage used vs. limit
- Subdomain your apps live on (
{username}.deloc.devor{org-slug}.deloc.dev)
Run this before anything destructive — it's easy to end up in the wrong account when you have multiple.
API tokens
Tokens authenticate every CLI and MCP call. You already have one from deloc login (stored in ~/.deloc/config.json). Create additional named tokens for specific machines or CI pipelines:
Using a token
Three ways, in precedence order:
DELOC_TOKENenvironment variable (highest priority — best for CI)~/.deloc/config.json(written bydeloc login)- MCP server
envblock in the editor's config
Token scope and expiry
Tokens carry the identity of the user (or org member) who created them. They inherit that user's role — publisher, admin, viewer. Default expiry is 30 days, but you can rotate or revoke any time from deloc tokens list.
Upgrading and billing
Self-serve plans — Pro, Pro Unlimited, Team — are Stripe checkouts. You're returned to the dashboard after payment and the tier flips immediately. Enterprise is custom — see pricing and reach out.
Tier limits at a glance
The canonical values live in packages/shared/src/constants.ts and are enforced identically by the API (on upload) and the Worker (on each request). Enterprise custom deals override individual caps via the org record.
- Free tier shows a Deloc branding badge; all paid tiers remove it.
- Domain-restricted access is Pro Unlimited and above.
- Actions are Pro and above.
- Team tier adds multi-publisher, org roles, and activity log.
- Enterprise adds SSO, admin console, audit log export, SCIM.
Logout and switching accounts
Revokes the current token server-side and clears ~/.deloc/config.json. Your MCP server loses auth too (it reads the same config).
To switch accounts, logout then login with the other credentials:
Or override on a per-command basis without touching the config: