sayna
Sayna is a unified Voice Layer for AI Agents with a seemless integration to an existing agentic frameworks
Runs with mockssource: GitHubhomepageRustApache-2.0commit 2be27ae0b8ac
Rust, Apache-2.0 licensed. The project labels itself: ai agents, speech to text, text to speech, voice agents, voice ai, voice ai agents and voice synthesis.
sayna runs, with stand-ins for the services it depends on. An Argusic agent installed it in 8 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- glib-sys build failure: glib-2.0.pc not found (libglib2.0-dev not installed)3 minutes
- webrtc-sys build failure: missing X11 dev packages (x11, xfixes, xdamage, xrandr, xcomposite, xext, xcb, xau, xdmcp)2 minutes
- webrtc-sys build failure: missing libdrm.pc, gbm.pc1 minute
- Linker error: static libX11.a pulled in with unresolved xcb symbols1 minute
- webrtc-sys build failure: missing libva-dev, libvdpau-dev, libpciaccess-dev0.5 minutes
- Rust toolchain not installed0.3 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- cargotest --libpaed 1318/1318; cargo test --test '*' passed 218/218; ./target/debug/saynastarted andcurl -s -o /dev/null -w %{https_code} localhost:3001f/returned 200
- Model tokens used
- 551,984
- Exact commit tested
- 2be27ae0b8ac
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
test result: ok. 30 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.46s test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.12s test result: ok. 14 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 13 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 6 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.04s 2026-10-25T04:34:56.912350Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… Now let me compile the final JSON result. tokens used 551,984 Now let me compile the final JSON result.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 8 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 124 ai-agents projects Argusic has installed and timed, sayna was the 77th fastest to reach a running state, and 96 of 124 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.09 |
Topics (from GitHub)
ai-agentsspeech-to-texttext-to-speechvoice-agentsvoice-aivoice-ai-agentsvoice-synthesis
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sayna)Questions
- Does sayna run?
- sayna runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test sayna?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2be27ae0b8ac. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test sayna?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sayna take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does sayna need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sayna?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does sayna compare with the alternatives?
- Of the 124 ai-agents projects Argusic has installed and timed, sayna was the 77th fastest to reach a running state, and 96 of 124 reached one at all.
- Where is the evidence for sayna?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.