@@ -0,0 +1,27 @@
+---
+title: "Readyset"
+link: "https://readyset.io"
+github: "readysettech/readyset"
+description: "A transparent, MySQL- and Postgres-compatible SQL caching layer that sits in front of your database and keeps cached query results up to date from the replication stream."
+subcategories:
+  - Proxies & Traffic Management
+compatibility:
+  - MySQL
+  - RDS MySQL
+deployment:
+  - Self-Hosted
+  - Docker
+pricing:
+  - Free
+  - Commercial
+images:
+  - logo.png
+---
+
+Readyset is a caching layer that sits between an application and its database and speaks the MySQL and PostgreSQL wire protocols, so it can be adopted by changing a connection string, with no application rewrite and no hand-written cache invalidation. It caches the queries you choose and proxies everything else straight through to the database, working with your existing ORM or client.
+
+It offers two kinds of cache. *Deep* caches are dataflow-based: Readyset snapshots your tables and then follows the database's replication stream, updating cached results incrementally as the underlying data changes. *Shallow* caches are simpler and TTL-based, served without snapshotting or replication. The company also offers a managed Readyset Cloud and Readyset QueryPilot, which automates query caching for AI-generated workloads.
+
+For MySQL it supports version 8.0 and later, alongside PostgreSQL 13 and later, and it is generally available on self-hosted servers, Amazon RDS, and Aurora, with Azure, Google Cloud SQL, Supabase, and Aiven at alpha level. It's written in Rust and runs from a Docker image or a Linux binary (the binary is recommended for production), with a one-line quickstart script for trying it out.
+
+Readyset is released under the Business Source License 1.1, which is source-available rather than open source: production use is free as long as your aggregate deployment stays within 2 GB of RAM across all instances and you aren't offering it as a managed service, larger deployments need a commercial license from ReadySet, Inc., and each version converts to Apache 2.0 four years after it is published. The project is actively developed — the latest stable release, `stable-260924`, shipped in September 2026.
@@ -0,0 +1,23 @@
+---
+title: "TidesDB"
+link: "https://tidesdb.com"
+github: "tidesdb/tidesdb"
+description: "A fast, embeddable transactional key-value storage engine library written in C on an LSM-tree, with TideSQL pluggable storage engines for MySQL and MariaDB."
+subcategories:
+  - Database Software
+compatibility:
+  - MySQL
+  - MariaDB
+deployment:
+  - Self-Hosted
+pricing:
+  - Open Source
+images:
+  - logo.png
+---
+
+TidesDB is a transactional key-value storage engine library written in C, built on a log-structured merge-tree (LSM-tree) that it combines with a B-tree. It isn't a full database: it's a library you can build a database on top of, or use directly as a standalone key-value and column store. It provides ACID transactions with MVCC and five isolation levels (including two-phase commit and XA), column families, key-value separation, ordered bidirectional iteration with range-bounded scans and range deletes, TTL, a configurable compression pipeline (Snappy, LZ4, and Zstd), and configurable durability, all aimed at low write and space amplification. It runs on Linux, macOS, Windows, the BSDs, and Solaris/Illumos across x86, ARM, RISC-V, and PowerPC, and has official bindings for Go, Rust, Python, Java, C#, C++, TypeScript, and Lua.
+
+For the MySQL ecosystem, the project also publishes **TideSQL**, pluggable storage engines for [MySQL](https://github.com/tidesdb/tidesql-mysql) and [MariaDB](https://github.com/tidesdb/tidesql) built on TidesDB. A TideSQL table keeps its rows in a TidesDB LSM B+tree instead of InnoDB, and moving a table over is a matter of changing the `ENGINE` clause to `TidesDB`. The MySQL engine supports transactions with optimistic MVCC (readers never block writers, and a write conflict surfaces at `COMMIT` for the application to retry), primary and secondary indexes, foreign keys, generated columns, full-text and spatial indexes, online DDL and backup, row expiry, and data-at-rest encryption, with per-table compression, bloom-filter, isolation, and TTL options set through `ENGINE_ATTRIBUTE`. Its own documentation lists the limits — for example, `VECTOR` columns are stored faithfully but there is no similarity search.
+
+TidesDB is released under the Mozilla Public License 2.0, with permissive licenses for its bundled dependencies, and the TideSQL engines under the GPL-2.0. It is actively developed — the latest release, v10.1.1, came out in October 2026 — and has a community on Discord.