Simple pricing, built for growth

What is a task?

Tasks are functions that can run for a long time and provide strong resilience to failure. They run on our servers so there are no timeouts and no infrastructure to manage. You can read more about how they work in our docs .

Can I self-host Trigger.dev?

Absolutely. We have a self hosting guide right here .

How long can a task run for?

Tasks can run for as long as you need, with no timeouts.

Where are my tasks run?

In order to provide reliable tasks with no timeouts, we host your task code on our servers and run it on our infrastructure. Your tasks are added to /trigger folders and code inside these is bundled and deployed together. Of course you can self-host everything if you prefer.

How do I estimate my usage?

Multiply per second machine price by the seconds your run will take. Add the per run invocation cost and multiply by your run count.

A 10s task that does 100 runs per day on the small-1x machine:

1 run = (10s × $0.0000338) + $0.000025 = $0.000363
1 day = 100 × $0.000363 = $0.0363
1 month = $0.0363 × 30 = $1.09

How does usage work?

We charge for usage in 2 ways: the number of seconds of compute your tasks execute for, and the number of runs you do. The compute cost depends on the machine you've chosen.

When triggering and waiting for subtasks, the parent is checkpointed and while waiting does not count towards compute usage. When waiting for a time period (wait.for or wait.until), if the wait is longer than 5 seconds we checkpoint and it does not count towards compute usage.

Are there rate limits?

Yes. The free plan is limited to 60 API requests per minute while paid plans are limited to 1,500 API requests per minute. You can trigger more tasks than this by using batchTrigger().

Can I get more concurrency?

Yes. Concurrency is limited on our Free plan but you can increase your concurrency limit by upgrading to a paid plan. If your tasks require more than the Pro plan limit (100), you can purchase bundles of 50 additional concurrency for $50/month.

Do tasks waiting to execute count towards my concurrency limit?

No. Concurrency limits in Trigger.dev only apply when code is executing. Our built-in wait functions snapshot the process and restore it later, meaning you don't pay for time spent waiting. This approach allows you to efficiently manage long-running tasks, such as multi-day email marketing flows, without unnecessarily consuming your concurrency limits or incurring costs during idle periods.

Can I run Trigger.dev locally?

Yes. Using our CLI you develop your tasks locally with hot reloading.

What frameworks does Trigger.dev support?

Trigger.dev is framework agnostic so it works with most JavaScript frameworks. We have created guides for popular frameworks which provide a great way to get started.

Can I build complex tasks?

Yes. There’s no limit to the complexity of tasks you can create. Tasks are created in code so you can write conditional, looping, branching or time delayed logic using normal async code.

Can I use version control or roll-backs?

Yes. You create tasks directly in your own code so it’s version controlled with everything else. You can also rollback to previous deploys in the dashboard.

How long does it take to code a task?

A simple task triggering using APIs will take about 5 minutes to create.

Can I use any API I need?

Yes. You can use any API either by using their SDK or through web requests using fetch or your preferred alternative.

Is Trigger.dev open source?

Yes. Trigger.dev is open source using the Apache 2.0 license. We are committed to open source software and working with our community to build a great product.