meetbot.dev

All comparisons · vs MeetingBaaS

meetbot vs MeetingBaaS.

MeetingBaaS is the EU competitor most often considered alongside us — same Falkenstein-region vibe, source-available bot, generous free tier. The substantive difference is pricing shape: they bundle a monthly subscription with per-bot tokens and daily caps; we bill a flat per-minute rate on the bot-hour with no plan tiers and no caps. If your usage shape matches their plan tiers exactly, they can win at very high sustained volume — we admit that on scenario 3 below.

Sign in →Skip to pricinglast verified 2026-05-09

01 · tl;dr

The short version.

Use MeetingBaaS if…

  • →Your usage exactly fits an Infinity-tier shape (sustained ~3,000 bots/day).
  • →You want a generous free tier (75 bots/day) for prototyping before you commit.
  • →You're on Gladia for transcription already and want their 0.25-token bundle deal.
  • →You like cute branding — they have it.

Use meetbot if…

  • →You want flat per-minute pricing on the bot-hour with no token math, no plan tiers, no daily caps.
  • →Your usage is bursty or hard to predict — token packs penalise that shape.
  • →You want a true MIT license on the SDK + sample apps (vs their Elastic License 2.0).
  • →You want the same EU-hosted footprint without the subscription floor.
  • →You're fine running BYOK transcription on per-speaker audio (Whisper/Deepgram/AssemblyAI on your key) until our hosted Whisper ships Q3.

02 · spec table

Side by side. No spin.

Numbers verified against the cited source on the date in the page footer. PR a correction if anything has moved.

meetbotMeetingBaaS
pricing modelflat $0.30 / hrsubscription ($0–$299/mo) + tokens ($0.35–$0.50)[1]
effective $/hr (Pro tier)$0.30~$0.50 (1 token/hr × $0.50)[2]
effective $/hr (Scale tier)$0.30~$0.44 (1 token/hr × $0.44)[3]
subscription floor—$0–$299 / mo[4]
daily bot capsnone75 / 300 / 1k / 3k by tier[5]
free tierfirst hour, no card75 bots/day on PAYG (free)[6]
transcriptionBYOK today (free pass-through on per-speaker audio); hosted Whisper-large-v3 ships Q3 2026BYOK + Gladia bundle (0.25 token/hr)[7]
self-hostM5 (source available)supported (source available)[8]
SDK license
ELv2 blocks competing hosted services. MIT does not.
MITElastic License 2.0
platformsMeet, Teams, ZoomMeet, Teams, Zoom
data residencyHetzner Falkenstein (DE)EU (France)
transportswebhook · websocket · RTMPwebhook · websocket
pricing exposedthis pagepublic, with calculator[9]
  1. [1]pricing model: meetingbaas.com/pricing
  2. [2]effective $/hr (Pro tier): meetingbaas.com/pricing
  3. [3]effective $/hr (Scale tier): meetingbaas.com/pricing
  4. [4]subscription floor: meetingbaas.com/pricing
  5. [5]daily bot caps: meetingbaas.com/pricing
  6. [6]free tier: meetingbaas.com/pricing
  7. [7]transcription: meetingbaas.com/pricing
  8. [8]self-host: github.com/Meeting-Baas/meeting-bot-as-a-service
  9. [9]pricing exposed: meetingbaas.com/pricing

03 · pricing scenarios

The math, three ways.

Three usage points: a hobbyist, a startup, and a scaled company. Formula visible per cell — copy it into a spreadsheet, plug your own numbers in.

scenario 1

Hobbyist · 10 hr / mo

10 hours of meeting recording per month.

meetbot
10 hr × $0.30 = $3.00
$3.00/mo
MeetingBaaS
PAYG free tier covers it: $0 plan + 10 tokens × $0.50 = $5.00
$5.00/mo

MeetingBaaS PAYG technically allows 75 bots/day for free, but tokens are still per-call. Realistically both providers absorb this in free tier.

scenario 2

Startup · 1,000 hr / mo

1,000 hours of meeting recording per month.

meetbot
1,000 hr × $0.30 = $300.00
$300/mo
MeetingBaaS
Pro $99/mo + 1,000 tokens × $0.50 = $599
$599/mo

Or Scale tier: $199/mo + 1,000 × $0.45 = $649 (worse here because the cap doesn't help). meetbot remains $300 either way.

scenario 3

Scale · 50,000 hr / mo

50,000 hours of meeting recording per month.

meetbot
50,000 hr × $0.30 = $15,000
$15,000/mo
MeetingBaaS
Enterprise $299/mo + 50,000 × $0.35 = $17,799
$17,799/mo

Honest note: at sustained ~30k-50k hr/mo you'd negotiate a custom MeetingBaaS deal that may beat $0.35/token. We don't yet do volume tiering — at that scale, talk to both.

04 · where they win

Where MeetingBaaS is the better choice.

We include this section because the alternative — pretending we win everywhere — is dishonest, and dishonest comparison pages are the reason most of them aren't worth reading.

  • 01Generous free tier. 75 bots/day on PAYG with no card is one of the most permissive free tiers in this space — a real win for prototypers.
  • 02Mature self-host story today. Their Docker compose stack runs locally; ours is M5 work and not yet shipped.
  • 03Gladia bundle. If you're on Gladia for transcription, the 0.25-token-with-Gladia deal can drop their effective price below ours at high volume.
  • 04Pricing calculator UI. They ship an interactive calculator on the pricing page — ours is in the M6 backlog.
  • 05Dashboard polish. Their hosted dashboard is more mature than our M0 customer dashboard. We'll catch up; they're ahead today.

05 · where we win

Where meetbot wins.

Each line links to the doc page that proves it. Numbers, not adjectives. Sourced against MeetingBaaS's public surface as of the date below.

  • 01Flat $0.30/hr on the bot-hour — no tokens, no plan tiers, no daily caps. The price doesn't depend on what your usage shape looked like last quarter.
    proof: /pricing
  • 02MIT license on the SDK + sample apps. ELv2 (theirs) prevents you from offering a competing hosted service; MIT does not. Material if you're a CRM or ATS shipping recording as a feature.
    proof: github.com/meetbot
  • 03Three transports per endpoint (webhook, WebSocket, RTMP). Their RTMP support is request-only.
    proof: /docs/transports
  • 04Per-minute granularity, billed by the second of meeting time — not by token consumed at bot dispatch.
    proof: /pricing
  • 05Same EU-jurisdiction footprint (Hetzner Falkenstein vs OVH France). EU residency by default, no Atlantic-crossing path on the bot or control plane (DPA available on request as a template; no published certifications yet).
    proof: /security

06 · migration

The whole switch. Eight lines.

Same shape, same fields, different host. Replace your MeetingBaaS bot-dispatch call with a meetbot one. Webhook payloads land in the same JSON shape your handler already parses.

MeetingBaaS (before)ts
// MeetingBaaS
const res = await fetch("https://api.meetingbaas.com/bots", {
  method: "POST",
  headers: {
    "x-meeting-baas-api-key": process.env.MBAAS_KEY!,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    meeting_url: "https://meet.google.com/abc-defg-hij",
    bot_name: "notes",
    reserved: false,
    speech_to_text: { provider: "Gladia" },
    deduplication_key: "user-42-meeting-99",
  }),
});
meetbot (after)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 lands in your bucket; pipe it into your provider
    delivery: [{ transport: "webhook", url: WEBHOOK_URL }],
    idempotency_key: "user-42-meeting-99",
  }),
});

07 · faq

The questions we actually get.

Q.Why is your token-math comparison fair?
MeetingBaaS bills 1 token per bot-hour at the raw rate ($0.35–$0.50 depending on tier), or 0.25 token if you bundle Gladia transcription. We took the middle of that range ($0.50 on Pro, $0.45 on Scale, $0.35 on Enterprise) and added the monthly plan floor for the headline scenarios. If your usage perfectly matches their plan caps and you're on Gladia, your effective rate gets closer to ~$0.25/hr bundled — that's a real edge case where they win, especially since we don't have hosted transcription yet (BYOK only today, hosted Whisper Q3).
Q.Can I really sue MeetingBaaS for self-hosting under ELv2?
You can self-host fine. ELv2 prohibits offering a competing hosted service that substantially provides their software's functionality to third parties. If you embed it in your own product and bill your own customers for that product, you're fine. If you'd resell the bot itself as a competing API — you're not. MIT (us) has none of these clauses.
Q.Are your bot tiers as stealthy as theirs?
We use the same approach: Workspace bot accounts on a rotation pool, cookie persistence, and tier escalation on retry — each retry uses a stealthier Chrome fingerprint. This is the same playbook the Meet/Teams adapter ecosystem converged on through 2025.
Q.Do you have RTMP delivery?
Yes — same three-transport model as MeetingBaaS plus RTMP available without a request. The bot container has ffmpeg already (we use it for x11grab); RTMP push is a flag on the bot create call.
Q.How do I migrate webhook handlers?
The payload shape is materially the same: a top-level event type, a bot id, a recording manifest URL, and signed with HMAC-SHA256. Switch your verification secret and the destination URL, run our compatibility test against your handler, done.
Q.What if I'm on the free MeetingBaaS PAYG tier today?
Stay there if it covers your usage. Their free tier is generous enough to cover most prototypes — there's no point switching at that scale. Come to us when usage starts costing real money.

Last verified 2026-05-09 against MeetingBaaS's public surface. Spotted an error? Fix it on GitHub.

All comparisonsSign in →