Springtail adds real time, elastic read replicas to your Supabase Postgres database without code changes or data migration. You can scale replicas on demand to handle traffic spikes and reduce costs.

This gives you the performance benefits of traditional read replicas without the operational burden. Add replicas in seconds to handle peak load, and remove them when demand drops to avoid paying for unused capacity.

How it works

Springtail uses PostgreSQL logical replication to stay in sync with your Supabase database. Once connected, it maintains a real time copy of your data and handles load balancing, replica lifecycle, and scaling behind a single endpoint.

Your application connects to Springtail through a standard Postgres-compatible proxy. The proxy automatically routes read queries to Springtail replicas and sends write queries to your Supabase primary. This allows you to improve performance and scale reads without modifying your application code.

Unlike traditional read replicas, Springtail uses a shared storage layer across all replicas. This architecture allows new replicas to start up in seconds without needing to copy the full dataset. You can increase read throughput quickly by adding replica nodes as needed, making your application faster and more responsive under load without over-provisioning.

Use cases

• Improve query performance for read heavy applications
• Handle traffic spikes without over-provisioning
• Reduce costs by scaling replicas only when needed

Key benefits

• Works with your existing Supabase Postgres database
• Fast startup of new replicas, no need to copy your entire database
• No changes to your schema or application logic
• Zero maintenance replicas that scale on demand

Learn more

• 📖 Read the docs
• 🖥️ Book a demo