Non-US region support

[worldly lake]

Hi, Trigger.dev team, thanks for the great product. Your service improved our developer experience a lot. We use v3

Our database is in Singapore region and it takes long time to run db query from trigger.dev instance (I assume it is in US East region). For example, a simple write query takes 1 second. As we run batch jobs writing thousands queries, it takes too long or fail with timeout.

Supporting Singapore region will help us a lot and I believe it will help other international community devs.

[hasty burrow]

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

---

Thank you for your feedback about Trigger.dev and the challenges you're experiencing with database queries to your Singapore-based database.

Based on the knowledge sources provided, there isn't specific information about current regional deployments or plans for Singapore region support. The documentation doesn't mention which regions Trigger.dev currently operates in or any roadmap for international region expansion.

For your specific issue with long-running database queries, Trigger.dev is designed to handle long-running background jobs without timeouts, which should help with your batch jobs. However, the latency between regions is a separate issue that would indeed benefit from having Trigger.dev instances closer to your database.

I'd recommend a few options:

1. Submit this feature request on the public roadmap as mentioned in the Request a feature documentation.

2. Consider reaching out to the Trigger.dev team directly through:

   • Discord community
   • Email contact form
   • If you have a paid account, request a private Slack Connect channel for support

3. You might also want to explore self-hosting Trigger.dev on your own infrastructure in the Singapore region, which could potentially address the latency issues.

For the timeout issues you're experiencing, you might want to check if adjusting the retry configuration or machine specifications could help, as mentioned in the Limits documentation.

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

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

[worldly lake]

I found this feature request

[flint wing]

After we launch v4 (in a couple of weeks) we'll have the ability to do multi-region.

Definitely vote on that feature request because we'll decide whether there's enough demand for an asian region using that feature request.

There's additional overhead and cost to adding new regions so we won't do it until there's going to be enough demand.

[worldly lake]

Thanks @flint wing . Understood.

I was also reading the self-host doc in your website. We are small team and have experience running few fly.io instances. We are not sure how much resource we will be required to setup/maintain self-host. I see trigger.dev is consistently releasing updates so it would be great if you have any suggestion