In Review
183Under consideration
Self-hosted workers
You can fully self-host Trigger.dev. This is a really good option in lots of situations if you’re experienced with setting up and managing infrastructure. Another option would be if we offered self-hosted workers. You would host them inside your own cloud account (or on-prem) and they would connect to the Trigger.dev cloud. The pricing model for this is TBD, but it would probably be a combination of a cost per connected worker server and an invocation cost that is higher than the managed worker one.
CPU and Memory graphs on the run page
It’s currently difficult to diagnose performance issues. It would be useful to have graphs on the run page. This would also make it possible to find memory leaks Currently you have to use Node functions to log out the memory: const memory = process.memoryUsage(); logger.log(“Memory usage”, memory);
Event triggers
Please reintroduce the events feature in V3, similar to what was available in V2. Trigger with an event name and payload A task can subscribe to a named event with a filter (it will only create a run if the filter matches) A single event can trigger many tasks if it matches many
Full Python support
This feature will follow on from our Python extension to allow full Python support in Trigger.dev.
CPU and memory optimised machines
Currently all our machines are evenly balanced between CPU or RAM (or some of them have double the RAM than vCPU). We could add a set of CPU-optimized machines (e.g. 1vCPU + 0.25GB RAM) and memory optimized machines (e.g. 0.25vCPU + 1GB RAM). What do people think? What combos would be useful?
E2E and unit testing utilities
Would be cool to unit test: have a way to unit test specific tasks and mock other other tasks (that are used within the tested task) e2e test: have a way to spin up a instance for e2e tests locally (programmatically for jest/bun testing) and tear it down after tests ran
Asia worker region
Workers in Asia will reduce the latency when accessing your regional resources from your tasks.
Run Trigger.dev in dev mode offline
Trigger.dev currently does not support “offline” dev mode, where you can run tasks without an internet connection. Please let us know if this is a feature you want/need. This would be great to have, and would compliment a Supabase/Next.js stack nicely. I am online 99% of the time but it would be great to develop fully locally in that last 1% where I’m at an airport or in a cafe with bad wifi.
Filter runs by payload value
I recently tried to find a run by filtering on a value of the payload but I couldn’t figure out how. It would be great to be able to do something like “get be runs where task = X and payload.customerId = Y”
Simple support for Observability tools (e.g. Sentry, DataDog, Axiom, etc)
These tools typically require code to be inserted extremely early in the code execution order because they automatically instrument other modules. It might be technically possible to write an ESBuild plugin that works with Trigger.dev (we support those via extensions) but it won’t be trivial. We should add an easy way to use these tools.
Planned
3Committed and queued
Rate Limiting / throttling
We currently support setting a concurrencyLimit on a task, or on a queue that you create. This can also be used with a concurrencyKey to have per-user queues: https://trigger.dev/docs/queue-concurrency Sometimes instead of concurrency you want to limit using a rate. For example, 10/minute, 1/second. This is especially useful when using APIs that have rate limits. We should support this with a per-tenant key like we do for concurrency.
Simulate CPU and Memory Limits on Dev Environments
Hosted remote MCP server for cloud-based agents
Please provide an official, cloud-hosted Trigger.dev MCP endpoint that cloud-based agents can connect to directly. The current MCP server runs locally through the CLI, which makes it harder to integrate into a cloud-agent setup. A hosted endpoint would let us: Connect cloud agents without running and managing a local MCP server. Access the latest Trigger.dev MCP tools.
In Progress
1Actively being built
Completed
54Recently shipped
Vercel integration
Right now you can have a great experience with Trigger.dev and Vercel by using our Preview branches and our syncVercelEnvVars extension. — An official Vercel integration would do those two things but with less setup: Sync environment variables from Vercel to Trigger.dev. Create preview branches on Trigger.dev.
Incoming webhook trigger
In the dashboard you each task would have a URL for each of your environments. Then you can use this URL in 3rd party products. Any data in the body of the request to that URL would come through to the task as the payload.
HIPAA compliance
Support log drains
Support for logs to be sent from Trigger.dev to 1+ other destinations. We would probably start with an HTTP POST request with a JSON body, similar to how Supabase do this.
Isolated dev sessions for multiple local trigger dev instances
Right now, multiple trigger dev instances for the same project share one queue, so any instance can run any task and they end up “stealing” each other’s work. The ask is to support something like preview branches, but for the dev environment: separate dev sessions (e.g. a session id or “dev branch”) so each local instance only runs tasks triggered from that same session. That would let you run several work trees or app copies in parallel (e.g. with Codex/Claude) without tasks from one ending up running in another.
Specify a smaller concurrencyKey concurrency limit
This would allow for being able to have a concurrency limit on the entire queue, lets say 10, but each concurrency key only gets lets say 1 at a time. So the queue would never been executing more than 10 at once, and each concurrency key would only ever execute 1 in parallel. See this real world use-case: https://x.com/euboid/status/1929470623191101613
Role Based Access Controls (user permissions)
At the moment all users in your team are admins, which means they can all view the API keys, deploy, add/remove team members, and create/edit/view/delete environment variables. We need to add a permissions system so this can be configured by admins.
OIDC support
Add OpenID Connect (OIDC) support so Trigger.dev jobs can obtain short-lived, workload-scoped credentials from cloud providers and secret managers at runtime, instead of relying on long-lived static secrets. This enables securely pulling secrets (e.g. from AWS, GCP, Azure, Vault) using identity-based access tied to the job or environment, reducing secret sprawl, simplifying rotation, and improving security posture for production workloads.
Filter by run type (schedule/task) or hide schedule runs
If one has many CRON schedules that run every X minutes, they will have their Runs section cluttered with a lot of those schedule originated runs. It would be beneficial to either have a toggle to hide those type of tasks or add an additional filter.
Multiple API Keys with Granular Access Control for Endpoints and Tasks
I would like to be able to create multiple API keys and configure access permissions on a per-endpoint or per-task basis. Currently, there is only one API key per project, but from a security perspective, it would be much better to be able to create and distribute API keys with permissions limited to specific tasks only when integrating with external systems via API. This feature would allow us to follow the principle of least privilege by granting minimal necessary access rights to each external integration, thereby improving overall security posture.