Limits | Hub Docs

Not built yet

Backups. Nothing backs up volumes. Keep your own copy of data that matters.
Email. Hub sends none. Invitations and org invites print a link for you to send.
Custom domains. Apps answer only at <app>.<org>.myhub.host.
Scaling. Your org's apps share one host. No autoscaling and no second region.

What	Limit
Upload per deploy	200 MB
Builds kept for rollback	The last 5 per instance
App login	12 hours, then the visitor signs in again
CLI login	90 days
Org invite link	One use, 7 days
App invitation link	No expiry, until you revoke it
`exec` output	48 KiB, and 60 seconds of run time
An unattached shell	Ends after 15 minutes
Open shells	4 per org at a time
Fix attempts for failed GitHub deploys	1 per commit, 5 per org a day
Org name	30 characters
App name	40 characters
Instance name	20 characters

Revoking an app invitation, changing the access mode, removing a member and changing a role take effect on the next request. Everyone with the app open signs in again on that request, without a form. An app that loads data in the background can see that one request fail until the page reloads.
private is not a boundary against members of your org. A member can still deploy to a private app, open a shell in it and read its environment variables.
Hub does not verify email addresses. An invitation or invite link nobody has accepted yet can be claimed by whoever holds it, by signing up with the address it names. Revoke a link that went to the wrong place.
Runtime logs are what the running containers kept. A new release starts them again; build logs stay.
Build-time variables are visible in the image history on your host. Keep secrets in runtime variables.
An app with no public service, such as a worker, still gets a URL in hub apps, and that URL serves nothing.
A deploy from GitHub does not fetch submodules or Git LFS files.
A stopped app answers every visitor with "This app is stopped".
Everyone who can open the workspace reads every page in it.