Data Residency

Layerbase Cloud currently operates with a United States primary database region. Databases on our shared fleet, and cloud control-plane metadata, are stored on Layerbase Cloud infrastructure in Ashburn, Virginia, United States.

Shared-fleet databases have no region choice: they are placed on whichever server has capacity, all within that single United States region. The one exception is a dedicated server, where you choose the location 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.

Layerbase does not currently offer EU-only hosting, per-database region selection on the shared fleet, multi-region placement, or a contractual data residency guarantee.

Layerbase Cloud production databases run in isolated user containers on managed cloud servers in Ashburn, Virginia. 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 stored in the same Layerbase Cloud environment.

Backups are stored in Cloudflare R2. R2 is 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. Backup retention depends on the plan and current backup system. Account deletion is designed to purge R2 backups owned by the deleted account.

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 database residency;
• customer-selected regions for shared-fleet databases (only a dedicated server picks its region, and only from the locations we sell today: the United States and Brazil);
• 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.