UNMUTE// is LIVE. An open standard for declaring voice agents. HERE

SLNG

Sydney

Voice agent infra running locally in Australia

Keep your models. Keep your orchestrator. Less cost and latency per call. Your audio stays in Australia.

Use cases

Pricing tailored to your use case

Tap a layer to switch it between SLNG and your own keys

Execution LayerSLNGAlways on

Execution Layer only

Optimise your existing agent

Keep your orchestrator, STT, LLM, and TTS. SLNG adds the execution layer — cache, routing, governance, marking.

  • Execution Layer+ US$ 0.001

US$ 0.001/ agent minute

Continuous optimization

What runs on every call

The Execution layer stacked between your orchestrator and your models. Running locally in Sydney.

PII redaction

Stripped before audio reaches your models or logs.

TTS Smart caching

Repeated TTS responses served from cache. Provider never gets called.

LLM routing

Simple turns stay local. Complex turns hit your LLM. Fewer model calls per conversation.

Transcripts

Region, provider, model, cost, latency. Logged per step, per call.

Analytics

Cost and latency tracked against baseline. Dashboard shows the delta.

In-region compute

One line decides where everything runs.

Choose a regional endpoint for your voice infrastructure.

Base URL

https://id.api.slng.ai

One line decides where everything runs.

ISO 27001

Certified

SOC 2 Type II

Certified

HIPAA

Compliant

GDPR

Compliant

Agentic voice

From a file to a live call, without opening a dashboard

Your coding agent writes the file, validates it against your rules, compiles it and deploys it through the API, with SLNG routing every call locally in Australia.

Define

One UNMUTE file holds the whole agent. Prompt, models, tools, channels. Your coding agent writes it, you review it like any other code.

Govern

A saved manifest sets your company's rules: which models and providers, which languages and regions, which deployment targets and tools.

Compile and ship

Violations fail at compile, not on a call. The same package targets Pipecat, LiveKit or SLNG, then deploys, versions and rolls back through the API.

Own your voice AI stack

Run one call. Read the numbers.

Point your agent at SLNG and check the dashboard tomorrow. Latency and cost, measured against what you had before.

Is SLNG data-compliant?

SLNG is ISO 27001 and SOC 2 Type II certified. HIPAA compliant. GDPR compliant. PII redaction built in.

How is SLNG different from calling Deepgram or OpenAI directly?

The SLNG Execution layer sits between your orchestrator and your models. You keep your existing providers. The execution layer adds LLM routing, smart caching, PII redaction, and analytics, reducing cost and latency on every call. Running in Mumbai means no round-trips to US servers.

Can I bring my own model API keys?

Yes. BYOK is the default. Bring your existing OpenAI, Anthropic, Deepgram, or ElevenLabs keys. The SLNG Execution layer routes through them, adding routing, caching, and observability without changing your provider contracts.

Is SLNG suitable for regulated environments?

Yes. SLNG enforces region and country rules at runtime. Enterprise plans add residency, retention, auditability, and SLA-backed guarantees for regulated workloads.

Does my voice AI data stay in-region?

Yes. Audio processed in a region stays in that region. Every call is logged with region, provider, model, and timestamp. You swap your base URL to the region of your choice.

How is SLNG priced?

US$ 0.001 per agent minute for the Execution layer. Same price as every other region. STT and TTS add-ons are each US$ 0.003 per agent minute with model costs included. No contracts, no minimums, no regional surcharges.

Define. Govern. Execute.

SLNG

© 2026 SLNG