MeetOnTrack
vs tl;dv
tl;dv combines recording, a shared meeting library and team workflows, and now offers bot-free desktop capture too. MeetOnTrack is a different fit when local media, open-source control and inspecting local working documents matter more than a managed collaboration suite.
Choose MeetOnTrack if...
You want to inspect or adapt the application and retain the meeting files under your own local storage policy. Your assistant needs to check specific repository documents or code history while you talk.
Choose tl;dv if...
You want a vendor-managed meeting library, cross-meeting questions and sales or team workflows. You prefer shared cloud access and integrations to operating a local technical beta.
Compare the same criteria
Open source comes first. Read the caveats as carefully as the capabilities.
| Criterion | MeetOnTrack public beta | tl;dv |
|---|---|---|
| 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. Integration/API access should not be confused with rights to modify and redistribute the product. |
| Bot or device capture | Captures microphone and system audio on the computer. No meeting bot needs to join the call. | Bot recording and a bot-free desktop path are available. Older comparisons that describe tl;dv as bot-only are incomplete. |
| Platforms and installation | Separate Mac and Windows technical betas. Mac: Apple Silicon, macOS 15+. Windows: x64, Windows 11 24H2+. Requirements and package features differ. | Desktop downloads for Mac and Windows and a Chrome extension. Native-mobile-app availability is not established here; vendor pages differ on mobile options. |
| 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. | Managed cloud processing and storage. Its security page describes European hosting, not an on-device-only transcription product. |
| 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. | A managed recording library. Retained media and speaker names differ between bot and audio-only capture. Retention and export permissions depend on 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. | Meeting-library search, cross-meeting AI and connected team tools. Local Git checkout/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. | Meeting capture and timestamped notes are documented. Repository-grounded live statement checking is not verified by these sources. |
| 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. | Multilingual transcription and automatic mid-call switching are described. The vendor places multi-language meetings and premium transcription on Business in its current guide. |
| Who said what | Speaker separation where available, with attribution that needs review. No independently verified speaker-accuracy score is claimed here. | Bot capture provides speaker-labelled transcripts. Audio-only recordings can show numbered speakers unless linked to calendar context. Verify the selected mode. |
| 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. | Sharing, clips, collaboration and workflow integrations. Its guide notes transcript export-format limitations, so verify the format you actually need. |
| 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. | Free entry plan and paid tiers. AI, exports, retention and fair-use allowances need checking alongside the advertised recording allowance. |
| 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 collaboration and sales workflows. A better fit when the shared workspace matters more than maintaining local application source. |
A free recording plan is not unlimited everything
tl;dv offers a free entry point, but its own materials describe plan-dependent AI features, exports and retention, plus fair-use limits. Compare the exact plan and capture mode. Bot recordings and audio-only desktop capture do not necessarily provide the same media or speaker names.
Try this before switching
Try a conversation that switches languages and confirm that the chosen plan supports that workflow. Inspect the export formats and video-retention period before adopting it as a long-term archive. Compare named attribution in bot and audio-only recordings.
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.
- MeetOnTrack MIT licence
- Public product source and documented workflow
- Mac v0.1.9 release scope
- Windows v0.1.4 release scope
- tl;dv service terms and fair-use limits
- tl;dv product and bot-free capture
- tl;dv vendor guide: capture, languages and export limits
- tl;dv desktop downloads
- tl;dv hosting and storage
- tl;dv current plans