Workflow Pricing and Limits
Vercel bills Workflows usage across three resources:
- Workflow Events: Every state transition in a workflow run is persisted as an event. See Events for more details.
- Workflow Data Written: The amount of data written to managed persistence for workflow state and event logs, including stream data.
- Workflow Data Retained: The amount of data stored per month in managed persistence.
Vercel bills each resource based on usage. Hobby includes monthly allowances for Workflow Events and Workflow Data Written. Workflow Data Retained is not available on Hobby, and Vercel bills Pro usage on demand.
| Resource | Hobby Included | On-demand Rates |
|---|---|---|
| Workflow Events | 50,000 events / month included | $0.02 per 1K events |
| Workflow Data Written | 1 GB | $0.50 per GB |
| Workflow Data Retained | — | $0.50 per GB-month |
You can inspect the amount of Workflow Data Written for a specific workflow run by navigating to the workflow details on the Workflows page in the dashboard. Vercel calculates Workflow Data Retained based on the amount of data written and the retention period. For example, writing 1 GB and having a retention period of 1 month would result in 1 GB-month of retained data.
Functions invoked by Workflows continue to be charged at the existing compute rates. We recommend using Fluid compute with Workflow for reduced costs and higher performance.
Workflow uses Vercel Queues to orchestrate workflow runs. Vercel bills Queues usage at standard rates, see Vercel Queues pricing for more details.
Every state transition in a workflow run is persisted as an event. The full list of events is available in the Workflow SDK documentation.
As an example, a normal step function execution produces three events: step_created, step_started, and step_completed. For every time a step re-tries due to a transient error, a step_retrying event is also created.
Vercel bills Workflow Data Retained for the retention period of each run, which depends on your team plan. For retention periods, how long Vercel keeps run data, run metadata retention, and how to delete run data sooner, see Data Retention.
Vercel bills a run's full retention period when the run finishes. If you later delete the run's data from the dashboard, Vercel doesn't refund or prorate the Workflow Data Retained already billed for it. To avoid billing Workflow Data Retained for a run, start it with auto-delete.
The following limits apply to all Workflow runs. Events per run and Steps per run are the defaults for the Node.js runtime, and the QuickJS runtime lifts both.
| Limit | Value | Details |
|---|---|---|
| Run creations per second | 1,000 | |
| Events per run | 25,000 limit | Applies to the default Node.js runtime. QuickJS runs with snapshotting enabled are exempt from this cap. |
| Steps per run | 10,000 | Applies to the default Node.js runtime. Steps write events, so QuickJS runs that are exempt from the event cap can execute more steps. |
| Event creations per run per second | 200 | |
| Hook creations per second | 200 | |
| Max payload size | 50 MB | |
| Maximum total entity storage per run | 2 GB | |
| Max workflow replay duration | 240s | |
| Maximum run duration | No limit | |
Maximum sleep duration | No limit | |
| Max runtime of individual step | see Vercel Functions limits | |
| Max stream storage size | Unlimited | |
| Max stream chunk size | 10 MB | |
| Max stream chunks per second per stream | 1,000 | |
| Hook token size | 255 bytes | |
| Attributes per run | 64 | |
| Attribute write size | 8 KiB | |
| Workflow name | 255 bytes | |
| Step name | 255 bytes | |
| Dynamic workflow source size | 128 KiB | Dynamic workflows only. Experimental. |
Workflow runs your workflow function on the Node.js runtime by default, which caps each run at 25,000 events. Runs that start on the experimental QuickJS runtime with snapshotting enabled are exempt from that cap, so a run can record more events and execute more steps than the table above lists. Every other limit on this page still applies, including payload size, entity storage, replay duration, and the rate limits below.
To opt in:
- Set the
WORKFLOW_VMenvironment variable toquickjsfor your project. - Leave
WORKFLOW_SNAPSHOT_THRESHOLDunset, or set it to a positive integer. QuickJS snapshots workflow state every 1,000 events by default. A value of0turns snapshotting off, and those runs keep the 25,000 event cap. - Redeploy your project.
A run records its runtime and snapshot policy when it starts, so the exemption covers only runs that start after you redeploy. Runs already in progress keep the limits they started with, and runs that already failed with MAX_EVENTS_EXCEEDED don't resume on their own. Start those runs again.
QuickJS is experimental, and your workflow function sees a different set of globals: Intl, WebAssembly, and Atomics are unavailable, and crypto.subtle methods throw. Your step functions are unaffected and keep full Node.js access. For the complete list of differences, see the QuickJS runtime documentation.
| Limit | Value | Details |
|---|---|---|
| Concurrency | up to 100,000, see Vercel Functions limits | |
| Queued runs | No limit, see Vercel Queues limits | |
| Schedules/cron | No limit | |
| Projects | Unlimited | |
| Real-time connections | No limit | |
| Observability retention | See Data Retention | |
| Compute resources | See Vercel Functions limits | |
| Maximum total bundle size | 250MB, see Vercel Functions limits |
Requests include any event creation or stream write operation, as well as any operation for reading events, stream chunks, metadata, or event data.
For any request made from your deployment, exceeding the rate limit will automatically re-try with backoff. This includes the initial request to start the workflow. If the call to start() does not throw an error, the workflow will eventually start and run to completion or failure.
This means hitting the rate limit will not cause your workflow to fail, but it will slow down the rate at which your workflows run.
A rate-limited write that records a step's result is retried for as long as the function invocation runs, so the step doesn't run again or use up one of its retries.
| Plan | Requests per minute |
|---|---|
| Hobby | 50,000 |
| Pro | 500,000 |
| Enterprise | 2,500,000 |
A run's cost depends on how many events it records and how much data it writes and keeps. Vercel bills it as Workflow Events, Workflow Data Written, and Workflow Data Retained at the rates in the table above. The functions that execute your workflow and steps are billed at Vercel Functions rates, and the messages that dispatch them at Vercel Queues rates. To estimate events, count three for the run itself (created, started, and completed or failed), three for each step that succeeds on its first attempt, at least one more for each retry, two for each sleep(), and at least two for each hook. To see how much data a finished run wrote, open it on the Workflows page in the dashboard.
Yes. Hobby includes a monthly allowance of Workflow Events and Workflow Data Written, listed in the table above. Workflow Data Retained isn't available on Hobby. On Pro, Vercel bills all three resources on demand at the rates in the table.
No. A suspended run doesn't invoke any functions, so it uses no compute while it sleeps or waits on a hook, even for days or months. Creating and completing the sleep or hook records events, which count toward Workflow Events.
On the default Node.js runtime, a run that reaches 25,000 events fails with the MAX_EVENTS_EXCEEDED error code and doesn't resume on its own. Reduce the events per run, then start it again. You can split independent work into child workflows, bundle several items into each step, or switch to the QuickJS runtime with snapshotting, which is exempt from the cap. Replay can slow down past 2,000 events, so split long runs well before they reach the limit.
Vercel bills the resources your agent or bot uses, not eve or Chat SDK themselves. Every eve session on Vercel runs as a workflow, so its checkpoints and waits count toward Workflow Events and Workflow Data Written, alongside Vercel Functions, AI Gateway, Vercel Sandbox, and any other resources it uses. See eve pricing and limits. A Chat SDK bot incurs Workflows charges only for the workflows you start from it, such as an approval flow. Its webhook handlers run as regular Vercel Functions.
Was this helpful?