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
③ Modern Mode (Prisma 7+)
The future is here. Prisma 7's new prisma-client removes Rust dependencies entirely, enabling faster installs and simpler deployments.
The future is here. Prisma 7's new prisma-client removes Rust dependencies entirely, enabling faster installs and simpler deployments.
November 19, 2025 at 3:00 PM
③ Modern Mode (Prisma 7+)
The future is here. Prisma 7's new prisma-client removes Rust dependencies entirely, enabling faster installs and simpler deployments.
The future is here. Prisma 7's new prisma-client removes Rust dependencies entirely, enabling faster installs and simpler deployments.
② Engine-Only Mode (Prisma 6.7+ with custom output)
For teams using Prisma 6.7+ with a custom output directory but still using the Rust-based engine. This mode gives you control over the client generation process, but will take care of installing the engine binaries for you when deploying.
For teams using Prisma 6.7+ with a custom output directory but still using the Rust-based engine. This mode gives you control over the client generation process, but will take care of installing the engine binaries for you when deploying.
November 19, 2025 at 3:00 PM
② Engine-Only Mode (Prisma 6.7+ with custom output)
For teams using Prisma 6.7+ with a custom output directory but still using the Rust-based engine. This mode gives you control over the client generation process, but will take care of installing the engine binaries for you when deploying.
For teams using Prisma 6.7+ with a custom output directory but still using the Rust-based engine. This mode gives you control over the client generation process, but will take care of installing the engine binaries for you when deploying.
① Legacy Mode (Prisma 6.x and earlier)
Use this when you're running Prisma 6.x or earlier with the standard prisma-client-js provider.
Use this when you're running Prisma 6.x or earlier with the standard prisma-client-js provider.
November 19, 2025 at 3:00 PM
① Legacy Mode (Prisma 6.x and earlier)
Use this when you're running Prisma 6.x or earlier with the standard prisma-client-js provider.
Use this when you're running Prisma 6.x or earlier with the standard prisma-client-js provider.
Our Prisma Extension has been completely redesigned to support Prisma 7's new architecture, while maintaining full backward compatibility. Whether you're using the traditional provider or the new Rust-free client architecture, we've got you covered.
↓ Our 3 modes for every deployment strategy
↓ Our 3 modes for every deployment strategy
November 19, 2025 at 3:00 PM
Our Prisma Extension has been completely redesigned to support Prisma 7's new architecture, while maintaining full backward compatibility. Whether you're using the traditional provider or the new Rust-free client architecture, we've got you covered.
↓ Our 3 modes for every deployment strategy
↓ Our 3 modes for every deployment strategy
→Dashboard visibility:
Streams show up as first-class citizens now. You can inspect chunks in order, replay them, and debug long-running tasks without digging through logs or guessing what happened.
Streams show up as first-class citizens now. You can inspect chunks in order, replay them, and debug long-running tasks without digging through logs or guessing what happened.
November 18, 2025 at 5:15 PM
→Dashboard visibility:
Streams show up as first-class citizens now. You can inspect chunks in order, replay them, and debug long-running tasks without digging through logs or guessing what happened.
Streams show up as first-class citizens now. You can inspect chunks in order, replay them, and debug long-running tasks without digging through logs or guessing what happened.
→Pipe from your tasks:
Tasks can push chunked output directly into a stream without blocking:
Tasks can push chunked output directly into a stream without blocking:
November 18, 2025 at 5:15 PM
→Pipe from your tasks:
Tasks can push chunked output directly into a stream without blocking:
Tasks can push chunked output directly into a stream without blocking:
→React integration: useRealtimeStream hook
Frontend consumption is much more straightforward:
Frontend consumption is much more straightforward:
November 18, 2025 at 5:15 PM
→React integration: useRealtimeStream hook
Frontend consumption is much more straightforward:
Frontend consumption is much more straightforward:
→ Define your streams:
You define a stream once and use it everywhere with full type safety built-in: No per-run setup, no ad-hoc keys, no guessing the shape of chunks later.
You define a stream once and use it everywhere with full type safety built-in: No per-run setup, no ad-hoc keys, no guessing the shape of chunks later.
November 18, 2025 at 5:15 PM
→ Define your streams:
You define a stream once and use it everywhere with full type safety built-in: No per-run setup, no ad-hoc keys, no guessing the shape of chunks later.
You define a stream once and use it everywhere with full type safety built-in: No per-run setup, no ad-hoc keys, no guessing the shape of chunks later.
The core change: unlimited chunks, unlimited active streams, longer retention, and 300 MiB max size. v1 had tiny caps everywhere; v2 removes them:
November 18, 2025 at 5:15 PM
The core change: unlimited chunks, unlimited active streams, longer retention, and 300 MiB max size. v1 had tiny caps everywhere; v2 removes them:
🧵 Introducing Realtime Streams v2, built with s2.dev, designed for unlimited, reliable, type-safe streaming.
↓ Read about what we've improved, and how to upgrade.
↓ Read about what we've improved, and how to upgrade.
November 18, 2025 at 5:15 PM
🧵 Introducing Realtime Streams v2, built with s2.dev, designed for unlimited, reliable, type-safe streaming.
↓ Read about what we've improved, and how to upgrade.
↓ Read about what we've improved, and how to upgrade.
Pallet are on a mission to revolutionize global logistics.
Their AI agent copilot replaces legacy manual freight workflows parsing messy data, reconciling systems, and automating transport operations across the world.
↓ Read their customer story
Their AI agent copilot replaces legacy manual freight workflows parsing messy data, reconciling systems, and automating transport operations across the world.
↓ Read their customer story
November 13, 2025 at 8:47 PM
Pallet are on a mission to revolutionize global logistics.
Their AI agent copilot replaces legacy manual freight workflows parsing messy data, reconciling systems, and automating transport operations across the world.
↓ Read their customer story
Their AI agent copilot replaces legacy manual freight workflows parsing messy data, reconciling systems, and automating transport operations across the world.
↓ Read their customer story
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: