Today we're rolling out new v4 regions that are hosted on AWS. Let's run through why they're better for you, how you can switch to them today, and when we'll automatically migrate you.
4x included concurrency for paid plans
With v4 we introduced "burst concurrency". A single queue is capped at your concurrency limit, but you can burst up to 2x that when running across multiple queues or tasks.
When using our new AWS regions you will get double the included concurrency on your Hobby or Pro plan:
- Hobby: from 25 to 50 (up to 100 burst)
- Pro: from 100 to 200 (up to 400 burst)
We will be rolling out these increases over the next couple of weeks.
NOTE
We will automatically migrate all v4 projects to the new AWS regions on September 1st 2025 and the old regions will be retired.
Reduced pricing for extra concurrency
When on the Pro plan you can purchase extra concurrency. With our new v4 AWS regions this is 5x cheaper: 50 extra concurrency for $10/month.
For 500 concurrency (1,000 burst) you would now pay:
- $50/month for Pro
- $60/month for 300 extra concurrency
Static IPs
You can now secure your connections to databases and services that require IP whitelisting with our new static IP addresses. From our "Regions" page you will see the static IP addresses for each AWS region, if you're on a paid plan.
This means 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.
Almost all popular database services support static IPs, like Amazon RDS/Aurora, Supabase, PlanetScale, MongoDB Atlas, ClickHouse, and more.
NOTE
Free customers' runs are executed on dynamic IP addresses so whitelisting is not available. If you're currently using v3, you'll need to upgrade to v4 to use these new regions.
Multi-region workers
Execute your tasks closer to your users and APIs. Now you can choose from us-east-1 and eu-central-1.
Visit our brand new "Regions" page to see all that are available to you. From there you can set your default region:
Better still, you can override your default region when triggering a run:
await tasks.trigger<typeof yourTask>(payload, { region: "eu-central-1" });
New EU region
We now have a new worker region in Frankfurt, Germany. This enables you to:
- Access geo-restricted APIs that only allow requests from EU IP addresses.
- Reduce latency for tasks that interact with European services.
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 runs can now execute in different regions, all operational and log data remains in us-east-1.
Moving to AWS
Our new v4 clusters are on AWS. 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: Our container and server boot times are faster and more consistent.
- 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.
What's coming next
- AWS PrivateLink: This would allow you to connect to your databases and services without going over the public internet. Faster and more secure.
- More regions: We're looking to add more regions in the future.
- MicroVM architecture: We're moving the cloud workers to use MicroVMs which will give under 500ms cold starts.
