Elastic read scaling for your existing Postgres

Built for developers and data teams who want to scale read performance, without data migrations or code changes.

Horizontally scale Postgres read performance
Save up to 58% vs. traditional read replicas
Zero data migration, no code changes
Backed by

Better Postgres read performance, at a lower cost

Springtail lets you add elastic read replicas to your existing Postgres database. Scale up additional compute to handle read-heavy workloads, scale down to reduce costs when usage drops.

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

Works with your Postgres

Works with your existing Amazon RDS for PostgreSQL, Aurora PostgreSQL, or Supabase instances.

Elastic Scaling for PostgreSQL Read Replicas Icon illustrating Springtail’s ability to instantly scale PostgreSQL read replica compute capacity up or down based on workload demand on AWS.

On-demand scaling

Instantly scale compute for read heavy workloads. Pay only for the capacity you need, when you need it.

Fast PostgreSQL Read Replica Deployment Icon symbolizing rapid deployment of additional PostgreSQL read replicas with Springtail, minimizing setup time and syncing delays on AWS.

Fast replication

Deploy additional read replicas in seconds. No tedious setup or lengthy syncing delays.

ARCHITECTURE

Scale Postgres read performance without scaling your ops

Documentation

Springtail separates storage from compute, providing seamless horizontal scaling for read-heavy workloads.

You can use Springtail with your current Postgres infrastructure. No application changes or data migration required.

Springtail read scaling for PostgreSQL using logical replication and elastic compute nodes.

Springtail’s elastic replicas can scale out with your workload, and scale down when demand drops.

PERFORMANCE

Maximize throughput, minimize overhead

Documentation

Say goodbye to over-provisioned read replicas.

With Springtail, you only pay for the performance you need, when you need it.

Unlike traditional replicas that are always-on at full capacity, Springtail offers on-demand scaling, reducing overhead and saving you money.

Elastic Compute Scaling for PostgreSQL Replicas Icon illustrating Springtail’s ability to dynamically scale PostgreSQL replica compute nodes up or down based on workload needs on AWS.

Scaled compute

Scales read compute nodes up or down to match workload requirements.

Autoscaling Storage for PostgreSQL Databases Icon representing automatic storage expansion for PostgreSQL replicas with Springtail as data volume grows, maintaining seamless performance on AWS.

Bottomless storage

Seamlessly increases storage capacity as your data volume expands.

Load balancing

Distributes queries across replicas with consistent and optimized performance.

Read/Write Splitting for AWS PostgreSQL Databases Icon illustrating Springtail’s method of routing read queries to elastic PostgreSQL replicas while directing write operations to the primary Amazon RDS instance.

Read/write splitting

SOON

Offloads read queries to Springtail, sends write traffic to your primary database.

Built for developers and data teams who want Postgres scalability without the overhead.

TRANSPARENT

Works with your existing Postgres database

Documentation

Built on native Postgres replication. Zero migration.

Springtail connects to your existing database instance using native Postgres replication.

It streams changes from your primary database in real time, letting you scale out read workloads without changing your existing Postgres infrastructure.

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.

Automatic query fallback

Routes unsupported queries, like inserts/updates/schema changes, back to the primary.

Request Access

Get started for free

Scale read performance for your existing Postgres database.

Frequently asked questions

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