Cloud or self-hosted
Choose a deployment model#
Cloud#
Cloud is the managed path. Trigger.dev says it is scalable and designed for high availability, security, and scale. The public pricing page lists Free, Hobby, Pro, and Enterprise options; verify current prices before publishing a commercial comparison.
Self-hosting#
The self-hosted version runs as containers on your infrastructure. The public guide describes a webapp part and a worker part that can be scaled independently. Docker Compose and Kubernetes guides are available.
You own provisioning, updates, security, scaling, uptime, and data integrity for the deployment. Some Cloud features are not available self-hosted, including managed auto-scaling and dedicated support.
Self-hosting is an operational commitment. Read the upstream security guide and use version-tagged releases before deploying.
Which should you choose?#
- Choose Cloud when you want managed infrastructure and a faster path to production.
- Choose self-hosting when infrastructure control, data residency, or compliance requirements drive the decision.
- Confirm feature parity and limits against the upstream guide before making an architecture decision.