# readysettech/readyset

Readyset is a MySQL and Postgres wire-compatible caching layer that sits in front of existing databases to speed up queries and horizontally scale read throughput. Under the hood, ReadySet caches the results of cached select statements and incrementally updates these results over time as the underlying data changes.

Repository: https://github.com/readysettech/readyset
Canonical: https://ross.abutalabs.com/products/readyset
Homepage: https://readyset.io
Language: Rust
License: NOASSERTION
License Family: other
Topics: caching, caching-proxy, databases, mysql, postgres, postgresql, rust, streaming-data, sql, backend, cache, mysql-database, postgresql-database, rust-lang
Last push: 2026-08-26T23:12:14+00:00

## Health v2 (maintenance only)
Score: 94/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 83, longevity 100
- inputs: {"age_days": 1562, "days_push": 7, "days_rel": 34, "gap_med": 33, "n_releases_24m": 22}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 5272, forks 162 (observed 2026-08-28T04:09:14.016558+00:00)

## What it is
Readyset is a transparent, wire-compatible SQL caching proxy for Postgres and MySQL that sits between your application and database. It caches SELECT query results in memory and keeps them fresh via incremental updates from the database's replication stream, requiring no code changes or manual cache invalidation.

## Use cases
- speed up slow SQL queries without rewriting application code
- scale read throughput of a Postgres or MySQL database without adding read replicas
- avoid manual cache invalidation for database-backed caching
- protect a production database from heavy or AI-generated read workloads
- drop a caching layer in front of an existing database via connection string swap
- reduce database infrastructure costs for read-heavy applications

## When to choose
- you have read-heavy Postgres or MySQL workloads bottlenecked on query latency or database load
- you want in-memory caching without application rewrites or TTL tuning
- you need cached results to stay consistent with the source database automatically
- you want to avoid provisioning and managing read replicas

## When to avoid
- your workload is write-heavy with little repeated read traffic
- you need full SQL feature coverage for all queries, since only cacheable SELECTs are accelerated and others are proxied
- you require a permissive open-source license, as Readyset uses a source-available BSL license
- you cannot run an additional proxy component in your database path

## Facets
- artifact type: service
- maturity: active
- function: caching, database, proxy, middleware
- domain: databases, backend, performance, self-hosted, developer-tools
- platform: self-hosted, cloud, windows
- tags: sql-caching, cache-invalidation, wire-compatible, mysql-proxy, postgres-proxy, read-scaling, query-acceleration, replication-stream, sql, linux, docker, macos

## Member repositories
- readysettech/readyset (main) score 94

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:14.016558+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:59:27.567808+00:00, confidence not recorded.
  - readme: https://github.com/readysettech/readyset (fetched 2026-08-28T04:09:14.016558+00:00, sha 4ac7d8daa799)
  - homepage: https://readyset.io (fetched 2026-08-29T08:54:19.580151+00:00, sha 624327faed8c)
  - site_page: https://docs.readyset.io (fetched 2026-08-29T08:54:19.591757+00:00, sha 1b6274af5b6e)
  - site_page: https://readyset.io/pricing (fetched 2026-08-29T08:54:19.589694+00:00, sha ae217b6e5253)
- Data as of 2026-08-30T08:39:29.467469+00:00.