Elastic read replicas for PostgreSQL on AWS

  • Scale out Postgres read performance
  • Save up to 58% on RDS replica costs
  • Zero data migration, no code changes
Backed by

Better Postgres read performance, at a lower cost

Springtail provides elastic read replicas for Postgres on Amazon RDS. Scale up compute to improve read-heavy workloads, and scale down during low usage to reduce costs.

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 AWS Postgres

Seamlessly replace your Amazon RDS for PostgreSQL or Aurora PostgreSQL read replicas with Springtail.

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 up or down for read replicas. 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.

OVERVIEW

Elastic read scaling for your existing Postgres instance on AWS

Architecture

Springtail is a cloud-native distributed database that separates storage from compute, providing seamless horizontal scaling for read-heavy workloads.

Our service works alongside your existing Amazon RDS infrastructure, offloading and scaling reads while your Amazon RDS for PostgreSQL or Aurora PostgreSQL remains the trusted, primary store of data.

Diagram showing Springtail scaling PostgreSQL read performance on AWS using logical replication and elastic compute nodes.

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

Features

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 RDS 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 replica 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.

Autoscaled storage

Seamlessly increases storage capacity as your data volume expands.

Query Load Balancing for PostgreSQL Replicas Icon showing how Springtail distributes query traffic across PostgreSQL read replicas to optimize performance and maintain consistent response times.

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

Coming

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

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

compatibility

Works with your existing AWS Postgres database

Built on native Postgres replication. Zero migration.

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

Documentation
Real-Time Data Synchronization for PostgreSQL Icon representing Springtail’s ability to stream real-time data changes from the primary database using PostgreSQL logical replication on AWS.

Real-time data sync

Streams data changes from your primary using Postgres logical replication.

Schema Change Tracking for PostgreSQL Replicas Icon illustrating how Springtail captures DDL changes using triggers to keep PostgreSQL schemas synchronized across read replicas on AWS.

Schema change tracking

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

PostgreSQL Frontend Access via Foreign Data Wrappers Icon showing how Springtail exposes replicated PostgreSQL data as native Postgres tables using Foreign Data Wrappers for seamless application integration.

Postgres frontend

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

Automatic Query Fallback to Primary PostgreSQL Icon symbolizing Springtail’s automatic routing of unsupported queries, such as inserts, updates, and schema changes, back to the primary Amazon RDS database.

Automatic query fallback

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

Request Access

Get started for free

Scale out read performance for your existing Postgres.

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?
How can I reduce AWS costs for Postgres read replicas?
What kind of performance can I expect?