Using legacy

[fiery cradle]

Coolify still using the legacy method, can i use it for production? Or you do not recommend?

[swift wind]

Hi @fiery cradle. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

Based on the official documentation, the legacy Docker self-hosting method for Trigger.dev (v3) is explicitly described as suitable for evaluation purposes only and is not recommended for production. The documentation states:

Security, scaling, and reliability concerns are not fully addressed here. This guide is meant for evaluation purposes and won’t result in a production-ready deployment.

It also highlights several caveats, such as lack of ARM support, no enforced resource limits, and potential security risks due to direct Docker socket access and host networking. The guide further notes:

As self-hosted deployments tend to have unique requirements and configurations, we don’t provide specific advice for securing your deployment, scaling up, or improving reliability.

If you are using Coolify or any other platform that relies on this legacy method, it is not recommended for production use. For production deployments, you should consider using the updated v4 self-hosting guide or Trigger.dev Cloud, which addresses these concerns more robustly Docker (legacy).

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@fiery cradle Kapa.ai is still learning and improving, please let me know how I did by reacting below.