Fathom vs threadfork

Fathom and threadfork are both meeting assistants tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Fathom

Fathom sits in the crowded meeting-intelligence space alongside Gong and Otter, but positions itself as a passive capture tool rather than a coaching platform. It records video calls across Zoom, Teams, and Google Meet, then generates summaries and action items automatically—users report reclaiming roughly 38 minutes per meeting. The free tier is genuinely unlimited for one user; paid plans scale to enterprise teams with shared visibility. The main friction: exact pricing isn't listed on the homepage, forcing a sales conversation to know costs. Language support and international availability remain unclear from public-facing materials, a notable gap for global teams.

threadfork

Threadfork records and transcribes meetings entirely on your Mac, using local models that never touch a network connection. It captures mic and system audio simultaneously, so Zoom, Meet, Teams, and in-room conversations all feed the same pipeline without a bot joining the call. Summaries, extracted commitments with owners and deadlines, and semantic search across every transcript you've ever made — all processed on your hardware, including offline. The ceiling appears fast if your team isn't on Apple Silicon or isn't running macOS 14+: there is no Windows build, no browser version, and no API for piping results into other systems.

Attribute	Fathom	threadfork
Pricing	Paid	Paid
Price	$19/mo per user	$39 /month
Free trial	90 days	14 days
Open source	No	No
Has API	Yes	No
Self-hosted option	No	No
Platforms	Web	macOS 14+ (Apple Silicon)
Languages	English	—
Released	2019	—
Pros	Automatically generates summaries and action items, saving average 38 minutes per meeting Searchable transcripts and ability to query past conversations with Ask Fathom feature Works across team sizes from 1 to 1000 with shared visibility and consistent execution SOC 2 Type II, GDPR, HIPAA compliant with SSO/SCIM support Eliminates manual follow-ups and administrative overhead	Entire pipeline — transcription, entity extraction, semantic search — runs on-device with no network required, so sensitive conversations stay on hardware you control and never appear in a vendor's data pipeline. Captures both mic and system audio without joining calls as a bot, which means participants don't see a recording notice and the tool works identically for Zoom calls and in-room conversations. Commitments and decisions are extracted automatically with named owners and deadlines, so action items don't require manual review of a 45-minute transcript to surface what was actually promised. Entity timelines aggregate every mention of a person, company, or topic across all recorded meetings, so preparing for a renewal call means opening Acme and reading four months of context rather than hunting through individual notes. Semantic search with typed filters lets you query across every transcript by person, topic, or date range, so finding the exact moment a commitment was made takes seconds instead of scrubbing audio.
Cons	Specific pricing details not shown on homepage No mention of supported languages or international availability	Apple Silicon and macOS 14+ are hard requirements, not recommendations — a team member on an Intel Mac or any Windows machine cannot run the tool at all, which forces mixed teams back to a cloud notetaker immediately. No API and no export pipeline means extracted summaries, threads, and entities stay inside Threadfork's interface; teams whose workflow requires meeting data to flow into a CRM, project tracker, or shared wiki have to copy-paste manually or abandon the tool. Local model processing on-device means transcription and extraction speed is bounded by your machine's hardware — on older or less capable Apple Silicon, long recordings take noticeably longer to process than cloud-based alternatives that offload compute to their own infrastructure. The knowledge base is single-user and local: there is no shared workspace, so a sales team trying to pool meeting history across five reps faces the same wall as the Windows user — the architecture does not support it, and teams with that requirement will move to a cloud platform.

Bottom line

Only Fathom exposes a public API. Choose based on which difference matters most for your workflow.

Frequently asked questions

What is the difference between Fathom and threadfork?

Fathom is Paid, while threadfork is Paid. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Fathom better than threadfork?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.