Private voice AI runtime
Run voice AI on your infrastructure.
Deploy and operate a private voice runtime from a SaaS-like cockpit. Bring your own STT, LLM, TTS and telephony while call audio, transcripts, recordings, provider secrets and tool payloads stay inside your environment.
Public demo runs on Aywa infra for evaluation only. Production traffic runs on the runtime you install.
One private runtime connects voice entrypoints to the providers and data plane you control.
Runtime integrations
Bring the providers your stack already trusts.
Native integrations, compatible APIs, BYO telephony, S3-compatible storage, observability sinks, and customer adapters can coexist inside the same private runtime.
Streaming STT
Voice routes
Telephony and media
Runtime data plane
Production controls
Voice experience engine
Voice-to-voice runtime, optimized for the human turn.
The runtime is built around the real-time phone experience: listening, deciding when the user has finished speaking, streaming the model early, keeping TTS playable on telephony, and measuring latency across every stage without locking the deployment to one provider.
Streaming STT, turn classification, model first-delta tracking, segmented TTS, barge-in, and media playout in one private call/session boundary.
Telephony audio normalization, loudness leveling, soft limiter, speed adjustment, TTS continuity, and a single-output call mixer.
STT preconnect, streaming LLM first-delta tracking, segmented TTS playout, provider retries, fallback voices, and runtime SLO metrics.
Function tools, native call controls, signed server messages, webhook outbox retries, redacted logs, and outbound request allowlists.
For integrators and controlled environments
A production platform without giving up the infrastructure boundary.
Keep the workflow and client experience you already deliver. Aywa standardizes the private execution layer when an agency customer or enterprise needs control of deployment, providers, data and operating costs without assembling a framework into a platform from scratch.
We describe infrastructure tradeoffs as a product category. Aywa Runtime is independently developed and does not imply affiliation with any third-party voice platform.
Run the call path, provider secrets, recordings, tool payloads and runtime logs inside infrastructure you operate.
Use one cockpit for licensing, releases, health and migration while the private runtime stays in your environment.
Choose your STT, LLM, TTS, telephony, storage and observability providers, with customer-owned accounts and keys.
License Aywa separately, pay providers directly and keep provider-minute economics visible without Aywa markup.
Architecture
Control plane outside. Runtime inside your infrastructure.
The SaaS manages licensing, releases, instance health, and migration workflows. The call path, provider secrets, recordings, and telephony edge stay in the customer deployment.
STT, LLM streaming, TTS, barge-in, tools, webhooks, retries, and call state stay in process.
Deployment
One command for trials. Hardened paths for production.
Start on one VPS with the Standard runtime, then move to Enterprise when Aywa needs to help with multi-runtime, HA, load balancing, or custom release channels.
curl -fsSL https://api.aywaruntime.com/v1/installer | \
sudo AYWA_INSTALL_TOKEN="$AYWA_INSTALL_TOKEN" \
RUNTIME_PUBLIC_URL="https://runtime.example.com" \
AYWA_RUNTIME_IMAGE="$AYWA_RUNTIME_IMAGE" \
bash
aywa status
aywa update --channel stable
aywa support-bundle --redact
Private runtime pricing
One production runtime slot. Enterprise when you need more.
Standard is a single licensed private runtime installed on your infrastructure. Aywa charges the runtime license; STT, LLM, TTS, telephony, storage, and analytics stay with your provider accounts, so usage is paid at source with no Aywa platform markup on call minutes.
Runtime license prices exclude applicable taxes. Stripe applies configured VAT or local tax registrations at checkout from the billing address and business tax ID when provided.
Additional Runtime Slots, volume pricing, HA, load balancing, private builds, and accompanied installs are Enterprise custom.
No credit card required for qualified technical evaluations.
One Runtime Slot to validate deployment, import flow, provider credentials, voice-to-voice calls, and call quality.
- 1 private Runtime Slot
- Installer and Docker Compose
- Trial license token
One production Runtime Slot. $49/month or $490/year, before applicable taxes.
For one production deployment with the runtime dashboard on customer infrastructure and provider costs paid directly.
- 1 production Runtime Slot
- Stable release channel
- Open Runtime Dashboard from app.aywaruntime.com
Volume pricing for multiple Runtime Slots.
For teams that need multi-runtime, HA, load balancing, private builds, SLA, or installation led by Aywa.
- Custom Runtime Slots and groups
- Managed Edge / HA architecture
- Private release policies
Enterprise path
When one runtime slot is not enough, we design the deployment with you.
Standard stays intentionally simple: one licensed runtime, installed by the customer. Enterprise is for teams that need multiple runtimes, private release policies, HA/edge design, procurement, security review, or an accompanied production cutover.
Use Enterprise for architecture, not just volume.
We scope runtime topology, rollout gates, provider routing, support boundaries, and operational ownership before any custom contract.
Customer-owned load balancer, SIP/media edge choices, failover expectations, and runbook ownership.
Pinned releases, private channels, rollout windows, and signed images for controlled environments.
Import mapping, provider credential plan, phone-number cutover, and validation calls before traffic.
Data boundary, support bundle policy, access model, audit events, and deployment evidence package.