Our take
Activeregular commits and releases- Activity
- 76
- Community
- 84
- Issues
- 54
- Pull requests
- 20
+12 stars in the last 30 days
Readyset is an actively maintained, specialized database cache with regular releases and a broad contributor base, making it a credible option for teams that can validate their query workload against its documentation.
Good fit if
- Your application uses PostgreSQL or MySQL and repeated SQL reads are a performance concern.
- You want database-backed cache updates without adding manual invalidation to application code.
- You can run a Rust-based service or use the managed Readyset Cloud offering.
Look elsewhere if
- Your database is not PostgreSQL or MySQL.
- You need a general-purpose cache rather than a layer for caching SQL query results.
- The Business Source License 1.1 terms do not suit your deployment or distribution plans.
All health signals
| Last commit | 2026-11-16 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 12 (latest stable-261022, 2026-10-22) |
| Contributors | 77 (top contributor: 20% of commits) |
| Issues closed, last 90 days | 21 (typically closed in 39 days) |
| Pull requests merged, last 90 days | 0 |
| Project age | 4 years |
Checked on 2026-11-17 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
5,303Forks
166Change since Nov 16, 2026: 0 stars·0 forks
Overview
Readyset is a Rust-built, wire-compatible caching layer for PostgreSQL and MySQL. It sits between an application and its existing database, caching the results of SQL reads and keeping them updated from the database's replication stream. The goal is to reduce repeated query work and increase read throughput without requiring application rewrites or manual cache invalidation.
It is aimed at teams whose database read load is becoming a bottleneck but who want to keep their current database client or ORM. Readyset supports complex SQL reads, though whether a particular query can be cached should be checked against the project documentation.
Key Features
- Speaks the PostgreSQL and MySQL wire protocols, so applications can connect using their existing database client or ORM.
- Caches results of selected SQL
SELECTstatements for faster lookups. - Uses database replication streams to keep cached results synchronized as underlying data changes.
- Sits between an application and its database, without requiring application-level cache invalidation logic.
- Can be installed using the provided quickstart script, a Docker image, or a Linux binary.
- Offers a managed Readyset Cloud service as an alternative to running the cache yourself.
Use Cases
- A backend team wants to reduce repeated read-query load on a PostgreSQL database while retaining its existing application and ORM.
- A service with growing read traffic needs to scale database reads, and its team wants a cache that tracks database updates rather than relying on manual invalidation.
- A team evaluating query caching wants to test whether its SQL reads can benefit before changing its application architecture.
- An organization that prefers a managed service can evaluate Readyset Cloud instead of operating Readyset itself.
What you need
Detected in the repository
- Rust (from Cargo.toml)
- A Compose file to run it with its related services
Getting Started
Run the quickstart script:
bash -c "$(curl -sSL https://launch.readyset.io)"
See the README and getting started guide for setup details and supported deployment options.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Considerations
Readyset must be integrated into the path between the application and its PostgreSQL or MySQL database, and its cache synchronization depends on the database replication stream. Check the documentation to confirm that your SQL workload and deployment setup are supported. The repository is actively maintained, with recent commits and releases and contributions from many people; issue resolution can still take time. The README states that Readyset is licensed under BSL 1.1, converting to Apache 2.0 after four years, so review the license terms for your intended use.
Found this useful?
Share it with someone who would like readyset.