--- title: vercel daemons product: vercel url: /docs/cli/daemons canonical_url: "https://vercel.com/docs/cli/daemons" last_updated: 2018-10-20 type: reference prerequisites: - /docs/cli related: - /docs/daemons - /docs/cli/link - /docs/cli/global-options - /docs/cli/login - /docs/cli summary: List and inspect production daemons, override regional instance counts, and inspect or restart individual instances with Vercel CLI. install_vercel_plugin: npx plugins add vercel/vercel-plugin --- # vercel daemons The `vercel daemons` command manages [Daemons](/docs/daemons) for a project. All daemon commands target **production**. They use your [linked project](/docs/cli/link) by default. To select another project, pass `--project ` and use [`--scope`](/docs/cli/global-options#scope) to select its team. Sign in with [`vercel login`](/docs/cli/login), or [authenticate in CI/CD](/docs/cli#using-in-a-cicd-environment). For deployment, scaling, and shutdown behavior, see [Managing Daemons](/docs/daemons/managing-daemons). ## Usage Run `vercel daemons` without a subcommand to list production daemons: ```bash filename="terminal" vercel daemons vercel daemons list ``` *Both commands list daemons for the linked project.* ## Commands ### list List daemon names, status, and instance counts. `ls` is an alias for `list`: ```bash filename="terminal" vercel daemons list --project my-app --scope my-team vercel daemons list --limit 20 --json vercel daemons list --next --json ``` *List daemons for a project, or request a page of results.* By default, the CLI fetches every page. Passing `--limit` or `--next` returns one page. JSON output includes `daemons` and `pagination.next`. Pass the next cursor to `--next`; `null` means there are no more results. | Option | Description | | --- | --- | | `-n, --limit ` | Maximum results for one page, from 1 to 100. Defaults to all results when you omit both pagination options. | | `--next ` | Fetch the next page using the cursor from a previous response. | ### inspect Inspect a daemon by its name in your configuration: ```bash filename="terminal" vercel daemons inspect worker vercel daemons inspect worker --json ``` *Inspect the configuration and readiness of the \`worker\` daemon.* The output includes the image, memory allocation, and regional instance counts. It also indicates whether scaling overrides differ from the deployed configuration. ### scale Override instance counts by region: ```bash filename="terminal" vercel daemons scale worker iad1=3 fra1=1 vercel daemons scale worker iad1=0 vercel daemons scale worker --reset ``` *Set regional counts, stop instances in one region, or restore the deployed configuration.* Each override uses `REGION=NUMBER`, with an integer from 0 to 100. Specify each region at most once. Regions you omit keep their existing counts. Overrides persist across deployments until you reset them. Use `--reset` to clear the overrides and restore the instance counts from your deployed configuration. You can't combine `--reset` with regional overrides. The command applies the change **without a confirmation prompt**. It returns after saving the override; instances start or stop asynchronously. Use `vercel daemons inspect worker` to check readiness. See [Scaling](/docs/daemons/managing-daemons#scaling-a-daemon) for more details. ### instances list List instances across all daemons, or filter by daemon name. `ls` is an alias for `list`: ```bash filename="terminal" vercel daemons instances list vercel daemons instances list worker --json ``` *Find instance IDs, regions, and runtime status.* Use the full `dmni_...` instance ID from this output with `instances inspect` and `instances restart`. ### instances inspect Inspect one instance and its CPU, memory, and network metrics: ```bash filename="terminal" vercel daemons instances inspect vercel daemons instances inspect --since 24h --json ``` *Replace \`\\` with an ID from \`instances list\`.* | Option | Description | | --- | --- | | `-s, --since