Platform for building and running durable background jobs and AI agent workflows in TypeScript, with retries and observability.
Works with AI agents:llms.txtTrigger.dev runs background work for TypeScript apps: video processing, long chains of AI calls, multi-day email sequences and other work too slow for a serverless function's timeout. You write tasks as ordinary async functions, trigger them from your app, and they run elsewhere with retries, queues and a dashboard of every run.
The model to understand: tasks live in your repo (usually a trigger folder) and are built and deployed by the Trigger.dev CLI to Trigger.dev's infrastructure, separate from your web app. Your app calls trigger() and gets back a handle; a worker runs the task in an isolated container. When a task waits on a subtask or sleeps for a minute or more, the platform snapshots the whole process and frees the machine, then restores it to continue. There are guides for Next.js, Remix, Node.js, Bun and Supabase.
What a small team gets: tasks with no built-in timeout (you set a maxDuration), per-task retries with backoff, idempotency keys so retried steps are not repeated, queues and concurrency limits, cron schedules, machine sizes up to 8 vCPU and 16 GB RAM, realtime run updates in React, and preview branches. A Python build extension lets tasks run Python scripts. It runs on Trigger.dev Cloud, where you choose a region per run, or self-hosted with Docker or Kubernetes.
Limits worth knowing: payloads are capped at 3 MB and outputs at 10 MB. Self-hosting lacks the snapshotting, warm starts and auto-scaling of the cloud version, and you own its uptime.
24 tools, from its own code, website and Product Hunt page.
23 makers' products, each linked to the source that shows it, and 5 open-source projects that declare it in their code.
giselleGiselle is an open-source tool for building and running AI workflows in a visual node ed…“Trigger.dev powers our AI workflow execution engine. Running complex multi-step AI workflows reliably in the background — with support for long-running tasks and automatic retries — would have been incredibly complex to build ourselves. Thank you for making background job processing so developer-friendly!”
Background Jobs & CronMaker says so +1 · source ↗
Human BehaviorHuman Behavior is a product analytics tool whose SDK records events, errors and session…“Orchestrates our long-running background agents 24/7”
Background Jobs & CronMaker says so +1 · source ↗
THEO GrowthPositioning Intelligence for brand strategists“To get the workflows organized and stable”
Background Jobs & CronMaker says so +1 · source ↗
Cal.comOpen-source scheduling platform: a Calendly alternative you can self-host or use hosted,…Background Jobs & CronCustomer story +1 · source ↗
papermarkOpen-source document sharing and virtual data room with viewer analytics and custom doma…Background Jobs & CronIn its code +1 · source ↗
ReloopVideo studio built for small teams“Probably one of the best background task experiences I've ever had, it's so nice working with tools like this. Everything just works and it's super complete”
Background Jobs & CronMaker says so · source ↗
FlowgladFlowglad is an open-source payments and billing provider that apps integrate without web…“Powers all of our background jobs”
Background Jobs & CronMaker says so · source ↗
Onboarding0Turn company knowledge into AI-guided onboarding“With Trigger.dev we make sure every background job is resilient and durable!”
Background Jobs & CronMaker says so · source ↗
ContriveSearch and act across all your work apps“The processing of indexing data from various work applications is performed through time-consuming processes, retries, and tracking of their status. We were provided with a powerful way of running and monitoring these workflows using Trigger.dev.”
Background Jobs & CronMaker says so · source ↗
MiddayRun your business smarter“We have a lot of background jobs in Midday, and thanks to Trigger.dev we can focus on building our product instead of handling queues and infrastructure.”
Background Jobs & CronMaker says so · source ↗
CopyCopterCreate viral TikToks and Shorts from text to video with Al“CopyCopter uses Trigger.dev as a background job manager, making the code cleaner, more scalable and more fun to play with! Trigger.dev is a must-have for NextJS Serverless App.s”
Background Jobs & CronMaker says so · source ↗
devlogs.ggdaily game devlog finds“I'm using Trigger to run background jobs for maintaining all the data on Directus.”
Background Jobs & CronMaker says so · source ↗“The most sturdy option.”
Background Jobs & CronMaker says so · source ↗“Trigger.dev made it easy for us to do post-processing on Clawcast's conversations to generate audio in parrellel and ensure we create podcast cover art.”
Background Jobs & CronMaker says so · source ↗
KeetVideo Courses on Anything“Best tool for long running workflows.”
Background Jobs & CronMaker says so · source ↗“I was having difficulty with audio processing in background jobs, so I looked for solutions like BullMQ with Redis and Squirrel. However, I found Trigger.dev’s documentation to be very clear and helpful. Matt, the CEO, was also great on Discord with my questions. Thanks 💚”
Background Jobs & CronMaker says so · source ↗
Pitch Lucy AIAdversarial Agent Shark Tank Game“solved a lot of security issues for us thanks”
Background Jobs & CronMaker says so · source ↗
BoltoFind, interview, and vet engineers with AI“We love Trigger.dev – particularly appreciate the automatic retries on tasks and no timeouts.”
Background Jobs & CronMaker says so · source ↗“Their SDK was key to powering our live previews and virtual machines, helped us move fast with a super responsive team behind it”
Background Jobs & CronMaker says so · source ↗Open source: a project that declares Trigger.dev as a dependency in its public code — verifiable, but not necessarily a live product.
12 makers on why they use Trigger.dev, in their own words on Product Hunt.
Trigger.dev powers our AI workflow execution engine. Running complex multi-step AI workflows reliably in the background — with support for long-running tasks and automatic retries — would have been incredibly complex to build ourselves. Thank you for making background job processing so developer-friendly!
giselleSep 2026 ↗I was having difficulty with audio processing in background jobs, so I looked for solutions like BullMQ with Redis and Squirrel. However, I found Trigger.dev’s documentation to be very clear and helpful. Matt, the CEO, was also great on Discord with my questions. Thanks 💚
The processing of indexing data from various work applications is performed through time-consuming processes, retries, and tracking of their status. We were provided with a powerful way of running and monitoring these workflows using Trigger.dev.
ContriveSep 2026 ↗CopyCopter uses Trigger.dev as a background job manager, making the code cleaner, more scalable and more fun to play with! Trigger.dev is a must-have for NextJS Serverless App.s
CopyCopterSep 2026 ↗Probably one of the best background task experiences I've ever had, it's so nice working with tools like this. Everything just works and it's super complete
ReloopSep 2026 ↗Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general. Open a row to see the pull requests.
Trigger.dev → BullMQ3 PRs
InngestEvent-driven, multi-step workflows where each step retries on its own and your code stays in your existing app.Compare with Trigger.dev →On Product Hunt, people weigh it against: Temporal.
There is no platform timeout. You set a default maxDuration in trigger.config.ts (minimum 5 seconds) and can override it per task; set it very high if you never want runs stopped. source ↗
On the cloud, no. While a task waits on a subtask or a wait of 60 seconds or more, its state is checkpointed and the machine is released, and that paused time isn't charged. source ↗
Yes, with Docker Compose or a Helm chart for Kubernetes. The self-hosted version lacks warm starts, auto-scaling and checkpoints (waits keep the machine busy), and gets community rather than dedicated support. source ↗
Yes. Each project has a default region and you can override it per run, for example eu-central-1. The region decides where the run executes, not where payloads, outputs or logs are stored. source ↗
Free projects get 20 concurrent production runs, 10 schedules, 10 realtime connections, one day of log retention and no preview branches. source ↗
A single trigger payload can be up to 3 MB and a task's output up to 10 MB; larger data should go through storage you pass by reference. source ↗
Yes, through the @trigger.dev/python build extension, which installs Python in the deployed image so a TypeScript task can run Python scripts. The tasks themselves are still defined in TypeScript. source ↗
Yes — there is a free tier a small product can run on; paid use starts at $10/mo. source ↗
Open source, and you can self-host it. source ↗
It serves an llms.txt docs index.
23 makers' products we track, each with a source, and 5 open-source projects declare it in their code. source ↗
AI SDK
Amazon Bedrock
Amazon S3
Amazon SES
Amazon Web Services
Better Auth
BugSnag
Claude
Claude Code
Clerk
ClickHouse
Drizzle ORM
Express
MinIO
Nodemailer
OpenAI API
PostgreSQL
PostHog
Prisma
React
React Router
Resend
Sentry
Vercel
Temporal
Upstash
RabbitMQ
pg-boss
Celery