Cloudflare KV

At Cloudflare, we have our eyes set on an ambitious goal — to help build a better Internet.

Est 2009|Valuation $112.6B|Raised $3B

	Cloudflare Workers KV	Vercel Edge Config	Upstash Redis
Starting Price	Included with Workers Free; published minimum paid plan available from the vendor	Varies by plan; includes read/write quotas depending on tier	Free tier available; paid plans vary by model
Best For	Read-heavy edge configuration, feature flags, routing maps, allowlists; native Workers-bound applications	Feature flags and configuration inside the Vercel platform	Redis semantics for broader data patterns and atomic operations
Key Strength	Integration with Workers; cost profile favorable for large volumes of cached reads; edge-cached reads for hot data	Integration with Vercel platform and tooling; explicit per-read/write pricing	Redis feature set (data types, atomic operations), managed service options
Key Weakness	Eventual consistency model; documented per-key write limits; cold-read latency can be higher	Costs can increase with scale; platform lock-in trade-offs	Not inherently edge-native in the same way as in-platform KV; network hops may increase latency for some edge scenarios

	Cloudflare Workers KV	Vercel Edge Config	Upstash Redis
Starting Price	Included with Workers Free; published minimum paid plan available from the vendor	Varies by plan; includes read/write quotas depending on tier	Free tier available; paid plans vary by model
Best For	Read-heavy edge configuration, feature flags, routing maps, allowlists; native Workers-bound applications	Feature flags and configuration inside the Vercel platform	Redis semantics for broader data patterns and atomic operations
Key Strength	Integration with Workers; cost profile favorable for large volumes of cached reads; edge-cached reads for hot data	Integration with Vercel platform and tooling; explicit per-read/write pricing	Redis feature set (data types, atomic operations), managed service options
Key Weakness	Eventual consistency model; documented per-key write limits; cold-read latency can be higher	Costs can increase with scale; platform lock-in trade-offs	Not inherently edge-native in the same way as in-platform KV; network hops may increase latency for some edge scenarios

01Competitive Landscape