Turso Cloud now runs in Singapore and Frankfurt
Two new AWS regions: Singapore and Frankfurt. Turso Cloud now runs in twelve regions.
On October 1, Turso Cloud added Australia, Brazil, Canada, and Sweden. This week, we're adding Singapore and Frankfurt.
Singapore is where most apps serving Southeast Asia run. Until today, an app there reached its nearest Turso Cloud region, Mumbai, at about 62 ms per round trip. In-region, that round trip takes about 1 ms (CloudPing medians, October 30, 2026).
Frankfurt covers a different need. Apps in central Europe already had Dublin and Stockholm close by, but some teams need their data to stay in Germany. Now it can.
#What Turso Cloud is
If the only thing standing between you and Turso Cloud was a region in Singapore or Germany, you're out of excuses. Here's what you get.
Turso Cloud is the managed version of Turso, the open-source, SQLite-compatible database. Each database is a file in object storage, with no server process running for it. That lets you create one for every agent, user, or tenant: an idle database costs only its storage, and there is no cold start when it's queried again.
AI agents fit this model well. Each agent gets its own database for its memory and its log of actions, and can branch that database before a risky step and roll back if the step fails. Many of these workloads have no shared schema either. An agent, or a user of a CRM or app builder, defines its own tables, and a database per entity handles that without forcing everyone into one schema.
Once every agent, user, or tenant has its own database, you can also decide where each one lives. An agent serving users in Jakarta can run against a database in Singapore. A tenant whose contract requires data to stay in Germany can live in Frankfurt, while your other tenants stay where they are. Location is set per group, so one Turso account can serve tenants in several countries. Each new region adds to the places you can put them.
#All Turso Cloud regions
| Country | Location | Location code |
|---|---|---|
| United States | Virginia | aws-us-east-1 |
| United States | Ohio | aws-us-east-2 |
| United States | Oregon | aws-us-west-2 |
| Canada | Central | aws-ca-central-1 |
| Brazil | São Paulo | aws-sa-east-1 |
| Ireland | Dublin | aws-eu-west-1 |
| Germany (new) | Frankfurt | aws-eu-central-1 |
| Sweden | Stockholm | aws-eu-north-1 |
| India | Mumbai | aws-ap-south-1 |
| Singapore (new) | Singapore | aws-ap-southeast-1 |
| Japan | Tokyo | aws-ap-northeast-1 |
| Australia | Sydney | aws-ap-southeast-2 |
To create a database in a new region, create a group there and add your database to it:
turso group create --location aws-ap-southeast-1 my-group
turso db create --group my-group my-db
The current list of locations is always available in the docs.
#Why these two
Turso Cloud writes its Write-Ahead Log to S3 Express One Zone, AWS's low-latency storage class, and compacts it back into S3 asynchronously. That means we can only run where AWS offers S3 Express. Our October 1 post explains why we made that trade-off.
Paris, Seoul, and N. California are still on our list. If one of them matters to you, tell us on Discord.
#Sign up for Turso today
If you're building in Southeast Asia or Germany, your agents, users, and tenants can now have a database close to home, with the response times and data residency that come with it.
Sign up for Turso Cloud today at https://turso.tech/signup