Better read replicas for modern workloads

Scale read performance at a lower cost for the Postgres database you already use. No data migration, no code changes, and no additional infrastructure to manage.

Springtail supports Amazon RDS for Postgres, Amazon Aurora PostgreSQL, and Supabase Icon representing seamless integration of Springtail with Amazon RDS for PostgreSQL, Amazon Aurora PostgreSQL, and Supabase.

Works with Amazon RDS, Aurora, Supabase

Springtail Compatibility with AWS Postgres Icon representing seamless integration of Springtail with Amazon RDS for PostgreSQL and Aurora PostgreSQL, replacing read replicas without migration.

Save up to 58% vs. traditional read replicas

Introducing Springtail

Elastic read replicas for your existing Postgres database

Elastic read replicas for PostgreSQL databases.

On-demand read scaling

Add or remove read capacity in seconds to match workloads.

Works with your existing Postgres

Amazon RDS, Aurora, and Supabase are supported out of the box.

No code changes or rewrites

Queries are routed automatically, no app changes required.

Most read replicas sit idle 80% of the day. Springtail eliminates that waste.

Fast provisioning

Scale in seconds

Unlike traditional read replicas, Springtail uses a shared storage layer across all replicas. New replicas start in seconds without needing to copy your full database.

Read scaling for PostgreSQL using shared storage layer and on-demand compute nodes.
Chart of read replica usage with period of low demand.
Cost savings

Stop paying for idle read replicas

Quickly add read replicas to handle peak load, and remove them when demand drops to avoid paying for idle capacity.

Springtail scales read performance without additional engineering work or infra to manage.

Integrate in minutes

Works with your existing Postgres database

Developer docs

Point your application to Springtail, and it routes reads to its elastic replicas and writes to your existing primary.

Springtail uses PostgreSQL logical replication to maintain a real-time copy of your data in a shared storage layer.

Real-time data sync

Streams data changes from your primary using Postgres logical replication.

Schema change tracking

Captures DDL changes with triggers to keep schemas in sync across nodes.

Postgres frontend

Utilizes Foreign Data Wrappers to expose the replicated data as Postgres tables.

Low-risk adoption

Connect through a standard Postgres endpoint. Easy to integrate, no vendor lock-in.

Talk with us

Keep your Postgres. Add elastic replicas.

Scale read performance without paying for idle read replicas.

Frequently asked questions

What databases does Springtail support?
Which versions of Postgres does Springtail support?
How will Springtail import my existing data?
How long does onboarding take with Springtail?
Do I need to install a Postgres extension for Springtail?
Why not just use traditional read replicas?
What kind of performance can I expect?