모든 비교 · 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.

로그인 →가격 섹션으로마지막 확인 2026-05-09

01 · 요약

짧게 말하면.

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.

Otter.ai을(를) 사용해야 할 때…

→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.

meetbot을 사용해야 할 때…

→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 · 사양 표

나란히. 과장 없이.

페이지 푸터의 날짜에 인용된 출처에 대해 확인된 숫자. 무언가 변경되면 PR로 수정해 주세요.

	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 · 가격 시나리오

계산, 세 가지 방식.

세 가지 사용 지점: 취미가, 스타트업, 규모 있는 회사. 셀별 공식 가시화 — 스프레드시트에 복사하고 자신의 숫자를 넣으세요.

시나리오 1

Hobbyist · 10 hr / mo

월 10시간의 회의 녹화.

meetbot

10 hr × $0.30 = $3.00

$3.00/월

Otter.ai

1 user × Pro $16.99 = $16.99

$16.99/월

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.

시나리오 2

Startup · 1,000 hr / mo

월 1,000시간의 회의 녹화.

meetbot

1,000 hr × $0.30 = $300

$300/월

Otter.ai

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

$900/월

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.

시나리오 3

Scale · 50,000 hr / mo

월 50,000시간의 회의 녹화.

meetbot

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

$10,550/월

Otter.ai

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

$45,000/월

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 · 그들이 이기는 곳

Otter.ai이(가) 더 나은 선택인 영역.

이 섹션을 포함하는 이유는 그 대안 — 어디서나 우리가 이긴다고 척하는 것 — 이 부정직하고, 부정직한 비교 페이지가 대부분 읽을 가치가 없는 이유이기 때문입니다.

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 · 우리가 이기는 곳

meetbot이 이기는 곳.

각 줄은 그것을 증명하는 docs 페이지로 링크됩니다. 형용사가 아닌 숫자. 아래 날짜 기준 Otter.ai의 공개 표면에 대해 출처화되었습니다.

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.
증거: /pricing
02Raw outputs to your bucket. Per-speaker audio, tab video, captions JSONL, chat JSONL. You build the app, you keep the data.
증거: /#what-you-get
03Your brand on the bot in the meeting, not Otter's. Pass bot_name on dispatch — participants see your product name.
증거: /docs/quickstart
04MIT-licensed SDKs, OpenAPI spec, sample apps. Otter doesn't have an integrate-it-into-your-product story.
증거: 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).
증거: /security

06 · 마이그레이션

전체 전환. 여덟 줄.

같은 형태, 같은 필드, 다른 호스트. Otter.ai 의 bot 디스패치 호출을 meetbot 호출로 교체하세요. webhook 페이로드는 핸들러가 이미 파싱하는 같은 JSON 형태로 도착합니다.

Otter.ai (이전)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 (이후)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

실제로 받는 질문.

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).