Trigger.dev
@triggerdev.bsky.social
Open source background jobs and AI infrastructure (YC W23).
→ http://trigger.dev
→ http://github.com/triggerdotdev
→ http://trigger.dev/discord
The official 🦋 account for Trigger.dev
→ http://trigger.dev
→ http://github.com/triggerdotdev
→ http://trigger.dev/discord
The official 🦋 account for Trigger.dev
1️⃣ Upload triggers a batch task
2️⃣ 3 images are generated in parallel
4️⃣ Generated images auto-upload to R2 storage
5️⃣ Frontend shows live run progress
2️⃣ 3 images are generated in parallel
4️⃣ Generated images auto-upload to R2 storage
5️⃣ Frontend shows live run progress
November 6, 2025 at 5:45 PM
1️⃣ Upload triggers a batch task
2️⃣ 3 images are generated in parallel
4️⃣ Generated images auto-upload to R2 storage
5️⃣ Frontend shows live run progress
2️⃣ 3 images are generated in parallel
4️⃣ Generated images auto-upload to R2 storage
5️⃣ Frontend shows live run progress
Waitpoints: Pause task execution for @replicate webhooks using wait.forToken(). No polling, no timeouts, just normal async waiting.
November 6, 2025 at 5:45 PM
Waitpoints: Pause task execution for @replicate webhooks using wait.forToken(). No polling, no timeouts, just normal async waiting.
Realtime Updates: Live frontend updates via useRealtimeRun(). Watch generation status change from "Generating..." to "Completed" without any polling.
November 6, 2025 at 5:45 PM
Realtime Updates: Live frontend updates via useRealtimeRun(). Watch generation status change from "Generating..." to "Completed" without any polling.
Batch Triggering: Trigger 3 AI generations in parallel with batchTriggerAndWait(). One line replaces complex coordination logic.
November 6, 2025 at 5:45 PM
Batch Triggering: Trigger 3 AI generations in parallel with batchTriggerAndWait(). One line replaces complex coordination logic.
Our open source projects are designed to teach core concepts. The product image generator demonstrates how to:
→ Batch trigger multiple AI generations in parallel
→ Trigger runs from the frontend and subscribe to updates
→ Pause task execution for webhooks with Waitpoints
Here's how it works ↓
→ Batch trigger multiple AI generations in parallel
→ Trigger runs from the frontend and subscribe to updates
→ Pause task execution for webhooks with Waitpoints
Here's how it works ↓
November 6, 2025 at 5:45 PM
Our open source projects are designed to teach core concepts. The product image generator demonstrates how to:
→ Batch trigger multiple AI generations in parallel
→ Trigger runs from the frontend and subscribe to updates
→ Pause task execution for webhooks with Waitpoints
Here's how it works ↓
→ Batch trigger multiple AI generations in parallel
→ Trigger runs from the frontend and subscribe to updates
→ Pause task execution for webhooks with Waitpoints
Here's how it works ↓
The recent AWS outage reminded us how much even the best providers can fall over sometimes.
→ So we made our deploys more resilient.
You can now deploy locally built Docker images even when our build service is down.
→ So we made our deploys more resilient.
You can now deploy locally built Docker images even when our build service is down.
November 4, 2025 at 5:00 PM
The recent AWS outage reminded us how much even the best providers can fall over sometimes.
→ So we made our deploys more resilient.
You can now deploy locally built Docker images even when our build service is down.
→ So we made our deploys more resilient.
You can now deploy locally built Docker images even when our build service is down.
You can also override the concurrency limits on a queue by using the "Override limit" menu item from an individual queue on the Queues page.
October 30, 2025 at 5:00 PM
You can also override the concurrency limits on a queue by using the "Override limit" menu item from an individual queue on the Queues page.
You can override the concurrency limits on a queue by using the `queues.overrideConcurrencyLimit` and `queues.resetConcurrencyLimit` functions like this:
October 30, 2025 at 5:00 PM
You can override the concurrency limits on a queue by using the `queues.overrideConcurrencyLimit` and `queues.resetConcurrencyLimit` functions like this:
You can now override the concurrency limits on a queue from the API or dashboard.
Very useful if you need to temporarily increase the concurrency for a queue or update the concurrency limits programmatically.
See how it works ↓
Very useful if you need to temporarily increase the concurrency for a queue or update the concurrency limits programmatically.
See how it works ↓
October 30, 2025 at 5:00 PM
You can now override the concurrency limits on a queue from the API or dashboard.
Very useful if you need to temporarily increase the concurrency for a queue or update the concurrency limits programmatically.
See how it works ↓
Very useful if you need to temporarily increase the concurrency for a queue or update the concurrency limits programmatically.
See how it works ↓
✅ Trigger.dev is now SOC 2 Type II compliant.
This security milestone reinforces our commitment to keeping your workflows and data secure, so you can focus on building. 👇
This security milestone reinforces our commitment to keeping your workflows and data secure, so you can focus on building. 👇
October 27, 2025 at 5:30 PM
✅ Trigger.dev is now SOC 2 Type II compliant.
This security milestone reinforces our commitment to keeping your workflows and data secure, so you can focus on building. 👇
This security milestone reinforces our commitment to keeping your workflows and data secure, so you can focus on building. 👇
We've been putting a ton of work into Cloud reliability and performance lately, especially during peak usage:
1️⃣ Implemented a new scheduling strategy
2️⃣ Deployed a custom k8s operator
3️⃣ Configured parallel image pulls and aggressive garbage collection
1️⃣ Implemented a new scheduling strategy
2️⃣ Deployed a custom k8s operator
3️⃣ Configured parallel image pulls and aggressive garbage collection
October 21, 2025 at 4:00 PM
We've been putting a ton of work into Cloud reliability and performance lately, especially during peak usage:
1️⃣ Implemented a new scheduling strategy
2️⃣ Deployed a custom k8s operator
3️⃣ Configured parallel image pulls and aggressive garbage collection
1️⃣ Implemented a new scheduling strategy
2️⃣ Deployed a custom k8s operator
3️⃣ Configured parallel image pulls and aggressive garbage collection
🚀 You can now connect your GitHub repo to Trigger so tasks deploy automatically when you push. No need to manually deploy or use custom CI scripts.
October 16, 2025 at 4:00 PM
🚀 You can now connect your GitHub repo to Trigger so tasks deploy automatically when you push. No need to manually deploy or use custom CI scripts.
✨ Adding AI agents to your app shouldn’t require you to re-architect your product.
With Trigger you start with a foundation that compliments your stack and scales with you. Here are the 6 main pillars we provide ↓
With Trigger you start with a foundation that compliments your stack and scales with you. Here are the 6 main pillars we provide ↓
October 14, 2025 at 4:00 PM
✨ Adding AI agents to your app shouldn’t require you to re-architect your product.
With Trigger you start with a foundation that compliments your stack and scales with you. Here are the 6 main pillars we provide ↓
With Trigger you start with a foundation that compliments your stack and scales with you. Here are the 6 main pillars we provide ↓
When you call out from a task and want to propagate the trace context to your external service, you can use the otel.withExternalTrace function:
October 9, 2025 at 4:06 PM
When you call out from a task and want to propagate the trace context to your external service, you can use the otel.withExternalTrace function:
This is what the entire exported trace looks like in Axiom, showing:
1️⃣ Triggering from your backend
2️⃣ The Trigger task executing
3️⃣ Calls to APIs
4️⃣ Calling from the task out to your backend
5️⃣ Back to the task and the run finishing up
1️⃣ Triggering from your backend
2️⃣ The Trigger task executing
3️⃣ Calls to APIs
4️⃣ Calling from the task out to your backend
5️⃣ Back to the task and the run finishing up
October 9, 2025 at 4:06 PM
This is what the entire exported trace looks like in Axiom, showing:
1️⃣ Triggering from your backend
2️⃣ The Trigger task executing
3️⃣ Calls to APIs
4️⃣ Calling from the task out to your backend
5️⃣ Back to the task and the run finishing up
1️⃣ Triggering from your backend
2️⃣ The Trigger task executing
3️⃣ Calls to APIs
4️⃣ Calling from the task out to your backend
5️⃣ Back to the task and the run finishing up
Also, your observability data isn't locked in, you can export traces wherever you need them.
In this example we're exporting to Axiom
In this example we're exporting to Axiom
October 9, 2025 at 4:06 PM
Also, your observability data isn't locked in, you can export traces wherever you need them.
In this example we're exporting to Axiom
In this example we're exporting to Axiom
Get distributed tracing for your dependencies, with automatic spans for every query and request.
In this example we're adding Prisma and OpenAI instrumentation. There is a huge library of instrumentations you can easily add to your projects.
In this example we're adding Prisma and OpenAI instrumentation. There is a huge library of instrumentations you can easily add to your projects.
October 9, 2025 at 4:06 PM
Get distributed tracing for your dependencies, with automatic spans for every query and request.
In this example we're adding Prisma and OpenAI instrumentation. There is a huge library of instrumentations you can easily add to your projects.
In this example we're adding Prisma and OpenAI instrumentation. There is a huge library of instrumentations you can easily add to your projects.
Developers need to be able to easily debug when things go wrong.
We use @opentelemetry (OTEL) for our run logs, giving you a lot of detailed info about your tasks. It also allows us to support:
⚗️ Adding additional instrumentation
🛩️ Exporting your logs and traces to other external tools
⬇️
We use @opentelemetry (OTEL) for our run logs, giving you a lot of detailed info about your tasks. It also allows us to support:
⚗️ Adding additional instrumentation
🛩️ Exporting your logs and traces to other external tools
⬇️
October 9, 2025 at 4:06 PM
Developers need to be able to easily debug when things go wrong.
We use @opentelemetry (OTEL) for our run logs, giving you a lot of detailed info about your tasks. It also allows us to support:
⚗️ Adding additional instrumentation
🛩️ Exporting your logs and traces to other external tools
⬇️
We use @opentelemetry (OTEL) for our run logs, giving you a lot of detailed info about your tasks. It also allows us to support:
⚗️ Adding additional instrumentation
🛩️ Exporting your logs and traces to other external tools
⬇️
Their solution: a kan-ban style triage agent that acts like an engineering manager. It takes a queue of work (features, bugs, refactors), breaks it down, assigns tasks to specialized coding agents, monitors progress, and consolidates the results.
October 7, 2025 at 4:30 PM
Their solution: a kan-ban style triage agent that acts like an engineering manager. It takes a queue of work (features, bugs, refactors), breaks it down, assigns tasks to specialized coding agents, monitors progress, and consolidates the results.
Capy is the AI software engineer that ships dozens of features in parallel.
Rather than the usual process of having to run many concurrent Claude sessions, alt-tabbing between terminals, and manually checking progress, the Capy team have re-imagined the AI agent DX from the ground up.👇
Rather than the usual process of having to run many concurrent Claude sessions, alt-tabbing between terminals, and manually checking progress, the Capy team have re-imagined the AI agent DX from the ground up.👇
October 7, 2025 at 4:30 PM
Capy is the AI software engineer that ships dozens of features in parallel.
Rather than the usual process of having to run many concurrent Claude sessions, alt-tabbing between terminals, and manually checking progress, the Capy team have re-imagined the AI agent DX from the ground up.👇
Rather than the usual process of having to run many concurrent Claude sessions, alt-tabbing between terminals, and manually checking progress, the Capy team have re-imagined the AI agent DX from the ground up.👇
🌍 Multi-region workers let you to execute your tasks much closer to your customers. This gives you:
⚡️ Lower latency for regional users
🇪🇺 Access to EU-only APIs or IPs
🎛️ You can also override regions per task:
⚡️ Lower latency for regional users
🇪🇺 Access to EU-only APIs or IPs
🎛️ You can also override regions per task:
October 2, 2025 at 4:00 PM
🌍 Multi-region workers let you to execute your tasks much closer to your customers. This gives you:
⚡️ Lower latency for regional users
🇪🇺 Access to EU-only APIs or IPs
🎛️ You can also override regions per task:
⚡️ Lower latency for regional users
🇪🇺 Access to EU-only APIs or IPs
🎛️ You can also override regions per task:
When AI agents or workflows call databases or APIs, two things can become really important:
→ having static IPs so you can connect to prod DBs, enterprise APIs etc.
→ running in the right geographical region for low latency or compliance
Trigger now supports both. Here’s how they work 🧵
→ having static IPs so you can connect to prod DBs, enterprise APIs etc.
→ running in the right geographical region for low latency or compliance
Trigger now supports both. Here’s how they work 🧵
October 2, 2025 at 4:00 PM
When AI agents or workflows call databases or APIs, two things can become really important:
→ having static IPs so you can connect to prod DBs, enterprise APIs etc.
→ running in the right geographical region for low latency or compliance
Trigger now supports both. Here’s how they work 🧵
→ having static IPs so you can connect to prod DBs, enterprise APIs etc.
→ running in the right geographical region for low latency or compliance
Trigger now supports both. Here’s how they work 🧵
Considering a new job role 👀? We've just opened up new engineering positions and would love to hear from you if you are a:
→ Support Engineer
→ Senior Backend Engineer
Apply below ↓
→ Support Engineer
→ Senior Backend Engineer
Apply below ↓
September 30, 2025 at 9:00 PM
Considering a new job role 👀? We've just opened up new engineering positions and would love to hear from you if you are a:
→ Support Engineer
→ Senior Backend Engineer
Apply below ↓
→ Support Engineer
→ Senior Backend Engineer
Apply below ↓
The new middleware system wraps every lifecycle hook and lets you share state via 'locals'. Ideal for managing database clients that should disconnect while a run is waiting:
September 26, 2025 at 3:00 PM
The new middleware system wraps every lifecycle hook and lets you share state via 'locals'. Ideal for managing database clients that should disconnect while a run is waiting:
If you create an 'init.ts' file at the root of your trigger directory, it will be automatically loaded when a task is executed. This is useful if you want to register global lifecycle hooks, or initialize a database connection, etc.
September 26, 2025 at 3:00 PM
If you create an 'init.ts' file at the root of your trigger directory, it will be automatically loaded when a task is executed. This is useful if you want to register global lifecycle hooks, or initialize a database connection, etc.