Built with the leading voice ecosystem
How it works
From a file to a live call, without opening a dashboard
UNMUTE describes the agent. SLNG runs it. Your coding agent writes the file, validates it against your rules, compiles it and deploys it through the API, with SLNG routing every call underneath in the region you chose.
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.
Agent capabilities
Your agent can preview a change, roll it back, and read what happened on a real call.
Get started
Build a voice agent with UNMUTE and deploy it on SLNG. Install the UNMUTE CLI and skill, create a package from our manifest, run unmute validate and unmute compile, then deploy to SLNG in region eu-west. Docs index: https://docs.slng.ai/llms.txt. UNMUTE: https://unmute.ai.
Can my coding agent build a voice agent end to end?
Yes. With the UNMUTE CLI and skill it describes, validates and compiles the voice agent, then deploys and operates it through the SLNG API.
Do I have to run on SLNG?
No. UNMUTE compiles to Pipecat and LiveKit too, and SLNG can serve the models underneath either.
How do I keep AI agents within our rules?
Save a manifest with the models, providers, languages, regions and tools you allow. Validation fails on anything outside it.
Is UNMUTE open source?
Yes, and it works fully locally for free.

