Skip to content
Dashboard

Run background workers on Vercel

Vercel Daemons continuously pull and execute work from queues, databases, and third-party systems. No HTTP server required.
Seen from inside a daemon: a line of gray square tiles, one job each, recedes into the dark toward a vanishing point. When a tile reaches the front, a light runs once around its edge and it turns blue, processed. Then it is pulled in and out of view, the line steps forward, and a new tile appears far away.

For all your pull-based workloads

Deploy, monitor, and manage your daemons

  • Deploy daemons alongside your frontend and backend services. Set the working directory and start command for each daemon.

  • Monitor activity. Use built-in observability to spot issues and troubleshoot errors.

  • orders-daemoniad1 · 3/5 ready
    5

    Adjust capacity. Scale instances from the dashboard or API.

  • Handle restarts gracefully. Clean up on termination signals before restarting.

Frequently asked questions

What are Vercel Daemons?
Vercel Daemons run background processes on Fluid compute. They are designed for workers that pull work from queues or other systems.
What can I run with Daemons?
Any long-running, always-on process that pulls its own work, such as queue consumers, workflow workers, and CI runners.
How do Daemons scale?
You choose the number of running instances. You can adjust this manually or programmatically via API.
Do Daemons support persistent storage?
Persistent filesystem storage is not included in the initial release but will be added.
Can Daemons serve web requests?
It is not possible to serve HTTP traffic from a worker in the initial release. We expect this capability to be added later.

Deploy your first daemon