Multi-region workers, Static IPs, and AWS

Choose which region your workers run in, get static IPs, and our move to AWS.

Image for Multi-region workers, static IPs, and AWS

Multi-region workers

Deploy your tasks closer to your users and APIs with worker machines in European datacenters. You can set a default region in the dashboard and override it on a per-task basis in your code, giving you complete control over where your compute runs.

Regions dashboard page

New EU region

We now have a new worker region in Europe, enabling you to:

  • Access geo-restricted APIs that only allow requests from EU IP addresses
  • Reduce latency for tasks that interact with European services
  • Meet compliance requirements that require compute to happen within specific regions

Which regions should we add next?

We're looking to add more regions and will spin them up based on demand. If you have a specific region you'd like to see, please create a feature request.

NOTE

While your tasks can now execute in different regions, all operational and log data remains in us-east-1.

Static IPs

You can now secure your connections to databases and services that require IP whitelisting with our new static IP addresses. Login to your dashboard and head to the "Regions" page in the side menu to see your new static IP addresses.

Reliable database connections

Many production databases and enterprise services require you to whitelist specific IP addresses for security. With static IPs, you can:

  • Connect to production databases that enforce IP restrictions
  • Integrate with enterprise APIs that require pre-approved IP addresses
  • Access on-premise services behind firewalls with strict IP policies
  • Maintain consistent connections without worrying about IP changes

NOTE

If you're currently using v3, you'll need to migrate to v4 to use static IPs. If you've already whitelisted our previous IP addresses, you'll also need include our new ones.

Moving to AWS

A major part of our v4 GA release has been our migration to AWS infrastructure. This move unlocks immediate performance improvements while laying the groundwork for capabilities that simply weren't possible before.

What we've achieved today

  • Faster cold starts: Container boot times improved dramatically with consistent sub-second initialization, getting your tasks starting faster.
  • Static IP support: We now support static IP addresses for your tasks, making it easier to connect to databases and services that require IP whitelisting.
  • Improved network performance: Significant improvements in throughput and latency with AWS's purpose-built networking hardware, including features like SR-IOV and Enhanced Networking.

What's coming next

  • MicroVM architecture: Migrating to Firecracker microVMs on bare metal for near-native performance with 50-90% faster start times.
  • Global region expansion: Deploy compute closer to your services using AWS's extensive worldwide footprint.
  • Spot instance integration: Support for AWS Spot Instances will enable us to reduce compute costs for our customers.
  • Advanced networking: AWS PrivateLink and VPC peering will enable completely private network paths between Trigger.dev and your infrastructure.

Day 1

Day 3

Day 4

Day 5

Ready to start building?

Build and deploy your first task in 3 minutes.

Get started now