# dicedb/dicedb

Open-source, low-latency key/value engine built on Valkey with query subscriptions and hierarchical storage tiers.

Repository: https://github.com/dicedb/dicedb
Canonical: https://ross.abutalabs.com/products/dicedb
Homepage: https://dicedb.io/
Language: C
License: NOASSERTION
License Family: other
Topics: database, storage-engine, cache, key-value, key-value-store, nosql, redis, valkey
Last push: 2026-04-23T01:00:36+00:00

## Health v2 (maintenance only)
Score: 68/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 78, release rhythm 38, longevity 100
- inputs: {"age_days": 1463, "days_push": 133, "days_rel": 203, "gap_med": null, "n_releases_24m": 1}
- 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 10772, forks 1397 (observed 2026-08-28T04:10:44.226918+00:00)

## What it is
DiceDB is an open-source, low-latency key/value data store forked from Valkey (itself a fork of Redis), written in C. It extends Valkey with query subscriptions via OBSERVE commands and a spill module that transparently persists evicted keys to disk (RocksDB), while remaining fully compatible with Redis and Valkey clients, SDKs, and tooling.

## Use cases
- run a redis-compatible in-memory cache
- store datasets larger than RAM with tiered disk spilling
- subscribe to query changes and get real-time push updates instead of polling
- self-host a drop-in replacement for redis or valkey
- use a key-value store for caching and message queues
- migrate existing redis workloads without changing client SDKs

## When to choose
- you want Redis/Valkey compatibility with extra features like query subscriptions and disk spilling
- your working set exceeds available memory but hot data must stay in-memory fast
- you need reactive push-based updates to query results in live applications
- you want an open-source (BSD-3-Clause) self-hosted data store deployable via Docker

## When to avoid
- you need the mature, battle-tested Redis or Valkey codebase without fork risk
- you rely on features from the archived Go-based legacy DiceDB implementation
- you need strict license clarity - the GitHub license is marked NOASSERTION despite the site claiming BSD-3-Clause
- you need multi-model capabilities like document or graph storage

## Facets
- artifact type: service
- maturity: active
- function: database, caching, message-queue, streaming
- domain: databases, backend, self-hosted
- platform: windows, self-hosted, cpp
- tags: key-value-store, redis-compatible, valkey-fork, in-memory-database, storage-engine, nosql, query-subscriptions, tiered-storage, real-time, linux, macos, docker

## Member repositories
- dicedb/dicedb (main) score 68

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:44.226918+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:17:52.885075+00:00, confidence not recorded.
  - readme: https://github.com/dicedb/dicedb (fetched 2026-08-28T04:10:44.226918+00:00, sha 8da08f657e86)
  - homepage: https://dicedb.io/ (fetched 2026-08-29T08:16:47.359669+00:00, sha 5aec88cd9812)
  - site_page: https://dicedb.io/docs (fetched 2026-08-29T08:16:47.368914+00:00, sha c7de8c0a347e)
- Data as of 2026-08-30T08:39:29.467469+00:00.