WHY TELNYX
Not just compute. A platform.
Most edge compute platforms run your code and stop. You wire up storage, state, inference, and telephony from separate vendors. Functions runs as containers on infrastructure Telnyx owns and operates. KV, Stateful Actors, Object Storage, and Inference are connected through bindings, not API calls.
One platform, zero hops
Functions, KV, Stateful Actors, Object Storage, and Inference on one account, one API, one bill. Bindings connect them with no credentials and no network hops.
Owned infrastructure
Runs on infrastructure Telnyx owns and operates. Multiple independent sites per region with automatic failover. Not rented cloud capacity in a CDN PoP.
Built for AI agents
A function receives a request, loads agent state, calls inference on GPUs in the same facility, and responds. The orchestration, state, and models are on one platform with no hops between them.
FEATURES
Everything you need to ship. Nothing you don't.
Write a server. Run telnyx-edge ship. Get a public URL.
Platform architecture
Functions is the compute entry point. KV, Stateful Actors, Object Storage, Inference, and the Telnyx API are all on the same owned infrastructure, connected through bindings.
Any runtime, any language
Functions run as containers, not V8 isolates. TypeScript, Go, Python, Java, Rust, or any runtime that runs in a container. Use any package, any system library, any framework. No sandbox limitations.
Zero-credential bindings
Access KV, Stateful Actors, Object Storage, and Inference through bindings, not API calls. No credentials in your code, no auth headers, no secret rotation. The platform wires services together at the infrastructure layer.
Global edge distribution
Deploy once, run at every edge site. The platform handles routing to the nearest PoP automatically. No multi-region config, no DNS management, no cold-start regions. Your code is everywhere your users are.
Automatic TLS and custom domains
Every function gets a public URL with TLS by default. Bring your own domain and upload your own PEM certificate. The platform handles routing, you control the certificate chain, CA, and rotation schedule.
Pre-authenticated telecom access
A built-in binding connects to the Telnyx Voice and Messaging API. Make calls, send messages, and build voice agents from inside a function without managing API keys. Telecom is a function call, not an integration project.
CUSTOM DOMAINS
Serve Edge Compute Functions from your own domain.
Most serverless platforms auto-provision TLS and give you no control over the certificate chain. Custom domains let you bring your own PEM certificate, choose your CA, and manage your own rotation schedule.
Bring your own certificate
Upload a PEM-encoded certificate and private key. Any CA, any key size, any chain length. Stored encrypted with AES-GCM.
One-time DNS verification
Prove domain ownership with a single TXT record. No re-verification when you rotate certificates.
Zero-downtime routing
Your custom domain and the default telnyxcompute.com URL serve traffic simultaneously. Migrate at your own pace.
Up to 25 domains per org
Point multiple domains at the same function. No per-function restriction.
KV
Session data, cached responses, feature flags. Read and write from inside your function with no API key, no SDK, no network hop.
Learn more
Stateful Actors
Per-entity state. Delegate read-modify-write operations to an actor instance through a binding. The actor handles concurrency so your function does not have to.
Learn more
Object Storage
File access. Read and write files from inside your function. Same infrastructure, no credentials, no hop.
Learn more
Inference
Model calls. Invoke frontier open-source models on owned GPUs from your function. Sub-200ms round-trip when function and model are in the same facility.
Learn more
