Reference
Limits
Current v0 release and runtime limits agents should validate before publishing.
For agents: Check file count, decoded file sizes, paths, MIME types, and supported schedules before publish.
Release Limits
- Max files:
5000. - Max single decoded file:
20 MiB. - Max total decoded files:
500 MiB. - File paths must be relative and cannot use empty, dot, or parent segments.
- Scheduled jobs support
every_15_minutes,hourly, anddaily.
Plan Limits
The API enforces account entitlements locally during publish. Free accounts can create up to 3 apps and can publish public static/server apps with small data, files, secrets, and manual jobs. Paid-only manifest features include private apps, public app-user signup, private file stores, scheduled jobs outside the account schedule allowance, generic/GitHub webhooks by tier, slugs, custom domains, analytics, backup/export, and priority support.
Plan failures return 402 with entitlement_required or plan_limit_exceeded. The response includes machine-readable details so agents can point to the blocking manifest path and required plan.
Platform Limits
- Production server apps run as Workers for Platforms User Workers behind the Userland app gateway.
- v0 uses one shared Userland-managed D1 database. Apps do not get a dedicated D1 database.
- App data is scoped by
app_id; large or high-write apps may be moved to app-data shards later. - Current operational tripwires: shared D1 storage near
7 GB, D1 queueing/user-visible SQL latency, or one tenant degrading unrelated apps.