Limits
There are no plans: every workspace’s sites get the same limits.
Per request
Section titled “Per request”Each request a site’s Worker answers may use:
| Limit | |
|---|---|
| CPU time | 50 ms |
| Subrequests | 50, the platform paths included |
Time spent waiting on fetch, storage and the platform doesn’t count as CPU time.
Builds and uploads
Section titled “Builds and uploads”| Limit | |
|---|---|
| One git push or fetch | 512 MiB |
| The install command | 15 minutes |
| The build command and packaging, together | 20 minutes |
wrangler.jsonc and package.json |
1 MiB each |
| The build’s archive, compressed | 200 MiB |
| The build’s archive, expanded | 32 MiB: the Worker and every asset together |
| The bundled Worker | 10 MiB |
| Asset files per version | 100,000 |
| One asset file | 25 MiB |
Resources declared in wrangler.jsonc |
5 of each type (KV, D1, R2, queues) |
A build that goes past a limit fails with a message naming it, and the version that was live stays live.
Settings
Section titled “Settings”| Limit | |
|---|---|
| Worker name | 3 to 40 lowercase letters, digits and dashes |
| Description | 200 characters |
| Variables | 64 per Worker; names up to 64 characters, values up to 5,000 |
| Secrets | Names up to 64 characters, values up to 5,000 |
| Cron triggers | 5 per Worker |
| Routes | 20 per Worker |
| Push tokens | 1 to 365 days each |
Platform calls
Section titled “Platform calls”The platform paths have limits of their own, per minute:
| Path | Body | Rate |
|---|---|---|
/_platform/forms |
256 KB | 10 per site and visitor |
/_platform/store/checkout |
64 KB | 120 per site |
/_platform/store/checkout-status |
64 KB | 120 per site |
/_platform/store/submit-review |
64 KB, a review at most 16 KB | 30 per site and visitor |
/_platform/store/page-data, /_platform/store/reviews |
64 KB | None: they read a cached copy |
Over a rate, the call answers 429 with { "error": { "code": "rate_limited" } }. The analytics tracker’s beacon takes 120 posts a minute from one address.
Paths that never reach a site
Section titled “Paths that never reach a site”Paths that only scanners and exploit kits ask for get a 403 from Digize before the site’s Worker runs, whatever the site would have served, so they cost the site nothing. Each matches without regard to case, exactly or as a prefix (/backup also covers /backup/2026.zip):
/wp-admin/wp-login.php/wp-content/wp-includes/wp-json/xmlrpc.php/.env/.git/.svn/.hg/.aws/.ssh/.htaccess/.htpasswd/.ds_store/phpmyadmin/pma/adminer.php/config.php/config.json/database.sql/db.sql/backup/backup.zip/backup.sql/vendor/phpunit/server-status/cgi-bin/etc/passwd/web.config
/.well-known isn’t on the list, so certificates and app links work. The analytics paths /_platform/t/…, /_platform/e and, with a GA4 property, /_platform/g/… are answered by Digize too (Analytics).