Skip to main content

Locations

Turso optimizes data access with control over data storage and replication across global locations. Your databases form a group with a primary and optional replica locations, ensuring low latency. Turso handles synchronization automatically across its data edge.
  • Primary
    • All databases have a primary location (region) where data is stored, and can’t be changed. You can configure the primary location for groups using the Turso CLI and Turso Platform API.
  • Replicas
    • Databases can be replicated to other regions closer to your users by adding more locations to the group your database belongs to.
CodeLocation
amsAmsterdam, Netherlands
arnStockholm, Sweden
bogBogotá, Colombia
bosBoston, Massachusetts (US)
cdgParis, France
denDenver, Colorado (US)
dfwDallas, Texas (US)
ewrSecaucus, NJ (US)
fraFrankfurt, Germany
gdlGuadalajara, Mexico
gigRio de Janeiro, Brazil
gruSão Paulo, Brazil
hkgHong Kong, Hong Kong
iadAshburn, Virginia (US)
jnbJohannesburg, South Africa
laxLos Angeles, California (US)
lhrLondon, United Kingdom
madMadrid, Spain
miaMiami, Florida (US)
nrtTokyo, Japan
ordChicago, Illinois (US)
otpBucharest, Romania
qroQuerétaro, Mexico
sclSantiago, Chile
seaSeattle, Washington (US)
sinSingapore, Singapore
sjcSan Jose, California (US)
sydSydney, Australia
wawWarsaw, Poland
yulMontreal, Canada
yyzToronto, Canada
You can fetch the list of supported locations as JSON when building with the Platform API or using the Turso CLI.

Groups

All databases are part of a “group”, dictating their primary storage location and replication across distinct VMs (locations), each capped at 100GB. This setup ensures databases share resources yet remain isolated.
Turso Database Groups and Replication