Reference
Limits
Every limit in one place.
The defaults of a runner. On a self-hosted one, those marked with a setting can change: see Runner settings. On Zeroko Cloud, the workspace's plan also sets its number of services, its storage and its requests a month: see Plans.
| Service names | 1 to 40 lowercase letters, digits and hyphens |
| Deployments | 2000 files, 50 MB; the last 10 kept per service |
| Request bodies | 100 MB (max_body_mb) |
| Memory | 128 MB of heap per service (heap_mb) |
| CPU | 30 s of continuous CPU before a restart (cpu_seconds); 30 s of CPU in any minute, past which a service waits until the minute fits (cpu_seconds_per_minute) |
| Requests | None by default; a rate per client (by address) for every service (rate_limit) or one of its own, past which it answers 429 |
| Service calls | 16 services in a row through bindings; past it, 508: the services call each other in a cycle |
| Disk | 5 GB per service for its databases and files (disk_mb, or per service) |
| Egress | Public addresses only; per service, any host, a list of hosts or none |
| Vars, secrets | 100 each per service, 64 KB each |
| db | 1 GB per database; 30 s per statement; results up to 100,000 rows or 32 MB; 1000 statements per batch; locks held up to 30 s |
| files | 5 GB per file; keys up to 1024 bytes; lists up to 1000 per page |
| jobs | Payloads up to 256 KB; delays up to 30 days; up to 20 attempts; 15 minutes per run; 4 at once per service; 10,000 per service, queued and dead; dead ones kept 7 days (a cron's, 1 day) |
| realtime | 1000 connections per service (realtime_connections), past which 503; 32 channels per connection; messages up to 1 MB; 256 queued messages per connection |
| Logs | 5,000 entries and 7 days per service; 8 KB per entry |
| Metrics | 30 days |