An Otter.ai alternative with no bot in the attendee list
Otter announces itself to everyone in the room and keeps the recording on its servers. Oats does neither.
Short answer: Otter's assistant joins your meeting as a visible participant and uploads the conversation for processing. Oats captures the same audio through your Mac's own output, transcribes it on the device, and never contacts a server. Otter Business runs $19.99/month; Oats is free.
Otter vs Oats, side by side
| Otter.ai | Oats | |
|---|---|---|
| Bot joins the call | Yes — visible participant | No |
| Others can see you're recording | Yes | Only if you tell them |
| Where audio is processed | Their cloud | Your Mac |
| Works with no internet | No | Yes |
| Account required | Yes | No |
| Free tier | 300 min/month | Unlimited |
| Paid plans | Pro $8.33/mo · Business $19.99/mo | $0 |
| Minute caps | Yes, per tier | None |
| Source code | Closed | Open (MIT) |
Otter pricing as of July 2026, from otter.ai/pricing.
The bot is the actual problem
Otter's assistant shows up in the participant list with a name on it. That has consequences a feature comparison usually skips:
- It changes the meeting. People speak differently once they can see they're being recorded by software they didn't choose.
- It creates a consent moment you have to manage. Someone always asks. Now you're explaining a vendor's data policy instead of running your agenda.
- It gets blocked. Plenty of corporate Zoom and Teams tenants refuse unknown bots outright, so the notes you were counting on never happen.
- It's a record. The bot's presence is logged in the meeting host's attendee list, permanently, on someone else's infrastructure.
Oats has no such object. It reads the audio your speakers are already playing and the microphone you're already using.
On Otter and model training
In 2025 a federal class action was filed against Otter alleging that conversations were recorded and used to improve its models without consent from everyone on the call. The case is still working through the courts, and an allegation is not a finding — we're not going to pretend otherwise.
The reason we mention it: the lawsuit only makes sense as a question because the audio reaches a server in the first place. With Oats there is no equivalent question to litigate. Your words are never used to train anything, because they never arrive anywhere that could train on them.
Where Otter is genuinely better
- It joins meetings you don't attend. The bot can cover a call while you're elsewhere. Oats needs you in the meeting, because it's listening through your machine.
- Shared team workspaces and admin controls, which Oats has none of.
- Web and mobile access to your notes from any device. Oats notes live on the Mac that recorded them.
If unattended recording is the core of your workflow, Otter does something Oats structurally cannot. If you're in your own meetings and want them to stay yours, that's the trade Oats is built for.