---
title: Daemons Limits
product: vercel
url: /docs/daemons/limits
canonical_url: "https://vercel.com/docs/daemons/limits"
last_updated: 2018-10-20
type: reference
prerequisites:
  - /docs/daemons
related:
  - /docs/daemons/config-reference
  - /docs/plans/hobby
  - /docs/plans/pro-plan
  - /docs/plans/enterprise
  - /docs/daemons
summary: Limits on the configuration, size, and capabilities of Vercel Daemons during the beta.
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

# Daemons Limits

The following limits apply to Vercel Daemons during the beta. Vercel may raise limits as the beta progresses.

## Configuration limits

| 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                         |

See the [Daemon configuration reference](/docs/daemons/config-reference) for the naming rules and allowed values of each field.

## Instance limits

| 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 | 10 seconds after `SIGTERM` by default             |
| CPU architecture      | Linux `amd64`                                     |
| Image source          | A `Dockerfile` or `Containerfile` in your project |

## Default quotas

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 [Vercel Support](/help) or your account team.

| Plan                                    | Instance sizes          | Quota per team                                  |
| --------------------------------------- | ----------------------- | ----------------------------------------------- |
| [Hobby](/docs/plans/hobby)              | 1 GiB or 2 GiB (1 vCPU) | 10 vCPU-hours per month                         |
| [Pro](/docs/plans/pro-plan)             | All sizes               | 16 vCPUs and 32 GiB of memory running at once   |
| [Enterprise](/docs/plans/enterprise)    | All sizes               | Custom. Contact your account team               |

On Hobby, each instance uses vCPU-hours for as long as it runs, so a single 1-vCPU instance uses the monthly allowance in about 10 hours. Use Hobby to try daemons, and use Pro for daemons that need to run all month. When a Hobby team reaches the allowance, Vercel stops all of its daemon instances and logs an error. The daemons start again at the beginning of the next month, or when you upgrade the team to Pro.

## Unsupported features

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](/docs/daemons#local-development). |
| Inbound HTTP or TCP traffic     | Use [Services](/docs/services) or [Vercel Functions](/docs/functions) for workloads that respond to requests.                                              |
| Autoscaling                     | Set instance counts in your configuration or from the dashboard. See [Scaling a daemon](/docs/daemons/managing-daemons#scaling-a-daemon). Scaling from the Vercel CLI and API is coming soon. |
| Persistent local storage        | Store state in [Vercel Blob](/docs/vercel-blob) or a database from the [Marketplace](/docs/marketplace-storage).                                           |
| Running in `vercel dev`         | Run the daemon's image locally with Docker. See [Local development](/docs/daemons#local-development).                                                      |
| Service bindings and rewrites   | Daemons can't be the target of a [service binding](/docs/services/bindings) 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](/docs/builds/configure-a-build#root-directory) such as `apps/web` can't add daemons yet.                                |


---

[View full sitemap](/docs/sitemap)