Data residency
Easily meet international data storage requirements

Meet data residency requirements for global and local data.
Data residency
Easily meet international data storage requirements
Increasingly international regulations and/or customers require that data generated by citizens of a country or region are stored only in that country or region. With pgEdge you can control which tables are globally replicated, and which stay local. In addition you can implement geographic sharding, or “geo-sharding”, where tables are broken out based on a location field (like “country”). This shares global data globally, while keeping local data local where necessary.
For example, an e-commerce company might globally replicate product catalog data, while keeping customer information and the order data they generate within a geographic region like Europe or the United States.
Your choice to support your needs
Enterprise-grade Postgres for non-distributed and distributed applications
Production-ready Postgres for the enterprise with distributed-ready extensions

Fully distributed Postgres for modern globally distributed applications
Ready to deploy where you want: bare metal through fully managed cloud
Self-managed bare metal or virtual machines
For use with Kubernetes, Docker, Docker Swarm and OpenShift
Self-managed or fully-managed on AWS, Google Cloud or Azure
Dive deeper into pgEdge

How to Unleash Ultra High Availability and Zero Downtime Maintenance with Distributed PostgreSQL

How Multi-Master Distributed Postgres Solves High Availability and Low Latency Challenges
Get started today.
Experience the magic of pgEdge for non-distributed and distributed Postgres deployments.