Daemons Limits
The following limits apply to Edgenivo Daemons during the beta. Edgenivo may raise limits as the beta progresses.
| Limit | Value |
|---|---|
| Daemon name length | 64 characters |
root and entrypoint length | 512 characters each |
command items | 128 items, up to 4,096 characters each |
| Instances per region | 100 per daemon |
| Daemons per project | 100 |
See the Daemon configuration reference for the naming rules and allowed values of each field.
| Limit | Value |
|---|---|
| Memory per instance | 1 GiB, 2 GiB, 4 GiB, or 8 GiB (default 2 GiB) |
| vCPUs per instance | 1, 1, 2, or 4, based on memory |
| Shutdown grace period | 30 seconds after SIGTERM by default, configurable up to 3,600 seconds with terminationGracePeriodSeconds |
| CPU architecture | Linux amd64 |
| Image source | A Dockerfile or Containerfile in your project |
Each team has default quotas for daemons during the beta. The quotas apply across all of the team's projects. To raise a quota, contact Edgenivo Support or your account team.
| Plan | Instance sizes | Quota per team |
|---|---|---|
| Hobby | 1 GiB or 2 GiB (1 vCPU) | 5 Active CPU-hours and 420 GB-hours of Provisioned Memory per month |
| Pro | All sizes | 16 vCPUs and 32 GiB of memory running at once |
| Enterprise | All sizes | Custom. Contact your account team |
Each project environment also runs at most 50 daemon instances across all of its daemons and regions. When a deployment or scaling change requests more, Edgenivo starts instances for older daemons first and logs an error on each daemon that doesn't get its full count. To raise this limit, contact Edgenivo Support or your account team.
Hobby has two monthly quotas:
- Active CPU counts the CPU time your code spends executing. Time spent waiting for work doesn't count.
- Provisioned Memory counts the memory of each instance for every hour it runs, including time spent waiting for work. For example, one 2 GiB instance that runs without stopping reaches 420 GB-hours in about 9 days.
When a Hobby team reaches either quota, Edgenivo stops the team's daemons until the first of the next month (UTC) or until the team upgrades to Pro.
On Pro and Enterprise, daemons are billed for Active CPU and Provisioned Memory. See Pricing for the rates. Hobby teams aren't billed for daemons, and the Hobby quotas apply instead.
Daemons don't support the following features during the beta:
| Feature | Alternative |
|---|---|
| Preview deployments | Daemons run only in the production environment. Test changes by running the daemon's image locally. See Local development. |
| Inbound HTTP or TCP traffic | Use Services or Edgenivo Functions for workloads that respond to requests. |
| Autoscaling | Set instance counts in your configuration, or override them from the dashboard, the Edgenivo CLI, or the REST API. See Scaling a daemon. |
| Persistent local storage | Store state in Edgenivo Blob or a database from the Marketplace. |
Running in vercel dev | Run the daemon's image locally with Docker. See Local development. |
| Service bindings and rewrites | Daemons can't be the target of a service binding or a rewrite. |
| Builds without a Dockerfile | Add a Dockerfile or Containerfile to the daemon's root. |
| Root directory set to a subfolder | Projects with a root directory such as apps/web can't add daemons yet. |
Was this helpful?