🐙
Freemiumbackground jobsai agentsworkflow automationopen source

Trigger.dev lets developers write background jobs and AI agent workflows as plain code and deploy them without managing queues, retries, or infrastructure. It handles long-running tasks, scheduling, and observability out of the box, self-hostable or via a managed cloud. Apache-2.0 licensed, 16,000+ GitHub stars.

What is Trigger.dev?

Trigger.dev is an open source platform for background jobs and agent workflows, written as ordinary code. You define a task in your own TypeScript codebase, deploy it, and the platform handles the parts that make background work tedious: queueing, retries after failure, scheduling on a cron, and long running execution that would time out inside a normal web request. Every run is observable, so you can open a specific execution and see where it went, which is usually the difference between a background system you trust and one you dread. Because tasks are code rather than nodes on a canvas, they live in version control, get reviewed in pull requests, and can be tested like the rest of your application. It is Apache licensed and self hostable if you want to run the infrastructure yourself, with a managed cloud option for teams that do not.

Who is Trigger.dev for?

Reach for it when work no longer fits inside a request cycle. Typical cases are AI workflows that call a model several times and take minutes, video or document processing, nightly syncs against a third party API, and anything that must retry sensibly when an upstream service fails. It fits teams already writing TypeScript who want their background layer to look like the rest of their code, not a separate system they have to click through. If your needs are a single cron job on a small server, it is more machinery than the problem deserves. If you are not in the TypeScript ecosystem, the fit weakens, since the developer experience is the main argument for it.

How does Trigger.dev compare?

n8n is the visual counterpart. It is excellent when the workflow is connecting services and someone non technical may need to look at it, and harder to review and test when the logic gets complicated. Langflow occupies a similar visual space but aimed at language model pipelines and retrieval, which makes it a prototyping tool more than a production job runner. Ruflo sits at a different layer again, orchestrating multi agent swarms in TypeScript, where Trigger.dev cares about durable execution regardless of whether the task involves a model at all. Pick Trigger.dev when reliability, retries, and observability are the problem, and a visual builder when the point is that other people can see and edit the flow.

Compare with: n8n, Langflow, Ruflo

Trigger.dev pricing

The catalog records Trigger.dev as freemium. The project is Apache licensed, so you can self host the whole thing and pay only for the servers and database it runs on, plus the operational time. The managed cloud follows the usual pattern for this category: a free tier generous enough to build and test on, with paid plans as usage, concurrency, and retention grow. Check the site for current limits rather than trusting a directory. Self hosting trades a recurring bill for infrastructure you maintain yourself.

Notes

No notes have been added for this tool yet.

Trigger.dev FAQ

Can I self host Trigger.dev?
Yes. The project is open source under Apache 2.0 and publishes a self hosting path, so you can run it on your own infrastructure and keep job data in house. You take on the database, the workers, and upgrades in exchange for removing the vendor bill and any data residency concerns.
What language do I write tasks in?
TypeScript, inside your own repository. Tasks are normal functions using the platform SDK, which is why they version, review, and test like the rest of your code. That is the main structural difference from visual automation tools, where the logic lives in the vendor interface rather than your codebase.
How is it different from a cron job?
Cron starts a process on a schedule and nothing more. Trigger.dev adds durable execution, automatic retries with backoff, concurrency control, and a run history you can inspect when something fails. Scheduling is one trigger among several, alongside events and calls from your own application code.
Browse all Open Source