MeetingBot and Yating are both AI meeting assistants for recording, transcription, and summaries, compared here on pricing, features, and workflow fit. MeetingBot: Open-source meeting bot API that sends bots into Google Meet, Microsoft Teams, and Zoom to record calls, deployable to your own AWS infrastructure. Yating: Taiwan-built AI speech-to-text app for classes, meetings, and interviews, optimized for Taiwanese-accent Mandarin and Mandarin-English code-switching. They overlap on ai-meeting-assistants, so the right pick depends on team size, budget, and which meeting workflows you automate.
For ai-meeting-assistants workflows, shortlist MeetingBot when developers building products that need automated meeting recording across google meet, teams, and zoom matters most, and Yating when students transcribing lectures and classes in mandarin or mixed mandarin-english matters most. Both record across Zoom, Google Meet, and Microsoft Teams; trial each on real meetings before committing.
Open-source meeting bot API that sends bots into Google Meet, Microsoft Teams, and Zoom to record calls, deployable to your own AWS infrastructure.
Bot deployment to Google Meet, Microsoft Teams, and ZoomInfrastructure-as-code self-hosting via Terraform on AWSREST API for managing bots and accessing recordings, transcripts, and metadata
Taiwan-built AI speech-to-text app for classes, meetings, and interviews, optimized for Taiwanese-accent Mandarin and Mandarin-English code-switching.
API access for batch processing and ASRCross-platform: mobile, web, and Chrome pluginLive microphone transcription plus transcription of recorded and uploaded files
MeetingBot is a free tier with paid upgrades (freemium); Yating is a free tier with paid upgrades (freemium). Always confirm current pricing on each vendor's site before buying.
Bot deployment to Google Meet, Microsoft Teams, and Zoom
Live microphone transcription plus transcription of recorded and uploaded files
Standout feature
REST API for managing bots and accessing recordings, transcripts, and metadata
Optimized for Taiwanese-accent Mandarin and Mandarin-English code-switching
Team usage
Visual dashboard for bot management and data viewing
Support for Mandarin, Taiwanese, English, Japanese, and Cantonese
Integrations
Infrastructure-as-code self-hosting via Terraform on AWS
Speaker identification with timestamps
Languages & capture
Scalable AWS ECS-based deployment
Subtitle mode for accessibility
Best-fit workflow
TypeScript stack with Next.js, Express, PostgreSQL, tRPC, and Drizzle ORM
Cross-platform: mobile, web, and Chrome plugin
Best for
MeetingBot
Choose MeetingBot if you need developers building products that need automated meeting recording across google meet, teams, and zoom — strengths include open source and self-hostable so meeting data stays in your own aws account.
Yating
Choose Yating if you need students transcribing lectures and classes in mandarin or mixed mandarin-english — strengths include strong handling of taiwanese-accent mandarin and chinese-english code-switching.
Pros & cons
MeetingBot
+ Open source and self-hostable so meeting data stays in your own AWS account
- Self-hosting is tied to AWS, requiring cloud and Terraform familiarity
Yating
+ Strong handling of Taiwanese-accent Mandarin and Chinese-English code-switching
+ Privacy-focused with locally developed models and a no-data-selling stance
- Language strengths are centered on Taiwan-region languages rather than broad global coverage
FAQ
Is MeetingBot or Yating better for AI meeting notes?
It depends on your workflow. MeetingBot is strong for developers building products that need automated meeting recording across google meet, teams, and zoom, while Yating is strong for students transcribing lectures and classes in mandarin or mixed mandarin-english. Both transcribe and summarize meetings.
How do MeetingBot and Yating compare on price?
MeetingBot is a free tier with paid upgrades and Yating is a free tier with paid upgrades. Check each vendor's pricing page for the latest plans and free-tier limits.
Can I use both MeetingBot and Yating?
Yes. Many teams run more than one meeting assistant when the workflows are complementary and the budget is justified.