In Review

Planned

In Progress

Completed

Main Roadmap

You can <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://trigger.dev/docs/open-source-self-hosting">fully self-host Trigger.dev</a>.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 <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Trigger.dev">Trigger.dev</a> 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.

Self-hosted workers

mattaitken

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:<pre><code>const memory = process.memoryUsage();
logger.log(“Memory usage”, memory);</code></pre>

CPU and Memory graphs on the run page

Please reintroduce the events feature in V3, similar to what was available in V2. <ul><li>Trigger with an event name and payload</li><li>A task can subscribe to a named event with a filter (it will only create a run if the filter matches)</li><li>A single event can trigger many tasks if it matches many</li></ul>

Event triggers

An Anonymous User

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?

CPU and memory optimised machines

This feature will follow on from our <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://trigger.dev/changelog/python-extension">Python extension</a> to allow full Python support in Trigger.dev.

Full Python support

James

Would be cool to <ul><li>unit test: have a way to unit test specific tasks and mock other other tasks (that are used within the tested task)</li><li>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</li></ul>

E2E and unit testing utilities

Workers in Asia will reduce the latency when accessing your regional resources from your tasks.

アジアのワーカーは、タスクから地域のリソースにアクセスする際のレイテンシーを減らすことができます。

アジア労働者地域

Asia worker region

Support for logs to be sent from <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Trigger.dev">Trigger.dev</a> to 1+ other destinations. We would probably start with an HTTP POST request with a JSON body, similar to <a target="" rel="noopener noreferrer nofollow" class="link" href="https://supabase.com/docs/guides/platform/log-drains">how Supabase do this</a>.

Support log drains

<blockquote><a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Trigger.dev">Trigger.dev</a> currently does not support “offline” dev mode, where you can run tasks without an internet connection. <a target="_blank" rel="noreferrer" class="link" href="https://feedback.trigger.dev/">Please let us know</a> if this is a feature you want/need.</blockquote>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.

Run Trigger.dev in dev mode offline

Zachary Keener

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”

Filter runs by payload value

Rich Turnbull

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.

Incoming webhook trigger

We currently support setting a <code>concurrencyLimit</code> on a task, or on a queue that you create. This can also be used with a <code>concurrencyKey</code> to have per-user queues: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://trigger.dev/docs/queue-concurrency">https://trigger.dev/docs/queue-concurrency</a>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.

Rate Limiting / throttling

Simulate CPU and Memory Limits on Dev Environments

Conner Aldrich

When you trigger a prod or staging run in the Trigger.dev cloud it takes 3 seconds on average for the machine to start up and your code to start executing. This same slowness happens when a run resumes, like after using <code>wait.for</code> if the delay is above a threshold when we shut the machine down.They take this long because we're using Kubernetes for our cluster and a new pod takes a while to come up.We're switching to using MicroVMs for the cloud machines. Our target is to get the p95 for starts and resumes to under 500ms.

Make cold starts faster

Linear

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.

I øjeblikket deler flere trigger-udviklingsinstanser for det samme projekt én kø, så enhver instans kan køre enhver opgave, hvilket betyder, at de ender med at »stjæle« hinandens arbejde. Ønsket er at understøtte noget i stil med preview-grene, men for udviklingsmiljøet: separate udviklingssessioner (f.eks. et sessions-id eller en "udviklingsgren"), så hver lokal instans kun kører opgaver, der udløses fra den samme session. Det ville give mulighed for at køre flere arbejdstræer eller app-kopier parallelt (f.eks. med Codex/Claude) uden at opgaver fra den ene ender med at køre i den anden.

Isolerede udviklingssessioner til flere lokale trigger-udviklingsinstanser

Isolated dev sessions for multiple local trigger dev instances

Iss Haddad

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.

Role Based Access Controls (user permissions)

When you call the SDK functions, there’s an extra param which allows you to pass request options. We should add the ability to pass an access token and branch here.

Add ability to specify access token and preview branch in trigger options

Eric Allam

There was an incident yesterday that involved DNS and affected us-east-1. We were unable to run jobs reliably throughout the day and spent the day manually retrying failed jobs. The only alternative is eu-central-1, but that has far higher latency. It would be good to have a 2nd US region available in AWS as a redundancy against an issue like this that preserves relatively low latency for US-based workflows.

Add a 2nd US region in AWS such as us-west-2

Alex Farrill

Allow organizations to configure SSO settings at the org level, including selecting a single SSO provider, restricting access to specific email domains. This gives organizations more control over authentication methods and access policies.

Organization-level SSO configuration with domain restrictions

Right now you can have a great experience with <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Trigger.dev">Trigger.dev</a> and Vercel by using our <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://trigger.dev/changelog/preview-branches">Preview branches</a> and our <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://trigger.dev/docs/config/extensions/syncEnvVars#syncvercelenvvars">syncVercelEnvVars extension</a>.—An official Vercel integration would do those two things but with less setup:<ol><li>Sync environment variables from Vercel to Trigger.dev.</li><li>Create preview branches on Trigger.dev.</li></ol>

Vercel integration

Easily get realtime data from your task runs to your frontend (or backend).This would include basic stuff:<ol><li>Run status</li><li>Run payload</li><li>Run output</li></ol>But also more advanced use cases:<ol><li>Being able to send structured (and typed) data from inside your run functions to your frontend.</li><li>Being able to stream data from inside your run function to your frontend.</li><li>Being able to send React Server Components from your run function to you frontend. Maybe. We're trying to figure out if this is possible.</li></ol>

Realtime notifications

To access some databases, and other services, you need to provide them with an IP whitelist. 
For this to work well we need to have static IPs, potentially a per customer IP address.

Чтобы получить доступ к некоторым базам данных и другим службам, необходимо предоставить им белый список IP-адресов. 
Чтобы это хорошо работало, нам нужны статические IP-адреса, возможно, IP-адрес каждого клиента.

Статические IP-адреса

Để truy cập một số cơ sở dữ liệu và các dịch vụ khác, bạn cần cung cấp cho họ danh sách trắng IP. 
Để đảm bảo hoạt động hiệu quả, chúng ta cần sử dụng địa chỉ IP tĩnh, có thể là một địa chỉ IP riêng cho từng khách hàng.

Địa chỉ IP tĩnh

Static IP addresses

Inside your run function it would be useful to be able to pause execution until something external has happened.
We had a feature called "wait for event" in v2 that allowed you to do this. You could then send an event from your own code and the run would continue where it left off.
An example might be for an application process where the application needs to go through an approval step e.g. an AML check.
There would be a timeout of how long it would wait, with a default.

Wait for token

At the moment you can't delete a v3 project. You can rename them from "Project settings", but they can't be deleted.

Delete a v3 project

Currently, if your database of some of your services are not accessible to the public internet you can’t access them inside your <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Trigger.dev">Trigger.dev</a> tasks (unless you self-host the entire platform). There are many ways we could solve this. One obvious solution is for us to provide a Bridge Connector that you can run inside your cluster and it would only allow access from your <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Trigger.dev">Trigger.dev</a> tasks. We use a tool like this to access our restricted database outside of AWS. It would be very useful if you can share the kind of private resources you need to use in <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Trigger.dev">Trigger.dev</a> and what solutions you would be happy with!

VPC peering

HIPAA compliance

You can only provide 100 items in <code>batchTrigger</code> and <code>batchTriggerAndWait</code> at the moment. if you want to batch more items than this you need to call it multiple times, creating more than one batch.
We should add a way to create larger batches. It would involve multiple API calls and we'd probably want to make that explicit. For example, you would create a batch, add items to it and then finalize it.

Support more than 100 items in `batchTrigger` at once

You can view logs per-run at the moment, but not across all runs. It would be very useful to have search and filtering across all logs with full text search.This will require us to change where we store logs to Clickhouse (probably) so we can do fast filtering/search.

Logs view with global search and filtering

There are two things that aren't great about deploying at the moment:<ol><li>You can end up having to add a lot packages to <code>dependencesToBundle</code>.</li><li>You need to match the versions between the SDK and the CLI.</li></ol>We are changing the way we bundle your code so it works without intervention in more situations. Mainly this means changing to use ESM – we are currently using CJS because of one of our dependencies.We are also going to change to a single package for the CLI and SDK. This means it will be impossible to have version mismatches between them.