Yes, view our self-hosting guide.
Only what you choose to send. The main body of your Job code runs on your infrastructure. For example when you do a database query, that never touches us. We receive data that triggers the start of a Job, any data you pass to one of our API Integrations, and any data you choose to log using our logging function. We store this to display on the Runs page of your dashboard.
You can use Trigger.dev with a variety of frameworks. You can check out the full list here.
Yes. Jobs are created in your code locally.
Yes. There’s no limit to the complexity of Jobs you can create. Jobs are created in code so you can write conditional, looping, branching or time delayed logic.
A run is a single execution of a Job. This can be in either development, staging or production. View full details.
Yes. You create Jobs directly in your own code so it’s version controlled with everything else.
A simple Job doing a couple of API calls from different services will take about 5 minutes to create.
View our Integrations page to see the Integrations we currently support. If we don’t have an Integration you need, you can request it or create it yourself.
Yes, Trigger.dev is open source. We are strong supporters of open source software, and our first product, jsonhero.io, has a thriving open source community. Trigger.dev follows in that tradition.
No. Trigger.dev is designed for developers who want to create Jobs directly in code, without using a UI builder like Zapier. This allows developers to stay in their familiar development environment and customise their Jobs with code.
Developers will need to create Jobs. However, anyone on the team can monitor running Jobs in the Trigger.dev dashboard.