Globally distributed storage built for read-heavy edge workloads. No database to manage, no infrastructure to provision. Just write, read, and scale.

Most key-value stores lock you into a single compute platform or bury you in database-style complexity. Telnyx KV does neither. It works from anywhere, runs colocated with Telnyx telecom infrastructure, and ships as part of a broader edge compute platform. One account, one API, one bill.

Voice, messaging, storage, compute, and inference on a single API. Your application talks to the same infrastructure that carries the call, stores the data, and runs the model. No patchwork of vendors to reconcile.

Traffic between your functions, storage, and telephony stays on the Telnyx private network. Lower latency, no exposure to public internet routing, no hop through a third-party cloud.

Telnyx infrastructure carries production voice and messaging traffic for enterprises globally. The same network that handles millions of calls powers your edge compute workloads. Tier-1 backbone, redundant routing, 24/7 NOC.
Two access paths, one store. Zero-credential access from edge functions, REST for everything else.
Zero-credential edge access
Your code reaches KV directly from edge functions. No API keys to manage, no extra network hop. The store is available the moment your function runs.
Works from any language
Read and write from Python, Go, Rust, curl, or anything that speaks HTTP. The REST API is a core access path, not an afterthought.
Store any format
JSON, protobuf, raw text, binary. No schema to define, no envelope around your data, no opinions about your format. You choose the serialization.
Automatic expiration
Set a time-to-live on any key and the platform handles the rest. No cleanup jobs, no stale data, no cron-based garbage collection.
Global by default
Write from Chicago, read from Singapore. KV is accessible from any edge function in any region, not pinned to a single zone.
One store, every path
Edge functions and backends share the same data. Write from your function, read from your server. No replication step, no sync lag.
No schemas, no provisioning, no configuration. Create a namespace, write a key, read it back.
# Write a value
curl -X PUT "https://api.telnyx.com/v2/storage/kvs/{namespace_id}/keys/session_123" \
-H "Authorization: Bearer $TELNYX_API_KEY" \
-H "Content-Type: application/octet-stream" \
-d '{"user_id": "42", "role": "admin"}'
# Read it back
curl "https://api.telnyx.com/v2/storage/kvs/{namespace_id}/keys/session_123" \
-H "Authorization: Bearer $TELNYX_API_KEY"Edge functions read and write KV through a typed env binding. No API key, no network hop. The most natural access path for serverless code at the edge.
Learn moreActors use KV for shared state across instances. Session data written by a function is readable from an actor, and vice versa. One store, no sync.
Learn moreStore and retrieve objects from the same edge locations as your functions. Co-located storage means lower latency for your AI workloads.
Learn moreRun LLM inference on GPUs in the same facility as your KV store. No network hops between your data layer and your model serving.
Learn moreGet an API key, create a namespace, and write your first value in under five minutes.
Get an API key, create a namespace, and write your first value in under five minutes.
Telnyx KV is a globally distributed key-value store built for read-heavy edge workloads. You store data under a key and read it back fast from anywhere. It's designed for session data, cached responses, feature flags, and small values your applications need on every request.
KV is purpose-built for simple key-value access, not general-purpose querying. There are no tables to create, no schemas to define, no capacity to provision, and no query language to learn. You store a value under a key and read it back. That's it.
Yes. The REST API works from any language, any host, any environment. Edge function bindings are a convenience for zero-credential access, not a requirement. KV works equally well from your backend, your CLI, or any service that can send HTTP requests.
Any format. KV stores raw bytes, so you can use JSON, protobuf, raw text, or binary. KV does not enforce a format, wrap your data in an envelope, or require base64 encoding. You choose the serialization that fits your use case.
You can set a time-to-live on any key. The platform handles expiration automatically. No cleanup jobs to run, no cron-based garbage collection, no stale data lingering in your store. Keys expire on the schedule you define.
Yes. Edge function bindings and the REST API access the same store. A value written from an edge function is immediately readable from your backend, and vice versa. No replication step, no sync lag, no separate databases to reconcile.
KV is optimized for small values and fast reads. Object Storage is optimized for larger files. Use KV for session data, feature flags, and cached responses. Use Object Storage for images, documents, and backups.
Create a Telnyx account, generate an API key, and create a KV namespace. From there, you can start writing and reading keys via the REST API or an edge function binding. Most users write their first value within five minutes.