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.
Comments12
An Anonymous User
Dec 26, 2024
Would be especially cool if there was a nice Fly.io integration to just use their machines, which are already very very good.
An Anonymous User
Oct 8, 2024
We need this too
An Anonymous User
Nov 5, 2024
Self hosted workers would be really nice to have. The main reasoning is to be able to run tasks without extra setup(i.e within app code base). Deployment, env vars configuration and private subnets/resources is something that becomes hard to deal with once you have lot of externalities.
An Anonymous User
Nov 29, 2024
Would love that !
Raj Sharma
Nov 29, 2024
would be nice to hav ability to pick which tagged tasks get assigned to which group of workers if there are gonna be multiple.
This could allow the trigger.dev cloud to also allow users to self host just workers and add that as maybe an env into the existing cloud itself instead of having to self host everything and dealing with public ip etc.
An Anonymous User
Aug 23
This would be great as a data access pattern. E.g. hosting the workers on Railway so they have instant access to the database instead of going over the internet
Youmin Kim
Mar 26, 2025
This will be helpful to support non-us regions
An Anonymous User
May 21, 2025
Potentially stupid question. Do self-hosted workers do anything for you if you have data restrictions (e.g., data must reside in GovCloud)? Because doesn’t the task cache data make it over to the trigger control plan?
Víctor Barberà
Jul 18, 2025
Any updates on this?😬
Ashley Williams
Aug 15, 2025
Would use this as well.
Seems with v4 regions, we could just have a “self hosted region”, and have jobs spin up on them.
I think it would still be fair to pay the fixed running cost; but not the CPU time.