Workers KV Instant: Cloudflare brings Quicksilver speed to KV data

Cloudflare announced a new mode for Workers KV called Workers KV Instant, powered by its internal Quicksilver v2 key-value store. According to the Cloudflare Blog, KV Instant provides the same API as Workers KV but pushes updates globally for immediate availability and much lower read latency.

What Cloudflare said about Workers KV Instant

Cloudflare Blog reports KV Instant delivers read latency that is over 100 times faster than classic Workers KV, with p99 reads resolving in under two milliseconds and p95 reads measured in microseconds. Writes are propagated to the edge more than 20 times faster, with 99% of all writes replicating in around 250 milliseconds. Cloudflare also notes KV Instant uses Quicksilver v2, the same system they run on the hot path of many Cloudflare products.

KV Instant exposes the familiar Workers KV API calls like get(), put(), list(), and delete(), so existing code that uses those calls will be familiar. Cloudflare says the new mode is aimed at data that is written infrequently and read frequently, such as feature flags or global configuration that must be available everywhere immediately after a change.

How KV Instant differs from classic Workers KV

According to the Cloudflare Blog, KV Instant keeps the same basic API but has several important behavioral and billing differences you need to know:

• You must specify mode: namespaces are created with the attribute "mode": "instant".
• Metadata is not supported, so getWithMetadata returns null and you cannot attach metadata in put or list operations.
• list operations return all matching keys with no pagination.
• Write frequency is limited to one write per namespace per second because writes go through a single system of record.
• Storage is tightly constrained: each key can be up to 300 bytes, an Instant namespace can hold up to 10,000 key value pairs and the whole namespace cannot exceed one megabyte.
• Cloudflare says KV Instant propagates data to every Cloudflare location, and the table notes reference "over 300" edge locations as of publication.

Pricing and operational tradeoffs, as reported

Cloudflare Blog states reads in KV Instant are priced 60% lower than classic Workers KV reads, reflecting the product focus on read-heavy, small-data workloads. However, storage and Class A operations are substantially more expensive than classic Workers KV. The blog lists pricing dimensions for Instant namespaces: price per million Class B operations (reads), per Class A operation (put, delete, list), and per MB of storage. Cloudflare frames the two modes as complementary: classic Workers KV remains a good fit when you need to store larger amounts of data or update frequently, while KV Instant targets small, read-heavy configuration data.

Who should consider KV Instant

Cloudflare presents KV Instant as suited for data that is read on the hot path and updated rarely, for example feature flags or global routing settings that must take effect immediately worldwide. The Cloudflare Blog points to a common scenario: switching what shows on a homepage at a precise moment, where you need nearly zero read latency and instant visibility of updates across the globe.

If your application depends on large values, frequent updates, metadata, or paginated key listings, Cloudflare indicates classic Workers KV will remain the better fit.

Practical steps for teams that run sites or APIs

• Inventory the small bits of state your application reads on every request, such as feature flags, A/B routing keys, or small configuration values.
• Compare access patterns to Cloudflare's limits: KV Instant supports up to 10,000 keys and a 1 MB namespace size, keys up to 300 bytes, and one write per namespace per second.
• Model expected costs using Cloudflare's pricing: reads will be cheaper but storage and writes are billed differently than classic Workers KV.
• If you need metadata, pagination, or frequent large writes, plan to keep those items on classic Workers KV or another store.
• If this looks promising, apply for Cloudflare's private beta of KV Instant via the Cloudflare Blog sign-up and test your workload under the stated limits.
• If you want help evaluating whether your WordPress, Formidable Forms, or custom app should try KV Instant, contact our team at /contact.html.

Final note

KV Instant is in private beta, according to the Cloudflare Blog, and Cloudflare says it wants customer feedback as it expands availability. The announcement frames KV Instant as a specialized option for globally replicated, read-heavy, small-data use cases where immediate updates and very low read latency matter.