Keydb News November 2025 -

November 2025 was a pivotal month for , the high‑performance, multithreaded fork of Redis. The community saw the launch of KeyDB 7.2 , a major release that introduced native Active‑Active replication , Zero‑Copy Persistence , and Built‑in Cloud‑Connector modules.

The serverless offering is ; it is the same KeyDB binary packaged as a managed runtime, preserving the multithreaded performance that differentiates KeyDB from Redis.

Here are the latest updates and announcements from KeyDB in November 2025: keydb news november 2025

KeyDB’s response was swift:

| Metric (Q4 2025) | Value | YoY Change | |------------------|-------|------------| | | 1 200+ (incl. self‑hosted, managed) | +28 % | | Enterprise ARR | $84 M | +32 % | | Global Market Share – In‑Memory DB | 12 % (3rd place) | +3 pts | | Developer Sentiment (StackOverflow) | 4.8/5 | +0.3 | November 2025 was a pivotal month for ,

The answer came in the form of , a release that was announced internally in May 2025 and kept under a tight embargo until the official launch. The codename “Atlas” reflects the project’s ambition: to carry the weight of modern AI, security, and cloud workloads on the shoulders of a single, Redis‑compatible engine.

KeyDB is a high-performance, open-source, Redis-compatible NoSQL database that is designed for modern applications. As a popular in-memory data store, KeyDB is known for its exceptional performance, scalability, and ease of use. In this guide, we will summarize the latest news and updates from KeyDB in November 2025. Here are the latest updates and announcements from

| Time (UTC) | Action | |------------|--------| | | Trail of Bits notifies KeyDB security team (private disclosure). | | 06:45 | KeyDB acknowledges receipt, initiates incident response. | | 07:30 | Core team reproduces the bug and develops a patch. | | 08:10 | Patch 7.0.0‑rc1 released on GitHub with a high severity label. | | 09:00 | Advisory posted on the KeyDB security page, with mitigation steps (disable replication or upgrade). | | 13:45 | Full “hot‑fix” version 7.0.0‑rc2 released, with additional hardening of the replication protocol. | | 14:30 | Public disclosure of CVE‑2025‑3117, CVSS = 9.8. | | 15:45 | Third‑party audit (HackerOne) validates the fix and signs off on a “no‑regressions” report. | | 16:30 | KeyDB announces a $250 k bug‑bounty payout (largest in its history) to the discoverer. |

There has been ongoing discussion within the developer community regarding the pace of KeyDB's development under ownership. While major feature releases have slowed compared to the project's early years, KeyDB remains a foundational part of Snap's internal caching infrastructure.

: Remains superior for TLS-resilient performance . Recent benchmarks show KeyDB often has the lowest throughput impact when encryption is enabled compared to its peers. It is specifically favored for multi-primary write architectures .

In the weeks following the fix, **KeyDB announced a partnership with Security Working Group to establish a “Security‑as‑Code” pipeline for all future releases.