Data Residency

Databases on our shared fleet (Free, Solo and Pro) run in one of two regions, chosen when the database is created: US East, on Layerbase Cloud infrastructure in Ashburn, Virginia, United States, or EU West, in France. Account records, team records, cloud control-plane metadata and operational logs are stored in the United States, whichever region your databases run in.

Within a region, a shared database is placed on whichever server has capacity. A database stays in the region it was created in: existing databases do not move between regions. Dedicated servers have their own location catalog, chosen at purchase. Today that is the United States or Brazil, across US East (Virginia), US West (Oregon), and South America (São Paulo). Not every size is offered in every region; the dedicated pricing page lists which. Your databases then run on that machine, in that region.

EU West is a location, not EU data residency. Layerbase does not currently offer EU-only processing, multi-region placement, or a contractual data residency guarantee.

When you create a shared database in EU West, the following is stored in the EU:

• the database itself, on a server in France;
• its backups, in an object storage bucket restricted to the EU jurisdiction.

The following is stored in the United States:

• your account record, team records, and the control-plane records that describe your databases (names, engines, hostnames, status and similar metadata);
• operational logs and diagnostics, described under Logs and Observability below.

Managed DuckLake storage is not tied to a database region; see DuckLake Data below.

Layerbase Cloud production databases run in isolated user containers on managed cloud servers in the region chosen when the database was created: Ashburn, Virginia for US East, or France for EU West. Databases on a dedicated server run in the region chosen for that server, in the United States or Brazil. Database names, engine metadata, ports, hostnames, status, firewall rules, API key metadata, and related control-plane records are kept on the server that runs the database and in our account systems in the United States.

Backups are stored in Cloudflare R2. For databases in US East and on dedicated servers, R2 is used as a global object storage service and may route, replicate, cache, or process data outside the primary Layerbase Cloud server location as part of Cloudflare's infrastructure. Backups of databases in EU West are stored in an R2 bucket restricted to Cloudflare's EU jurisdiction. Backup retention depends on the plan and current backup system. Account deletion is designed to purge R2 backups owned by the deleted account.

Managed DuckLake data (the Parquet files that hold your lake tables) is stored in Cloudflare R2. Layerbase does not select an R2 location or jurisdiction for these buckets, so the same global routing, replication, and caching described for backups applies. If you connect your own bucket (Cloudflare R2 or AWS S3), your lake data stays with that provider, in the bucket and region you choose.

Operational logs and diagnostics may be processed outside the primary database region, including through Layerbase logging infrastructure and Cloudflare R2 log storage. Logs can include request metadata, IP addresses, user identifiers, database identifiers, error messages, and other diagnostic details. Logs are normally retained for about 30 days.

Authentication is handled through OAuth providers such as Google and GitHub. Billing and subscription processing is handled through Polar. These providers may process account, authentication, and payment metadata in locations governed by their own infrastructure and policies.

Layerbase does not currently support:

• EU-only or country-specific data residency (EU West keeps your databases and their backups in the EU, but account records, team records and logs stay in the United States);
• shared-fleet regions other than US East and EU West, or moving an existing database between regions;
• multi-region replication or failover;
• HIPAA, SOC 2, PCI DSS, or similar compliance programs;
• custom data processing agreements.

If your workload requires a specific jurisdiction, regulated data handling, a data processing agreement, or written retention terms, do not store that data in Layerbase Cloud until we have agreed to those requirements in writing.

Data residency questions can be sent to bob@layerbase.com.