Apache Kvrocks vs SuperMassive
Apache Kvrocks
kvrocks.apache.org
SuperMassive
supermassivedb.comSide by side
| Figure | Apache Kvrocks | SuperMassive |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Key-Value Databases | 7.6 (#12) | 7.6 (#15) |
| License | Apache Kvrocks is licensed under Apache License Version 2.0. | The project is licensed under BSD-3-Clause. |
| Product | Apache Kvrocks is a distributed key-value NoSQL database that uses RocksDB as its storage engine and is compatible with the Redis protocol. | SuperMassive is an open-source distributed key-value database designed for in-memory operations, durability, and low latency. |
| Replication | Kvrocks supports asynchronous replication using a binlog approach described as similar to MySQL. | Nodes write operations to journals and replicas synchronize missing journal entries from their primary. |
| Security | The project’s 2023 review lists replication with TLS among its progress that year. | The documentation describes username and password client authentication, shared keys for node communication, and optional TLS. |
| Support | The project links users to its Zulip community, issue tracker, and mailing list. | The repository invites users to join its Discord server to talk with maintainers and other users. |
Plans
In their own words
Apache Kvrocks
Apache Kvrocks has no write-up on Specifiction yet; its figures are above.
SuperMassive
SuperMassive is a self-hosted, open-source key-value database built for in-memory work, durability, and low latency. It spreads data across shards, and additional nodes can expand capacity horizontally. Writes rotate among primary nodes in sequence; reads run in parallel across primaries and, when needed, replicas. The project describes automatic failover and recovery when a node fails. Timestamp-based versioning settles conflicts in favor of the latest value. Commands include PUT, GET, DEL, INCR, DECR, REGX, STAT, RCNF, and PING. Nodes journal operations, while replicas copy any missing journal entries from their primary. Client connections use username-and-password authentication; nodes can use shared keys, and TLS is optional. Linux, macOS, and Windows builds are available as binaries or source, under the BSD-3-Clause license. The README identifies two limits: no transactions and only one user. GitHub marks the repository archived and read-only as of May 6, 2026.