MeetOnTrack
vs Bluedot
Both tools offer bot-free capture. Bluedot focuses on a managed, shared meeting library and post-meeting workflows. MeetOnTrack emphasizes inspectable source, local recordings and checking the conversation against your local working context.
Choose MeetOnTrack if...
You want locally retained meeting files and a workflow you can modify under MIT. Your live questions depend on documents, code or Git history in repositories already on your machine.
Choose Bluedot if...
You want bot-free recording connected to a shared meeting library and downstream CRM or collaboration workflows. You prefer a vendor-managed service with workspace governance rather than running the technical beta yourself.
Compare the same criteria
Open source comes first. Read the caveats as carefully as the capabilities.
| Criterion | MeetOnTrack public beta | Bluedot |
|---|---|---|
| Open source and licence | Public application source under MIT. Inspect, modify and redistribute it subject to the licence and third-party notices. Open source does not mean every connected AI service is open source. | Commercial service terms, not a full-product open-source licence. An available API or MCP integration does not provide the application's source licence. |
| Bot or device capture | Captures microphone and system audio on the computer. No meeting bot needs to join the call. | Bot-free browser and desktop capture. No extra participant is required for its documented capture workflow. |
| Platforms and installation | Separate Mac and Windows technical betas. Mac: Apple Silicon, macOS 15+. Windows: x64, Windows 11 24H2+. Requirements and package features differ. | Chrome, Mac and Windows desktop, plus mobile options are listed by the vendor. |
| Local processing and offline use | Audio capture and speech recognition run locally. Codex analysis can send selected conversation and repository excerpts to its AI service. The published beta is not an end-to-end offline AI product. | Vendor-managed processing and AWS storage. Its no-training commitments are distinct from a promise of offline processing. |
| Can you keep the audio? | Meeting recordings and transcript files are saved in the user directory. Local disk space and your backup policy determine retention. | Recordings live in the managed library. Audio/video options, recording duration and retention controls vary by plan. |
| Context beyond the transcript | Read-only Codex search over selected local Git checkouts, documents, source and history. A repository connection is not a licence to upload everything. | Searchable shared meeting history and CRM/collaboration connections. Read-only local Git history search is not established by these sources. |
| Help during the call | Near-live transcript and questions, risks and decisions. Ask Codex to check a statement against the selected working context. | The reviewed product pages emphasize capture, summaries and post-meeting automation. A repository-grounded live assistant is not verified here. |
| Languages and switching mid-call | Local ASR capabilities depend on the engine and build. Validate your language mix, accents and mid-call switches. New multilingual fixes in source are not automatically included in the pinned beta. | Automatic language selection and many transcription languages are documented. Its help guide describes limits when changing transcript languages, so test your mixed-language workflow. |
| Who said what | Speaker separation where available, with attribution that needs review. No independently verified speaker-accuracy score is claimed here. | Speaker attribution quality for your exact device/capture path is not established by the sources used here. Verify it in a trial rather than reading this as a missing feature. |
| Exports and connections | Local HTML/PDF reports. Optional delivery to Drive, email and Telegram requires configuration. Newer source features must be checked against the installed release. | Share links, clips and downstream integrations. API/MCP and CRM features have plan-dependent availability. |
| Cost and dependencies | MIT application source. Budget separately for Codex access and any paid services you choose. This is not a promise that future hosted offerings will be free. | The Free plan lists five lifetime meetings. Paid per-user plans expand recording and workflow allowances. Check the billing period and duration limits. |
| Setup and rollout trade-off | Technical beta with prerequisites and OS permissions. The Mac package is not notarized, the Windows beta is unsigned, and automatic updates are not enabled in these pinned packages. | Managed apps and workspace controls, including enterprise governance options on eligible plans. |
Bot-free does not mean local-only
Bluedot captures through the browser or desktop without joining as a bot, while its security documentation describes AWS data storage. That is a cloud workflow with device capture. MeetOnTrack retains files locally, but configured Codex analysis can still send excerpts to an AI provider. Decide separately where capture, transcription, storage and analysis are allowed to happen.
Try this before switching
Use a call that includes your real conferencing app and language mix. Check the retained recording, the transcript after a language switch and the destination of a shared report. For long calls, check the recording-duration limit of the exact Bluedot plan you are considering.
Compare the package you can actually install
The pinned packages are Mac v0.1.9 and Windows v0.1.4. They have different requirements and limitations. The source tree can be newer than either package. Development previews on the homepage do not extend the public beta's feature scope.
Automatic multilingual recognition, model choices, update notifications and newer integrations must be checked against the exact installed build. We do not claim tested parity between operating systems, guaranteed speaker attribution, fully offline AI or enterprise compliance certification.
How this comparison was made
Published by AI Agent Labs, maker of MeetOnTrack. This is a vendor-authored comparison, not an independent accuracy benchmark. Competitor capabilities come from the linked official product, help, pricing and policy pages, checked on 2026-10-16. We did not run comparative performance tests.
We use the same criteria for every product. An undocumented feature is marked unverified, not absent. Device capture, on-device speech recognition, cloud storage and cloud AI are separate questions. A free plan, public SDK or MCP endpoint is not an open-source licence for the whole application.
Pricing links point to current plans instead of mixing annual and monthly quote amounts. Plan limits and capture modes can change. Obtain the required participant consent regardless of whether a bot appears in the meeting.
Primary sources
Official vendor documentation, not third-party rankings. These are product statements, not independent validation of performance.