Invite-Beta Limits
These are safety boundaries for the invite-only disposable DEV beta, not a production capacity promise.
Direct-upload envelope
Section titled “Direct-upload envelope”| Boundary | Exact limit |
|---|---|
| Manifest entries | 256 files |
| Individual object | 8 MiB per file |
| Complete manifest | 64 MiB aggregate |
| Deploy-lock request | 128 KiB manifest/admission body |
| Canonical paths | Paths are up to 512 bytes |
| Admitted media type | Content type is up to 128 bytes |
| Session lifetime | Deploy session hard age is 60 minutes |
| Heartbeat window | Inactivity is 10 minutes |
| Provider work | 3 provider attempts per operation |
The limits apply to the complete manifest, not only to files that changed.
Admission rates
Section titled “Admission rates”- 4 admitted deploy sessions/hour per customer and per validated client IP.
- 30 ordinary lifecycle mutations/hour per customer and per validated client IP.
Ordinary lifecycle mutations are app create/delete and customer-token
mint/revoke. Each customer and validated client-IP bucket is enforced
independently. A rejected admission uses the stable rate_limited error and a
retry interval.
Customer tokens and apps
Section titled “Customer tokens and apps”A customer can have 3 active customer tokens.
The app cap is controlled by the operator-authorization grant. There is no universal app cap that applies to every grant.
Reaching a boundary does not imply an upgrade path. Stop the bounded walkthrough and contact the operator.