Data Residency

This page describes the current geographic footprint for Layerbase Cloud data, backups, logs, and payment metadata.

Last updated: May 9, 2026

Current Summary

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

Layerbase does not currently offer customer-selectable regions, EU-only hosting, multi-region placement, or a contractual data residency guarantee.

Primary Database Data

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

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.

Logs and Observability

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.

Billing and Authentication

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.

Not Supported Yet

Layerbase does not currently support:

  • EU-only or country-specific database residency;
  • customer-selected database regions;
  • multi-region replication or failover;
  • HIPAA, SOC 2, PCI DSS, or similar compliance programs;
  • custom data processing agreements.

Before Uploading Data

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.

Contact

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