Cloudflare pulled a key-value store out of its internal toolkit, opening Workers KV Instant, a new mode for its Workers KV service, to a private beta. The company’s announcement frames the offering around two claims: data written can be pushed across its network almost immediately, and the “cold read” penalty that has long hit developers fetching a key from an edge location for the first time is removed.
The headline numbers are Cloudflare’s own. Read latency in Instant mode resolves in under two milliseconds at the 99th percentile, which the company says is more than one hundred times faster than classic mode, with 95th-percentile reads measured in microseconds. Spanish tech outlet El Ecosistema Startup, which covered the same launch the day it broke, pulled the underlying comparison table from Cloudflare’s post: p99 reads at 1.62ms for Instant against 287ms for classic (160ms cached), median write replication at 107ms, p99 write replication at 256ms versus 4.38 seconds for classic, and roughly 99% of writes reaching all edge locations in about 250ms. Cloudflare operates more than 300 edge locations.
The noteworthy part is the engine underneath. Cloudflare says KV Instant runs on Quicksilver v2, the globally distributed key-value system it built internally and has relied on since around 2020, noting that nearly every request to its network performs at least one key lookup. Independent technical outlet InfoQ reported in 2025 on how Cloudflare migrated that store from an architecture that kept the full dataset on every server to a tiered caching model, adding local caches, data-center sharded caches, and full replicas on dedicated storage nodes backed by RocksDB, a change driven partly by unsustainable growth in the dataset.
For developers, the pitch is that existing Workers KV code carries over. The familiar get(), put(), list() and delete() API remains, with Cloudflare noting just three operational differences: you must declare Instant mode when creating a namespace, metadata is unsupported (getWithMetadata always returns null), and list operations return all matching keys without pagination. The company also imposes a one-write-per-namespace-per-second ceiling, which it likens to classic KV’s per-key write limit and frames as helping reason about update ordering.
Pricing is a headline differentiator. Cloudflare prices reads (class B operations) at $0.20 per million, sixty percent below classic KV’s $0.50, with class A writes billed per operation at $0.10. The trade-off is storage: Instant is billed at $100 per megabyte per month versus $0.50 per gigabyte for classic. Constraints are tight, with keys capped at 300 bytes, values sized so a namespace stays under one megabyte total, and up to 10,000 key-value pairs per namespace.
Caveats matter here. This is a private beta, so none of the performance figures are independently measured, and most operational detail is unverified. Independent reporting on this specific launch was thin: beyond Cloudflare’s own post and the Spanish outlet’s coverage, much of what circulates online is a repost of the announcement. InfoQ’s piece predates the launch and examines the underlying store rather than KV Instant itself. What is clear is that Cloudflare is exposing the store behind its own infrastructure to customers, at pricing that favors very frequent, very fast reads over cheap bulk storage.