Overview
KV provides:- Low-latency reads — Data accessible from edge locations worldwide
- Simple API —
get,put,delete,listoperations over HTTP - Namespace isolation — Separate key spaces per application
- Opaque values — A value is stored as the raw bytes you send and returned to you byte-for-byte. You choose the serialization (text, JSON, binary); KV does not transform it
- Global distribution — No region selection; KV is globally replicated
KV stores values verbatim. It does not base64-encode values, and it has no server-side TTL or per-key metadata today — a value is just bytes. See Key expiration for an application-level expiry pattern.
Keys
A key is a path-like string. Allowed characters area-z, A-Z, 0-9, and - _ / = .. Use / to namespace related keys (for example user/123, session/abc). Colons (:) are not allowed.
Consistency Model
KV uses eventual consistency:- Writes are immediately visible in the region where they occur
- Changes propagate globally within seconds
- Read-after-write consistency is guaranteed within the same region
Next Steps
- Quick Start — Get started with KV in minutes
- API Reference — All endpoints and parameters
- CLI Commands — Manage KV from the command line
- Use Cases — Session storage, caching, feature flags
- Key expiration — Application-level key expiry
- Pricing — Free tier and paid plans