SuperMassive
supermassivedb.com
- Free plan
- Windows
- macOS
- Linux
- Self-hosted
What SuperMassive is
SuperMassive is a self-hosted, open-source key-value database built for in-memory operations, durability, and low latency. It spreads data across shards, and nodes can be added for horizontal scaling. Writes are distributed among primary nodes in sequence-based round-robin order; reads run in parallel across primaries and, when needed, replicas. The project describes automatic failover and self-healing when nodes fail. Timestamp-based version control resolves conflicts by keeping the most recent value. Supported commands include PUT, GET, DEL, INCR, DECR, REGX, STAT, RCNF, and PING. Nodes write operations to journals, and replicas synchronize missing entries from their primary. Client authentication uses usernames and passwords; shared keys can secure node communication, with optional TLS. Prebuilt binaries and source builds are available for Linux, macOS, and Windows. SuperMassive uses the BSD-3-Clause license and has no listed commercial pricing. The repository README says it has no transactions and supports only one user. Its GitHub repository is archived and read-only as of May 6, 2026.
Who it suits
SuperMassive may suit technical teams seeking a self-hosted distributed key-value database on Linux, macOS, or Windows. Its stated limits and archived repository status are important considerations for anyone evaluating it.
Good to know, and what to watch
- Open source under the BSD-3-Clause license
- Supports scaling by adding nodes
- Describes automatic failover and self-healing
- Offers optional TLS for node communication
- No transactions
- Supports only one user
- GitHub repository is archived and read-only
Plans
Every plan and priceBSD-3-Clause open-source license
Open source
Getting started
- Open the SuperMassive website or repository
- Choose a prebuilt binary or build from source
- Install on Linux, macOS, or Windows
- Run the database in a self-hosted deployment
- Connect through the text protocol, such as with netcat
- Configure username/password authentication and optional TLS
Limits to check
The repository README states that SuperMassive has no transactions and only one user. Its GitHub repository is archived and read-only as of May 6, 2026.
The verdict
SuperMassive describes distributed storage, replication, and failover for in-memory key-value operations. Its README lists no transactions and one user, and the archived, read-only repository is a key project status consideration.
Questions people ask
What is SuperMassive?
It is a distributed key-value database for in-memory operations, durability, and low latency.
Is SuperMassive free?
Yes. It is open source under the BSD-3-Clause license, with no commercial plans or pricing listed.
Which operating systems can run it?
Prebuilt binaries or source builds are available for Linux, macOS, and Windows.
Does it support clustering and persistence?
Yes. Data is distributed across shards for clustering, and the product supports both in-memory and durable persistence modes.
What are its documented limitations?
The README says there are no transactions and only one user. GitHub marks the repository archived and read-only.
What the maker publishes
- Availability
- The product describes automatic failover and self-healing when nodes fail. source
- Consistency
- Timestamp-based version control resolves conflicts by returning the most recent value. source
- Data operations
- Supported commands include PUT, GET, DEL, INCR, DECR, REGX, STAT, RCNF, and PING. source
- Integration
- The documented client connection example uses the text protocol through netcat; no named third-party integrations are listed. source
- License
- The project is licensed under BSD-3-Clause. source
- Limit
- The repository README states that the system has no transactions and only one user. source
- Platform
- Prebuilt binaries or source builds are available for Linux, macOS, and Windows. source
- Product
- SuperMassive is an open-source distributed key-value database designed for in-memory operations, durability, and low latency. source
- Project status
- GitHub marks the repository archived and read-only as of May 6, 2026. source
- Reads
- Read operations run in parallel across primary nodes and, if needed, replicas. source
- Replication
- Nodes write operations to journals and replicas synchronize missing journal entries from their primary. source
- Scaling
- The database distributes data across shards and supports adding nodes to scale horizontally. source
- Security
- The documentation describes username and password client authentication, shared keys for node communication, and optional TLS. source
- Support
- The repository invites users to join its Discord server to talk with maintainers and other users. source
- Writes
- Writes are distributed across primary nodes using a sequence-based round-robin approach. source
Checked against the maker's pages on 9 Oct 2026.