Blog

Upgrading a 56TB database that's growing at 250GB per day with (nearly) no downtime

We had to upgrade our 56TB Aurora Postgres cluster by 31 July without taking Trigger.dev down. Instead of moving the database, we made the problem smaller: new runs and the control plane went to PlanetScale, and the old runs stayed behind.

Customize the runs list with columns and smart columns

Show, hide, and reorder the columns on the runs list, and add smart columns that pull a value out of a run's payload, metadata, or output by JSON path. Your layout lives in the URL, so a view is bookmarkable and shareable.

Set up Trigger.dev with your AI agent

Copy a project-aware prompt that connects your coding agent to Trigger.dev's MCP server, with a CLI fallback and live setup progress.

Multiple API keys per environment

Create as many keys as you need per environment, each with its own access scope, optional task restrictions, and an expiration date. Revoke any one instantly without rotating the rest.

Bulk actions from the SDK

Cancel or replay runs matching a filter straight from your backend code with runs.bulk.replay() and runs.bulk.cancel(), then poll for progress.

AI prompts: code-defined, versioned, overridable

Your prompts live in code, versioned on every deploy. Change the text or model from the dashboard without redeploying, and trace every generation back to the exact version that produced it.

The health report: diagnose a project in one command

A server-computed verdict on whether work is starting, whether the runs that start are succeeding, and whether your telemetry is fresh, each with a suggested next action. Run it from the CLI, the get_report MCP tool, or the API.

MCP server gets agent chat, prompt management, and reports

Your coding assistant can now chat with your deployed agents, manage prompt versions, query your run data with TRQL, and pull a health report for any environment.

Introducing chat agent

Every conversation gets its own stateful machine that sticks around for the entire chat, sleeping and waking when needed.

LLM observability, built in

Every LLM call your tasks make is recorded with its model, cost, tokens, and latency. See the whole workload on a dashboard, open any single call in the run trace, and query all of it yourself.

SCIM directory sync for SSO

If your team signs in with SSO, member provisioning is now automatic. Assign someone to Trigger.dev in your identity provider and they're added to your org; unassign them and their access is revoked.

Favorite pages and customize your sidebar

Pin any page to a Favorites section in the side menu, then make the sidebar yours: rename favorites, hide items you don't use, and reorder everything.

New region: US West (Oregon)

Run your tasks in AWS US West (Oregon). A third region alongside US East and Europe, for low latency to West Coast services and APIs.

Infisical integration

Sync secrets from Infisical straight into your Trigger.dev environment variables. Keep Infisical as your source of truth, with no build step or CLI required.

Higher Realtime connection limits

Paid plans now include more simultaneous Realtime connections: Hobby moves to 150 and Pro to 1,000.

Dashboard UI updates

A calmer redesigned sidebar, a dedicated overview page for every task, new task-type icons with filtering, a relocated Test button, and 24-hour activity charts.

Dev branches

Run several local dev sessions at once without their runs colliding. Each dev branch is isolated with its own dashboard, so parallel git worktrees and coding agents stay out of each other's way.

Billing limits & spend alerts

Set a spend cap on your organization. Reach it and we pause execution across every environment, so new runs keep queuing but stop running, and a runaway job can't blow past your budget.

Runs list and logs degraded

For several hours on June 30, the dashboard runs list and logs were degraded while your runs kept executing normally. Here's what happened, how we recovered, and what we're changing so it can't happen again.

Incident report on June 22, 2026

On June 22–23, 2026, both of our regions had spells where they couldn't start new runs, and recovery took the best part of a day. Here's what happened, what it cost, and what we're changing so it can't happen the same way again.

Trigger.dev is now HIPAA ready

Trigger.dev Cloud now meets HIPAA Business Associate requirements. Sign a BAA and run workloads that process Protected Health Information on our managed infrastructure.

Runs page updates Live

Runs page now updates in place: statuses change live, a banner flags new runs, and parent tooltips show child-run breakdowns.

Powering Cal.com's core booking engine with AI scans, calendar syncs, and durable async fan-out tasks

Morgan Vernay, Software Engineer at Cal.com, shares how their team runs millions of background tasks every month on Trigger.dev: booking side effects, AI phishing detection, fraud analysis, and Google/Microsoft Graph calendar syncing.

Errors: find and fix your bugs faster

Quickly track down what’s causing your runs to fail with error alerts. Then bulk replay when you’ve shipped the fix.

AWS PrivateLink: connect your AWS resources without exposing them

Reach private databases, caches, and APIs from your tasks over AWS PrivateLink. No public endpoints, no IP allowlists, no VPN. Set it up manually, with AI, or with a generated Terraform script.

Input streams: send data into running tasks

Bidirectional task communication. Send typed data into running tasks from your backend or frontend, with four receiving patterns from suspending (frees compute) to non-blocking.

We ditched worktrees for Claude Code. Here's what we use instead

Git worktrees solve code isolation but create infrastructure nightmares. We teach Claude Code to use GitButler's CLI directly, splitting one session's work across multiple branches without duplicating databases, Redis, or dev servers.

Why we replaced Node.js with Bun for 5x throughput

How we took our warm start service from 2,099 req/s on Node + SQLite to 10,700 req/s on a compiled Bun binary, and found a subtle memory leak that only exists in Bun's HTTP model.

10 Claude Code Tips You Didn't Know

Go beyond the chat interface. 10 lesser-known Claude Code patterns: session forking, parallel worktrees, multi-agent orchestration, and headless CI/CD.

Vercel integration

Connect your Vercel project to Trigger.dev and never run a manual deploy command again. Automatic deploys, env var sync, and atomic deployments

How we give every user SQL access to a shared ClickHouse cluster

A deep dive into TRQL — the SQL-like language behind Query. How we parse, validate, and compile queries to secure, tenant-safe ClickHouse SQL.

Query & Dashboards: analytics for your Trigger.dev data

Analyze your data using SQL for one-off queries or build custom dashboards with charts and tables.

Skills: teaching AI agents to act consistently

Skills teach AI agents how to do specific tasks consistently. Learn how they work, what's inside them, and how agents discover and load them.

How Tierly builds AI-powered pricing intelligence using Trigger.dev

Gerasimos Plegas, Founder at Tierly, shares how they orchestrate complex multi-step AI workflows for competitive pricing analysis using Trigger.dev.

Trigger.dev agent skills for AI coding assistants

Install our official agent skills to teach any AI coding assistant best practices for writing tasks, agents, and workflows.

AI SDK 6 support

Full compatibility with Vercel AI SDK 6 alongside existing 4 and 5 support.

New limits page

New limits page to manage concurrency limits for your projects.

Improved date and time filtering in the dashboard

Redesigned date picker with visual calendar navigation, time precision controls, and quick preset options for faster run filtering.

Debounced task runs

Consolidate multiple triggers into a single execution by debouncing task runs with a unique key and delay window.

Batch trigger improvements

Support for larger payloads, streaming ingestion, and fair processing with per-environment concurrency limits.

Trigger.dev raises $16M Series A

We've raised a $16M Series A led by Standard Capital, with participation from Y Combinator.

Adjacent task runs with ease

Tired of going back and forth between runs list and run details? Now you can easily navigate to the previous or next run directly from the run details page.

Faster cold starts with zstd compression

We've enabled zstd compression by default for deployment images, improving cold start times when images need to be pulled to worker nodes.

How GovSignals is solving government procurement using Trigger.dev

Conner Aldrich, Co-Founder & CTO at GovSignals, shares how his team uses Trigger.dev to power large-scale AI ingestion, high-compute proposal generation, and a dual-deployment model spanning both Trigger cloud and a fully self-hosted, FedRAMP High environment.

Login with Google

You can now create an account or login to Trigger.dev with your Google account.

Deployments with native builds

Deploy your tasks with native builds using our own build infrastructure.

Bun runtime upgraded to v1.3.3

We've upgraded the Bun runtime for deployments to v1.3.3, bringing improved performance and the latest features to your Bun-based tasks.

Higher concurrency limits and lower prices

We've increase the included concurrency on every plan, including Free. We've also dropped the price for extra concurrency and made it self-serve.

Prisma 6 & 7 support

Complete redesign of our Prisma extension with three modes to support Prisma 6.x, 7.x, and everything in between.

Realtime Streams v2

Introducing Realtime Streams v2: Unlimited, Reliable, and Type-Safe

Accelerating global logistics workflows using AI copilots

Karl Kaiser, Engineer at Pallet, shares how his team uses Trigger.dev to power their logistics AI copilot, automating the exchange of shipment and transport data between multiple systems in real-time.

Deployments logs in the dashboard

Deployment logs are now streamed to the dashboard in realtime.

Deployments with local builds

Build your tasks locally and deploy them to Trigger.dev cloud.

SOC 2 Type II compliance

Trigger.dev is now officially SOC 2 Type II compliant.

Logs moved to ClickHouse

Logs are now stored in ClickHouse for faster performance and better scalability.

Override concurrency limits

Override the concurrency limits on a queue from the API or the dashboard.

GitHub integration

Connect a GitHub repo to your project and your tasks deploy automatically on every push.

How we built a kanban-style triage agent for managing coding agents

Justin Sun, Co-founder and CTO of Capy, explains how they use Trigger.dev's workflow engine to run an intelligent triage agent that coordinates many concurrent coding agents in completing end-to-end engineering tasks.

Massive infrastructure scale and reliability improvements

Expanded capacity and smarter scaling for more reliable performance across every region.

Optimal workload scheduling for better availability

Improved startup performance and reliability for Medium and Large machines, especially during peak usage.

Jump to root or parent run

Navigate to parent or root runs using the new links on the run page.

Our roadmap for the next 3 months and beyond

After shipping v4 GA, we're focusing on making Trigger.dev the best platform for AI agents. Here's our 3-month+ roadmap: GitHub and Vercel integrations, sub-500ms MicroVM cold starts, improved logging with ClickHouse, an Agent Toolkit, and advanced metrics.

Powering HeroUI Chat's complex deployment pipeline with Trigger.dev

Junior Garcia, founder of HeroUI, explains how Trigger.dev powers the complex deployment pipeline for HeroUI Chat, their AI-powered platform that lets anyone build applications using atomic React components.

Official MCP server & agent rules

We've created an official MCP server and agent rules for Trigger.dev that makes getting setup, developing, and debugging your tasks a breeze.

Agent rules

Comprehensive guidance for AI tools to generate better Trigger.dev code with best practices and patterns.

Official MCP Server

Our official Trigger.dev MCP server for project initialization, task triggering, deployment, debugging, etc when using AI assistants.

4x concurrency, static IPs and multi-region workers powered by AWS

Get 4x more concurrency on paid plans and static IPs with our new AWS regions, starting with us-east-1 and eu-central-1.

Multi-region workers

Execute tasks closer to your users with our new multi-region workers.

Static IPs

Connect to production databases and enterprise APIs that require IP allowlisting.

Bulk actions

Bulk cancel and replay any number of runs using filters.

Improved bulk actions

Cancel or replay runs in bulk, from a handful to millions at once.

Preview branches

Create isolated environments for each of your git branches.

Ray.so Trigger.dev dark / light themes

Generate beautiful code images for your blog posts, social media posts, and docs.

Trigger.dev v4 GA

This is our most significant performance and developer experience upgrade yet, built on our new Run Engine.

Wait for HTTP callback

Save on compute costs by pausing runs until third-party services complete their work with webhook callbacks.

Waitpoints

Pause task execution for human-in-the-loop approval, external service callbacks, and conditional logic.

Trigger.dev v4 is now GA

Our most significant performance and developer experience upgrade yet, built on our new Run Engine 2.

Dashboard improvements

Environment-scoped pages, improved project switcher, real-time status, and dedicated queues page.

Bun and Node.js 22 support

Support for three runtime options: Node.js 21.7.3, Node.js 22.16.0, and Bun 1.2.18.

Billing alerts

Get notified when your usage exceeds certain thresholds.

How to reduce your Trigger.dev spend

We've added a new guide to our docs to help you reduce your Trigger.dev spend.

Mastra agents with memory full stack example

AI run filtering in the dashboard

How we built a real-time service that handles 20,000 updates per second

We process 20,000 run updates per second and 500GB of data daily using Postgres replication slots and ElectricSQL. Here's why we chose this over WebSockets and how we solved the hard problems of authentication, rate limiting, and caching.

Multi-factor authentication

How Magic Patterns migrated 200k monthly jobs to Trigger.dev in one day

Alex Danilowicz, Co-founder of Magic Patterns, shares why they migrated their critical background jobs to Trigger.dev from their unreliable self-hosted solution.

Increased OTel attribute limits

v4 full-stack example projects

Specify columns to exclude from Realtime streams

Self-hosting Trigger.dev v4 using Kubernetes

Self-hosting Trigger.dev v4 using Kubernetes

You can now self-host Trigger.dev v4 using Kubernetes. This adds to the existing Docker option.

Self-hosting Trigger.dev v4 using Docker

You can now self-host Trigger.dev v4 using Docker. This is a big step towards making Trigger.dev more accessible to everyone.

v4: Faster warm starts with processKeepAlive

Self-hosting Trigger.dev v4 using Docker

Preview branches

Isolated environments for each of your git branches.

Automating security compliance using AI agents

Lewis Carhart, Founder at Comp AI, shares how they use Trigger.dev to automate evidence collection at scale, powering their open source, AI-driven compliance platform.

Telemetry exporters

Export traces and logs to external services

Run cleanup using onCancel hook

Define an onCancel hook that is called when a run is canceled

AI in the dashboard and CLI

We've added an AI help widget to the dashboard and CLI.

Metrics preview

Secret environment variables

Icon: revolutionizing video ad creation with Trigger.dev

Caleb Tan, Founding Engineer at Icon, shares how they use Trigger.dev to process thousands of videos concurrently, powering their AI-driven ad creation platform that allows global brands to generate full video ads in minutes.

Delete a project

We've added a new way to delete a project.

Trigger.dev v4 beta

Today we're excited to launch our v4 beta, that includes Run Engine 2. There are significant performance improvements like warm starts, a totally revamped dashboard, human in the loop tokens, and more.

Trigger.dev v4 beta

How to write great Cursor Rules

What we learned writing a Cursor Rules file for Trigger.dev tasks, and 10 tips for writing your own

New guides for using Prisma and Trigger.dev in a Turborepo monorepo

We've added new guides to our docs and Examples GitHub repo.

Cursor rules

Use Cursor rules to automatically write your Trigger.dev tasks.

How Trigger.dev powers Huntr's internal AI agents

Sam Wright, Head of Operations and Partnerships at Huntr, explains how they use Trigger.dev to build AI agents for content generation and internal tooling.

Atomic deploys

Deploying your tasks atomically with your app using two-phase deploys, now on Trigger.dev

Python extension

Execute python scripts in your tasks with the new Python extension.

Refreshed run timeline

The timeline on the run page now displays more information about the run start times.

SvelteKit plugin

Trigger.dev now has a SvelteKit plugin, developed by a member of the community.

Alert webhooks

Receive a webhook alert when runs fail, deploys fail, or deploys succeed.

How MagicSchool AI develops insights using Trigger.dev

Ben Duggan, Staff Software Engineer at MagicSchool AI, shares how they use Trigger.dev and Vercel's AI SDK to extract insights from millions of student interactions.

Retry out of memory (OOM) errors on a larger machine

You can now automatically retry using a larger machine if you hit an OOM error.

Building effective AI agents with Trigger.dev

Learn how to build AI agents with Trigger.dev, and how they can help you build more resilient systems.

Example projects repo

We've added a new example projects GitHub repo to help you get started with Trigger.dev.

Midday's Automated Bank Synchronization, powered by Trigger.dev

Pontus Abrahamsson, CEO and co-founder of Midday, deep dives into how they use Trigger.dev to reliably sync bank transactions for their 11,500+ customers.

Update parent & root metadata

You can now update the metadata of parent and root runs from child runs.

Everything we launched during launchweek[0]

A recap of all the new features we announced during our first launch week.

Run Engine 2.0 (alpha)

Warm starts, multi-region workers, self-hosted workers, and new waitpoints.

Batch processing

A bunch of improvements to our batch processing system, including new limits and dashboard visibility.

Trigger from the frontend

Trigger.dev now supports triggering tasks from the frontend.

Build extensions

Install system packages, like FFmpeg and Puppeteer, and modify the build process.

Realtime goes GA

Keep your users updated with real-time task progress. Now with LLM streaming support and increased limits.

New run filters

Filter the runs table with IDs, a custom date range, and hide child runs.

How NUMI uses Trigger.dev to build resilient systems

Agree Ahmed, CEO of NUMI, shares his story of how they have re-architected their code to use Trigger.dev, and how it has changed the way they think about building complex distributed systems.

Example tasks using Fal.ai and Realtime

Create a Realtime task using Fal.ai that displays the task progress to the user on the frontend.

Real-time PDF conversion with Trigger.dev: Papermark's success story

Marc Seitz, co-founder of Papermark, runs through how they have used Trigger.dev to build a real-time PDF conversion service, with thousands of conversions successfully processed per month.

Realtime beta

Subscribe to realtime updates for your tasks, from your backend or frontend

How to scrape a website using Browserbase, Puppeteer, OpenAI and Trigger.dev

Learn how to scrape the top 3 articles from Hacker News and email yourself a summary every weekday at 9AM.

Trigger anything from a database change using Supabase with Trigger.dev

Learn how to use Trigger.dev with Supabase to create event-driven workflows. We'll cover triggering tasks from Edge Functions, performing database operations, and building a video processing pipeline with AI transcription.

Max duration

Set a maximum duration for a task to run, and automatically cancel it if it exceeds this limit.

6 more example tasks to copy paste

Better navigation between runs

Quickly navigate between parent, root and triggered runs using the new links in the run inspector.

12 example tasks to copy paste

Run metadata

Attach a small amount of data to a run and update it as the run progresses.

From beta to 3.0: Trigger.dev v3 reaches GA

Trigger.dev v3 is now out of beta and at v3.0.0. This release includes a new CLI, a revamped build system, and more.

3.0 is here! 🎉

Trigger.dev v3 is now GA at v3.0.0. This release includes a new CLI, a revamped build system, and more.

Alerts for failed runs

We've added alerts when runs completely fail. Previously, we alerted you when an attempt had failed which wasn't actually that useful.

Next.js quickstart guide

Get started with Trigger.dev and Next.js App Router, Pages Router or Server Actions with our quickstart guide.

How we stopped xmin horizon blocking Postgres vacuuming: a deepdive

We encountered an issue with xmin horizon blocking Postgres vacuuming, causing system slowdowns. Learn about our troubleshooting process, the solution we implemented, and our steps to prevent similar incidents in the future.

Better log retention

We've increased the log retention period for Hobby and Pro plans, as well as made the run page more useful when your logs are deleted.

Trigger.dev v2 end-of-life and how to upgrade to v3

Trigger.dev v2 will reach end-of-life on January 31st 2025. Here's what you need to know and how to migrate to v3.

Run inspector improvements

The redesigned run page highlights the most important information, has more detail with tabs, and allows replaying with a different payload.

Add tags to your runs

You can add tags to your runs then filter them using the dashboard or SDK.

Declare cron on your tasks

You can now add cron patterns directly on your tasks – they'll sync in development and deployment.

Trigger.dev v3 is now open to everyone

Today, I'm excited to announce that Trigger.dev v3 is now open to everyone. No more waitlist!

Automatic ratelimit retries

How we improved automatic ratelimit retries when rate limits are exceeded.

Task cancellation propagation

Task delays and TTLs

How we tamed Node.js event loop lag: a deepdive

We recently experienced some service degradation and downtime due to event loop lag in our Node.js service. Here's how we diagnosed and fixed the issue.

Improved typesafe task triggering

Scheduled task timezone support

Rollback deployments

runs.get() & runs.list()

Major v3 reliability improvements

Environment variables SDK

New v2 projects are disabled

Bulk replaying and canceling

Alerts

Run filtering

Bulk environment variables

v3 Staging

New tasks dashboard

New package release: @v3.0.0-beta.15

Scheduled tasks for v3

Trigger.dev v3 Developer Preview is now available

Today you can get early access to v3. No timeouts, easy reliability and a new dashboard for finding and fixing bugs.

Trigger.dev v3: Durable Serverless functions. No timeouts.

Write regular code and get durability with no timeouts. This means writing long-running tasks is far easier than before.

Trigger.dev raises $3M

Trigger.dev, the open source background jobs framework, has today announced a $3M seed round.