meetbot.dev

Wszystkie porównania · vs Attendee

meetbot vs Attendee.

Attendee is the closest in spirit to meetbot — a developer-first, source-available, Docker-friendly meeting-bot stack with a clean dev experience. The two substantive differences: license (they're Elastic 2.0 across the stack, our SDK + samples are MIT — bot binary closed) and platform coverage today (they ship Meet + Zoom; we ship eight API surfaces: Meet, Teams, Zoom Web, Zoom SDK, Webex, Whereby, Jitsi, and Discord). Their hosted free tier is genuinely good for prototyping; their paid tier pricing isn't publicly listed yet.

Zaloguj się →Przejdź do cenostatnio zweryfikowano 2026-05-09

01 · w skrócie

Krótka wersja.

Użyj Attendee jeśli…

  • →Your stack is Meet + Zoom only and won't need Teams.
  • →You want the simplest possible self-host experience today (their Docker compose is excellent).
  • →You're fine with ELv2 license terms and don't plan to ship a competing hosted product.
  • →You want their specific dev-tooling polish — the Attendee dashboard is sharp.

Użyj meetbot jeśli…

  • →You need Teams, Webex, Whereby, Jitsi, Discord, or both Zoom Web and Zoom SDK surfaces today.
  • →Your business model might one day include reselling recording-as-a-service — ELv2 forbids that, MIT doesn't.
  • →You want published, predictable pricing instead of a sales conversation for paid tiers.
  • →You want signed webhook delivery logs and helper SDKs, not only a raw webhook endpoint.

02 · tabela specyfikacji

Obok siebie. Bez ściemy.

Liczby zweryfikowane wobec cytowanego źródła w dacie z stopki strony. Zrób PR z poprawką, jeśli coś się zmieniło.

meetbotAttendee
platforms todayMeet, Teams, Zoom Web, Zoom SDK, Webex, Whereby, Jitsi, DiscordMeet, Zoom (Teams + Webex on roadmap)[1]
SDK license
ELv2 prohibits offering a competing hosted service.
MITElastic License 2.0[2]
self-host storyM5 (source-available)Docker compose today[3]
hosted pricing$0.30 / hr entry rate, published volume tiersfree tier; paid not listed[4]
transcriptionBYOK today (free pass-through on per-speaker audio); hosted Whisper-large-v3 ships Q3 2026BYOK (Deepgram, etc.)
transportswebhook · websocket · RTMPwebhook · websocket
data residencyHetzner Falkenstein (DE)self-host: anywhere; hosted: not specified
pricing exposedthis pageafter a sales conversation (paid)
production maturitypre-launch (zero paying customers today; sample apps + daily smoke tests against real meetings)growing fast, similar early stage
OAuth-managed signed-in botsM3 (Zoom · Meet · Teams); URL-based guest bots ship across all 8 surfacesyes (Zoom, Meet)
  1. [1]platforms today: attendee.dev/
  2. [2]SDK license: github.com/attendee-labs/attendee
  3. [3]self-host story: github.com/attendee-labs/attendee
  4. [4]hosted pricing: attendee.dev/

03 · scenariusze cenowe

Matematyka, na trzy sposoby.

Trzy punkty użycia: hobbysta, startup i firma w skali. Wzór widoczny w każdej komórce — skopiuj do arkusza, wstaw swoje liczby.

scenariusz 1oni tu wygrywają

Hobbyist · 10 hr / mo

10 godzin nagrywania spotkań miesięcznie.

meetbot
10 hr × $0.30 = $3.00
$3.00/mies.
Attendee
free tier (assumed) = $0
$0/mies.

Attendee's hosted free tier covers this if your bot count fits. We can't predict their paid tier. If $3/mo is your gating cost, hosted Attendee wins; otherwise indistinguishable.

scenariusz 2

Startup · 1,000 hr / mo

1,000 godzin nagrywania spotkań miesięcznie.

meetbot
1,000 hr × $0.30 = $300
$300/mies.
Attendee
paid tier (not listed) — sales conversation required
?/mies.

We can't quote because Attendee's paid tier isn't public. If you need predictable pricing for your finance model, that's a real edge for us at this scale.

scenariusz 3

Scale · 50,000 hr / mo

50,000 godzin nagrywania spotkań miesięcznie.

meetbot
1,000 hr × $0.30 + 9,000 hr × $0.25 + 40,000 hr × $0.20 = $10,550
$10,550/mies.
Attendee
paid enterprise — quote
?/mies.

At this scale you'd self-host Attendee on your own infra (~$300–800/mo Hetzner + ~0.3 FTE ops) which probably beats both hosted options. Worth a real proof-of-concept.

04 · gdzie wygrywają

Tam, gdzie Attendee jest lepszym wyborem.

Włączamy tę sekcję, bo alternatywa — udawanie, że wygrywamy wszędzie — jest nieuczciwa, a nieuczciwe strony porównawcze to powód, dla którego większość z nich nie warta jest czytania.

  • 01Mature Docker-compose self-host today. Their stack is genuinely simple to spin up; ours isn't yet.
  • 02Generous hosted free tier for prototyping with no sales conversation needed.
  • 03Sharper customer dashboard than ours today (we'll close that gap, but not by tomorrow).
  • 04OAuth-managed signed-in bots (for bypassing Zoom lobbies on free Zoom plans) are shipped today; ours land in M3.
  • 05Smaller, sharper API surface — they cover less, but what they cover is well-designed.

05 · gdzie wygrywamy

Gdzie meetbot wygrywa.

Każda linia linkuje do strony docs, która to potwierdza. Liczby, nie przymiotniki. Źródłowane wobec publicznej powierzchni Attendee na datę poniżej.

  • 01Broader platform surface today. Attendee covers Meet + Zoom; meetbot covers eight API surfaces: Meet, Teams, Zoom Web, Zoom SDK, Webex, Whereby, Jitsi, and Discord.
    dowód: github.com/meetbot
  • 02Microsoft Teams support today. Attendee's Teams adapter is on their roadmap. If your customer base includes any enterprise IT, Teams is non-negotiable.
    dowód: /docs/teams
  • 03Customer-visible webhook delivery logs and helper SDKs; RTMP remains a meetbot roadmap item.
    dowód: /docs/transports
  • 04Published usage pricing — $0.30/hr entry rate on the bot-hour, automatic volume tiers, no sales conversation. Their paid tiers are not public.
    dowód: /pricing
  • 05EU-hosted by default. Bot containers + control plane in Hetzner Falkenstein (DPA available on request as a template; no published certifications yet).
    dowód: /security

06 · migracja

Cała zmiana. Osiem linii.

Ten sam kształt, te same pola, inny host. Zamień swoje wywołanie dispatch bota Attendee na meetbot. Payloady webhook lądują w tym samym kształcie JSON, który twój handler już parsuje.

Attendee (przedtem)ts
// Attendee
const res = await fetch("https://app.attendee.dev/api/v1/bots", {
  method: "POST",
  headers: {
    Authorization: `Token ${process.env.ATTENDEE_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    meeting_url: "https://meet.google.com/abc-defg-hij",
    bot_name: "notes",
    transcription_settings: { provider: "deepgram" },
    webhook_url: WEBHOOK_URL,
  }),
});
meetbot (potem)ts
// meetbot — transcription is BYOK today (hosted Whisper Q3 2026)
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: "notes",
    // per-speaker audio in your bucket; pipe to your provider
    webhook_url: WEBHOOK_URL,
  }),
});

07 · faq

Pytania, które naprawdę dostajemy.

Q.What does Elastic License 2.0 actually prevent?
ELv2 has three primary clauses: (1) you can't offer the software as a hosted / managed service to third parties, (2) you can't circumvent the license-key functionality, (3) you can't remove or alter copyright notices. (1) is the one that bites if you build a SaaS that recording is a feature of and you'd benefit from running their bot internally as your hosted layer. MIT (us) has none of these.
Q.Will Attendee ship Teams support?
It's on their public roadmap; we don't have a date. If you can wait, evaluate again when it lands. If you need it now, that's a clear pick-meetbot signal.
Q.If I'm using their hosted free tier today, should I switch?
Probably not until you outgrow it. Their free tier is fine for prototyping. Once you start needing predictable pricing for finance forecasting, or paid-tier features they haven't publicly priced, the predictability of $0.30/hr starts to matter.
Q.Is your dashboard as good as theirs?
Not yet. Their dashboard is more polished today. Ours improves through M6 with the embeddable player, transcript viewer, calendar UI, and OAuth manager. Honest answer for today: theirs.
Q.How do retention controls compare?
Both expose per-bot retention. Ours: retentionPolicy: 'zero' | 'days:N' | 'forever' — nightly purge job per policy. Theirs: similar. Material parity.
Q.What about end-user OAuth for Zoom signed-in bots?
Attendee ships this today. We ship in M3 (signed-in bots for Zoom/Meet/Teams via hosted OAuth credential management). If bypassing Zoom free-plan lobbies is a must-have today, Attendee.

Ostatnio zweryfikowano 2026-05-09 wobec Attendee, publicznych danych. Zauważyłeś błąd? Popraw na GitHubie.

Wszystkie porównaniaZaloguj się →