すべての比較 · vs Recall.ai
Recall.ai はこのカテゴリ — meeting-bot-as-a-service — を作り、出荷した API のかたちは現在この市場の大部分が模倣しています。3000 社以上の顧客と増え続けています。当社は意図的に Recall の HTTP API をミラーしているため、午後一日で乗り換えられ、その上で ボット時間あたり安く 課金します。Recall のホスト型 API はクローズドソースであり、GitHub 上の公開サンプルリポジトリは LICENSE ファイルなしで公開されています (実質的に「全権利保留」)。当社の SDK + サンプルは MIT — クローン、フォーク、出荷可能です。以下: 各スペック行、3 つの利用ポイントでの計算、そして彼らがいまだに優れた選択である領域に充てた一節。
01 · 要点
Recall.ai を使うべきとき…
meetbot を使うべきとき…
02 · スペック表
ページフッターの日付に引用元に対して検証された数字。何か変わっていれば PR で訂正してください。
| meetbot | Recall.ai | ||
|---|---|---|---|
| recording price | $0.30 / hr (flat bot-hour) | $0.50 / hr[1] | |
| transcription price We do not ship transcription today. Per-speaker audio + the meeting platform's native captions are emitted; transcription is BYOK on those tracks until our hosted Whisper ships Q3. | BYOK today (free pass-through); hosted Whisper +$0.10/hr at GA (Q3 2026) | +$0.15 / hr[2] | |
| storage price | $0 (we don't host recordings; they upload directly to your S3) | +$0.05 / hr / 30 d[3] | |
| bundled $/hr (today) Apples-to-apples: 1 hr recorded + transcribed + stored 30 days. Today the BYOK path on per-speaker audio is free of meetbot fees but you pay your provider directly. At GA (hosted Whisper, Q3 2026) the bundled rate becomes $0.40/hr us vs $0.65/hr them. | $0.30 bot-hour + your own transcription bill (BYOK) | $0.65 | |
| billing granularity | per minute | per minute (rounded) | |
| free tier | first hour, no card | 5 hr / mo[4] | |
| SDK license Recall's hosted API is closed-source. Their public sample repos on github.com/recallai ship without a LICENSE file (effectively all-rights-reserved by default copyright). Ours are MIT. | MIT SDK + samples; proprietary hosted backend | proprietary API + unlicensed sample repos | |
| self-hostable | planned (M5, source available); not committed | no | |
| platforms | Meet, Teams, Zoom (Webex + Discord M2) | Meet, Teams, Zoom, Webex, Slack Huddles, GoTo | |
| data residency | eu-central (Falkenstein) only | US, EU, JP[5] | |
| compliance certifications | none today (SOC 2 Type 1 on M5 roadmap; no BAA template; no published uptime SLA) | SOC 2, ISO 27001, HIPAA BAA[6] | |
| SLA | no published SLA (will publish once status.meetbot.dev has real history) | 99.9% SLA on enterprise tier | |
| transports | webhook, websocket, RTMP | webhook, websocket, RTMP | |
| mobile SDK Recall has a mobile SDK in market. We do not. Our embedded SDK lands Q3 2026 — ambient mic capture only (Apple/Google block VoIP audio capture from other apps). | shipping Q3 2026 (iOS first) | shipping today[7] | |
| customers (public) | pre-launch (zero paying customers today) | 3,000+ |
03 · 価格シナリオ
3つの利用ポイント: ホビイスト、スタートアップ、スケールした企業。セルごとに数式が見えます — スプレッドシートにコピーして、自分の数字を入れてください。
月あたり 10 時間の会議録画。
Today: meetbot only bills the bot-hour; transcription (if you want it) is BYOK — pipe per-speaker audio into Whisper/Deepgram/AssemblyAI on your own key. Both providers' free tiers absorb most of this. Recall's 5-hr free tier means real cost ~$3.25; meetbot's first-hour-free means ~$2.70 plus whatever your provider charges for ~10 hrs of audio.
月あたり 1,000 時間の会議録画。
$350/mo of saved bot-hour spend at this scale — minus whatever your transcription provider charges. Whisper-large-v3 self-hosted on a Hetzner GPU box (~$200/mo for an RTX 4090) handles ~20 concurrent realtime streams; Deepgram pay-go is around $0.0043/min ≈ $0.26/hr. Real bundled cost on meetbot today: roughly $300 + $200–260 = $500–560/mo. At GA (hosted Whisper Q3 2026): $400/mo flat.
月あたり 50,000 時間の会議録画。
At this scale you self-host Whisper-large-v3 on dedicated GPU infra (a couple of $200–400/mo Hetzner GPU boxes serve thousands of concurrent streams) and the transcription leg approaches its hardware floor. Recall negotiates volume discounts at this scale. We don't yet, but our list price on the bot-hour is already below their post-negotiation floor we've seen quoted.
04 · 競合が優位なところ
このセクションを含めるのは、その代替 — どこでも我々が勝つふり — が不誠実だからで、不誠実な比較ページがほとんど読む価値がない理由です。
05 · 当社が優位なところ
各行はそれを証明する docs ページにリンクします。形容詞ではなく数字。下記日付時点の Recall.ai の公開情報に対して取得。
06 · 移行
同じ形、同じフィールド、別のホスト。 Recall.ai の bot ディスパッチ呼び出しを meetbot のものに置き換えてください。webhook ペイロードはハンドラーが既にパースしている同じ JSON 形で届きます。
// Recall.ai
const res = await fetch("https://us-west-2.recall.ai/api/v1/bot", {
method: "POST",
headers: {
Authorization: `Token ${process.env.RECALL_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
meeting_url: "https://meet.google.com/abc-defg-hij",
bot_name: "notes",
transcription_options: { provider: "deepgram" },
real_time_transcription: { destination_url: WEBHOOK_URL },
}),
});// meetbot — same shape, different host.
// Note: we don't ship transcription today — per-speaker audio
// lands in your bucket; pipe it into your provider of choice.
// Hosted Whisper option lands 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",
// captions: passthrough of platform-native captions (Meet/Teams/Zoom)
delivery: [{ transport: "webhook", url: WEBHOOK_URL }],
}),
});07 · FAQ
最終確認 2026-05-09 対象: Recall.aiの公開情報。 誤りを見つけましたか? GitHub で修正.