Toutes les comparaisons · vs Otter.ai

meetbot vs Otter.ai.

This page exists because Otter shows up in every "meeting recording" search. We're not the same product: Otter is the end-user SaaS, and meetbot is the developer API a product like Otter would be built on. Below we explain the framing, the price shape (per-seat vs per-hour), and when you'd pick one over the other. If you arrived here looking for a meeting-notes app for yourself, the honest answer is: install Otter. If you're a developer shipping a feature that records meetings, read on.

Se connecter →Aller aux tarifsvérifié le 2026-05-09

01 · résumé

La version courte.

01Otter sells per-seat to humans who attend meetings ($16.99–$30/user/mo). meetbot sells per-hour to developers shipping meeting features ($0.30/hr).
02Different shapes of customer, different shapes of price. We're not competing for the same buyer.
03If you're building a SaaS that includes meeting recording — a CRM, an ATS, a coaching app, a sales-intelligence tool — you need an API. Otter doesn't sell one.

Utilisez Otter.ai si…

→You're an end-user who wants a meeting-notes app on your phone and laptop.
→Your team needs a finished SaaS workflow today: recording, summary, action items, search.
→You'll never integrate the recording into your own product — you just want to use it.
→You want their consumer apps (iOS, Android, macOS, Windows, Chrome ext.) which are mature.

Utilisez meetbot si…

→You're building a SaaS product where recording-the-meeting is a feature.
→You need raw signals (per-speaker audio, captions, chat) — not a polished UI on top of them.
→You bill your customers per-seat or per-account; you want infra costs that match (per-hour, not per-seat).
→You want to put your brand on the bot in the meeting — not Otter's.

02 · tableau des spécifications

Côte à côte. Sans esbroufe.

Chiffres vérifiés contre la source citée à la date dans le pied de page. Faites une PR de correction si quelque chose a bougé.

	meetbot	Otter.ai
what is it	developer API (HTTP + SDKs)	SaaS app (web + mobile + Chrome ext)
primary buyer	engineering team building a product	individual or team end-user
pricing shape	$0.30 / hr of meeting time	$16.99–$30 / user / month^[1]
per-hour at 40 hr/mo Business	$0.30	~$0.50 ($30 ÷ 60 hr cap × 40 hr / 40 hr)^[2]
free tier	$5 one-time welcome credit	300 minutes / month^[3]
raw outputs (audio · video · captions · chat)	yes — to your S3 bucket	no — locked in app
brand the bot	yes (configurable bot_name)	no — bot is OtterPilot
platforms	Meet, Teams, Zoom Web, Zoom SDK, Webex, Whereby, Jitsi, Discord	Meet, Teams, Zoom, Webex
consumer apps	—	iOS, Android, macOS, Windows, Chrome ext
transcription quality	BYOK (Whisper, Deepgram, AssemblyAI on your own key); hosted Whisper-large-v3 ships Q3 2026	Otter ASR (well-tuned)
summarisation	BYO LLM via webhook payload	built-in (Otter AI Chat)

[1]pricing shape: otter.ai/pricing
[2]per-hour at 40 hr/mo Business: otter.ai/pricing
[3]free tier: otter.ai/pricing

03 · scénarios tarifaires

Le calcul, en trois temps.

Trois points d'usage : un hobbyiste, une startup, une entreprise à l'échelle. Formule visible par cellule — copiez-la dans un tableur, mettez vos propres chiffres.

scénario 1

Hobbyist · 10 hr / mo

10 heures d'enregistrement de réunion par mois.

meetbot

10 hr × $0.30 = $3.00

$3.00/mois

Otter.ai

1 user × Pro $16.99 = $16.99

$16.99/mois

Different products. If you're a person who attends 10 meetings, Otter is the right purchase — you get a UI. We give you four files in a bucket.

scénario 2

Startup · 1,000 hr / mo

1,000 heures d'enregistrement de réunion par mois.

meetbot

1,000 hr × $0.30 = $300

$300/mois

Otter.ai

30 users × Business $30 = $900 (capped per-user hours)

$900/mois

Apples to oranges: 30 Otter seats also gives you 30 humans using a polished app. 1,000 meetbot hours gives you raw signals ready to be ingested by your own product.

scénario 3

Scale · 50,000 hr / mo

50,000 heures d'enregistrement de réunion par mois.

meetbot

1,000 hr × $0.30 + 9,000 hr × $0.25 + 40,000 hr × $0.20 = $10,550

$10,550/mois

Otter.ai

1,500 users × Business $30 = $45,000

$45,000/mois

At this scale you almost certainly aren't using Otter — you're building your own product on top of an infra layer like meetbot. The number is included for completeness, not as a real choice.

04 · là où ils gagnent

Là où Otter.ai est le meilleur choix.

Nous incluons cette section parce que l'alternative — prétendre gagner partout — est malhonnête, et les pages de comparaison malhonnêtes sont la raison pour laquelle la plupart ne valent pas la peine d'être lues.

01You're a person, not a product. Otter is a great app — install it on your phone, attend meetings, get summaries. We don't ship a phone app and won't.
02Native consumer apps everywhere — iOS, Android, macOS, Windows, Chrome extension. Mature, fast, polished.
03Built-in summarisation, action-item extraction, in-meeting AI chat. We give you raw audio + native captions and trust you to build that yourself (or pipe per-speaker audio into the transcription provider of your choice).
04A consumer-grade recorder UX, calendar polish, and mature mobile/desktop apps. We cover Webex through the meeting-bot API, but we are not trying to replace Otter as a notes app.
05Brand recognition. End-users have heard of Otter. They haven't heard of meetbot.

05 · là où nous gagnons

Là où meetbot gagne.

Chaque ligne renvoie à la page docs qui le prouve. Des chiffres, pas des adjectifs. Sourcé contre la surface publique de Otter.ai à la date ci-dessous.

01We're the API your product would use. Per-hour pricing matches per-hour usage; per-seat (Otter) matches per-seat usage and breaks down when one customer of yours runs 200 meetings/month.
preuve : /pricing
02Raw outputs to your bucket. Per-speaker audio, tab video, captions JSONL, chat JSONL. You build the app, you keep the data.
preuve : /#what-you-get
03Your brand on the bot in the meeting, not Otter's. Pass bot_name on dispatch — participants see your product name.
preuve : /docs/quickstart
04MIT-licensed SDKs, OpenAPI spec, sample apps. Otter doesn't have an integrate-it-into-your-product story.
preuve : github.com/meetbot
05EU-hosted. If your customers ask 'where does the recording live before it gets to your servers,' the answer is Falkenstein, not OtterCloud (whose location is unspecified for non-enterprise tiers).
preuve : /security

06 · migration

Tout le changement. Huit lignes.

Même forme, mêmes champs, hôte différent. Remplacez votre appel de dispatch de bot Otter.ai par un appel meetbot. Les payloads webhook arrivent dans la même forme JSON que votre handler parse déjà.

Otter.ai (avant)ts

// Otter doesn't have a public bot-dispatch API.
// Their integration story is "your users sign in to Otter
// and it joins their meetings via OtterPilot."
// You can't programmatically dispatch a bot to a URL.
//
// If your product needs to drop a bot in a meeting on
// behalf of your customer — without your customer signing
// in to a third-party app — you need an infra API.

meetbot (après)ts

// meetbot — drop a bot in any meeting, metered by the second
const res = await fetch("https://api.meetbot.dev/api/v1/bot", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.MEETBOT_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    meeting_url: "https://meet.google.com/abc-defg-hij",
    bot_name: "YourProduct",
    webhook_url: WEBHOOK_URL,
  }),
});

07 · faq

Les questions qu'on nous pose vraiment.

Q.Why are you comparing yourself to Otter at all?

Because they show up in the same searches. We'd rather acknowledge it directly than pretend they don't exist or pretend we compete for the same buyer. The honest answer is: different products, different buyers, different pricing shapes. This page exists so the right reader picks the right tool.

Q.Can I use Otter's API to build my product?

Otter has limited API surface focused on workspace integration (importing existing recordings, SSO). There is no public "drop a bot in this meeting URL, send me the recording" endpoint. If that's what you need, you need an infra API — meetbot, Recall.ai, MeetingBaaS, Vexa, or Attendee.

Q.What about Fireflies / Read / Sembly / Bluedot?

Same framing — they're SaaS apps for end-users with per-seat pricing, not infra APIs for developers. If you're building a product, none of those are the right shape. We may write per-vendor pages for each over time; for now this Otter page is the canonical "infra-vs-SaaS" framing.

Q.I'm an end-user who came to this page by accident. What should I do?

Try Otter. It's a good product, with mature mobile apps and a polished summarisation flow. We don't ship anything for end-users and don't intend to.

Q.How do I know which side I'm on?

Quick test: if your meeting recording would end up displayed inside another piece of software you're building, you need an API (meetbot). If your meeting recording would end up displayed inside an app you opened on your phone, you need a SaaS (Otter).