Meeting BaaS License & Open Source Policy
Meeting BaaS is the open source platform and developer API for programmatic access to meeting data across Zoom, Google Meet, and Microsoft Teams.
Our mission is to empower technical and non-technical teams to build AI meeting assistants, automate workflows, and access meeting intelligence with no vendor lock-in.
Our API is available as a hosted service, with the option to self-host when you're ready.
Open Ecosystem: MIT for All, BSL for the Core
All our ecosystem projects—like REALTIME TRANSCRIPTION, Speaking bots, Transcript Seeker, and more—are MIT licensed. Use, remix, and deploy them freely. Only the core meeting bot engine/server is covered by the BSL (see below).
- transcript-seeker: Browser-based transcript viewer and manager.
- speaking-meeting-bot: Autonomous speaking bots using the MeetingBaas API.
- realtime-meeting-transcription: Real-time transcription for meetings.
- meeting-mcp: Model Context Protocol server for AI assistants.
- ai-chat: Hackable Next.js AI chatbot (Vercel fork).
- sdk-generator: TypeScript SDK generator for MeetingBaas API.
All of the above, and more, are MIT licensed. Use them in your own projects, commercial or not.
Business Source License (BSL): What & Why
The BSL applies only to our core meeting bot engine and main server. Everything else is MIT. BSL lets you self-host, audit, and extend the core, but not resell it as a service. After a short delay, all code changes are released under an open source license.
No talk to sales. No vendor lock-in. Just code, APIs, and freedom for builders.
- Feature delay: New features in the closed-source version are released under BSL after a 1-week delay.
- Open source transition: After 18 months, the code automatically converts to Apache 2.0.
View on GitHubBusiness Source License 1.1 Licensor: SAS SPOKE Licensed Work: Meeting BaaS (https://meetingbaas.com) Change Date: 1 year from the date of each code release Change License: Apache 2.0 Use Limitation: The Licensed Work may only be used for non-commercial purposes, or for your own internal business operations. You may not use the Licensed Work, or any part of it, to provide a commercial service or product to third parties, including as a hosted or SaaS offering, without explicit written permission from the Licensor. Feature Delay: Any new features or changes in the closed-source version will be released under this license after a 1-week delay. On or after the Change Date, this license will automatically convert to the Apache 2.0 License, and you may use the Licensed Work for any purpose, including commercial use.
Leverage Our Code
Fork, clone, or remix any of our MIT-licensed projects. Build your own meeting intelligence stack, automate workflows, or create new AI meeting assistants—no vendor lock-in, ever.
If you use Meeting BaaS in your internal tools, research, or non-commercial product, please include a link to meetingbaas.com in your documentation or about page. Attribution is appreciated and helps support the open source ecosystem.
Note: Commercial hosting or resale of Meeting BaaS as a service is not permitted under this license. If you are an NGO, non-profit, or have a special use case, we offer reduced or free usage—please contact us to discuss your needs.
Internal Use by Large Organizations: Internal use of Meeting BaaS by organizations with more than 100 employees or over $5M annual revenue requires a paid commercial license. Please contact us to discuss terms.