Read replicas

Supabase Read Replicas distribute read traffic across multiple databases. Use them to isolate analytics workloads from production, reduce latency for global users or scale read capacity beyond a single database.

Key features

1. Workload Isolation: Run heavy read queries (analytics, reports, exports, batch jobs) on dedicated replicas without impacting production response times.
2. Multi-region deployment: Deploy replicas in regions closer to your users. European users query European databases.
3. Dedicated endpoints: Each replica provides separate database and API connection strings for direct access.
4. Automatic routing: API load balancer routes GET requests to the nearest available replica.
5. Centralized configuration: Settings are propagated across all databases in a project.
6. Monitoring tools: Track replication lag and resource usage directly in the Supabase Dashboard.

When to use Read Replicas

• Your analytics team's reports slow down production (workload isolation)
• Users in Europe or Asia experience 100-150ms latency (geo-distribution)
• You've reached 16XL and need more read capacity (horizontal scaling)
• Your workload is 80%+ reads and needs to scale independently of writes

Get Started

Deploy your first Read Replica in minutes from Project Settings > Infrastructure. Choose a region—same region for analytics isolation, different region for geo-distribution. Select a compute size to match your workload.

Read blog post