June 2025 Summaries

Trigger.dev v4 introduces the ability to self-host on Kubernetes, offering a new deployment option alongside the existing Docker setup, thanks to the official Helm chart that simplifies scaling and orchestration in Kubernetes environments. This version is particularly advantageous for teams already utilizing Kubernetes infrastructure, those with stringent compliance requirements, or those needing private or air-gapped environments. Key improvements in v4 include integrated Postgres, Redis, and object storage, and streamlined worker management leveraging Kubernetes-native scaling capabilities. While self-hosting on Kubernetes offers flexibility, it also requires Kubernetes expertise for tasks like cluster maintenance and security management, with the Helm chart providing necessary components except for some Cloud-exclusive features like warm starts and checkpoints. The post emphasizes best practices such as version locking, environment-specific configurations, and security measures, and encourages leveraging external managed services for reliability. For those interested in enterprise support, Trigger.dev provides premium services, and users can access community support via Discord for guidance.

Trigger.dev's version 4 aims to simplify self-hosting by incorporating lessons from version 3, focusing on ease of use and comprehensive documentation to make it accessible without requiring extensive DevOps expertise. The preferred method for self-hosting is using Docker, with a Kubernetes guide to be released soon. While the managed Trigger.dev Cloud offers automatic scaling and dedicated support, self-hosting is recommended for those needing greater control, such as compliance with data residency or operating in private environments. Key updates in v4 include eliminating custom startup scripts, integrating a built-in registry and object storage, and enhancing worker management for easier scaling. However, self-hosters must handle infrastructure management, updates, and security, with setup facilitated by Docker Compose. The self-hosting approach involves trade-offs and requires active involvement, but offers flexibility with potential for enterprise support and community assistance through Discord.