Skip to content
SPECIFICTION
Get listed

SuperMassive

supermassivedb.com

Free plan WindowsmacOSLinuxSelf-hosted
Visit supermassivedb.com
Spec score 7.6 #15 of 31 in Key-Value Databases

What it is

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.

Spec sheet

Product
SuperMassive is an open-source distributed key-value database designed for in-memory operations, durability, and low latency.Read 9 Oct 2026 · github.com
Security
The documentation describes username and password client authentication, shared keys for node communication, and optional TLS.Read 9 Oct 2026 · supermassivedb.com
Support
The repository invites users to join its Discord server to talk with maintainers and other users.Read 9 Oct 2026 · github.com
License
The project is licensed under BSD-3-Clause.Read 9 Oct 2026 · github.com
Availability
The product describes automatic failover and self-healing when nodes fail.Read 9 Oct 2026 · supermassivedb.com
Consistency
Timestamp-based version control resolves conflicts by returning the most recent value.Read 9 Oct 2026 · github.com
Data operations
Supported commands include PUT, GET, DEL, INCR, DECR, REGX, STAT, RCNF, and PING.Read 9 Oct 2026 · github.com
Integration
The documented client connection example uses the text protocol through netcat; no named third-party integrations are listed.Read 9 Oct 2026 · supermassivedb.com
Limit
The repository README states that the system has no transactions and only one user.Read 9 Oct 2026 · github.com
Platform
Prebuilt binaries or source builds are available for Linux, macOS, and Windows.Read 9 Oct 2026 · supermassivedb.com
Project status
GitHub marks the repository archived and read-only as of May 6, 2026.Read 9 Oct 2026 · github.com
Reads
Read operations run in parallel across primary nodes and, if needed, replicas.Read 9 Oct 2026 · supermassivedb.com
Replication
Nodes write operations to journals and replicas synchronize missing journal entries from their primary.Read 9 Oct 2026 · supermassivedb.com
Scaling
The database distributes data across shards and supports adding nodes to scale horizontally.Read 9 Oct 2026 · supermassivedb.com
Writes
Writes are distributed across primary nodes using a sequence-based round-robin approach.Read 9 Oct 2026 · supermassivedb.com

Plans and prices

BSD-3-Clause open-source license Free No commercial plans or pricing listed on the official site Read 9 Oct 2026 · supermassivedb.com

Every SuperMassive plan and price →

Strong points and limits

Strong points

  • Free under the BSD-3-Clause license.
  • Distributes data across shards and supports adding nodes.
  • Describes automatic failover and self-healing.
  • Offers optional TLS and node shared keys.

Limits

  • No transactions, according to the README.
  • README says the system supports only one user.
  • Repository is archived and read-only.

Who it suits

It suits developers seeking a self-hosted distributed key-value database across Linux, macOS, or Windows. The stated limits of no transactions and one user, along with its archived status, matter when assessing fit.

Verdict

SuperMassive documents its clustering, replication, commands, and security approach, with no charge listed. Its single-user limit, lack of transactions, and archived repository are significant constraints to weigh.

Where Specifiction places it

Alternatives to SuperMassiveAll alternatives →