I considered the usual tools for meeting notes and transcription, like Granola, Otter, Fathom, and other AI meeting assistants.
They are useful, but for my work the main issue was always the same: most of them are cloud-based, often join meetings as a bot, and I don’t always want client conversations, discovery calls, and sensitive sales notes to live somewhere outside my control.
As an Account Executive and Business Development Manager, I spend a lot of time talking to clients. For me, the call itself matters a lot. I don’t want to be distracted by manual notes, but I also don’t want to lose control over the transcript.
That’s why Daisy felt different.
Hi everyone,
Daisy started as an internal tool. I do a lot of client interviews and discovery calls — design strategy work where the texture of what someone says matters as much as the substance — and for years my options were two:
1. Send the audio to Granola / Otter / Fathom / Shadow. Get fast summaries, lose control of where the transcript lives.
2. Type notes by hand and miss half the conversation.
I tried every cloud meeting tool. They're great products, but they all require a vendor relationship I didn't want for client conversations. The transcript sits on a server I don't own. Every new feature adds a subprocessor to their list. And the moment I asked "where exactly does my Acme client meeting live?", the answer was always "on our infrastructure, encrypted at rest, you can trust us."
I'd rather not have to trust anyone.
So I built Daisy. It records on the Mac — microphone plus the other side of the call captured through ScreenCaptureKit, no bot in the meeting. Whisper Large v3 transcribes on the Neural Engine. For summaries, you bring your own AI provider key — Anthropic, OpenAI, Apple Intelligence on macOS 26, or a local model via Ollama or LM Studio — and the key stays in your Keychain, with requests going straight from your Mac to the provider, never through our servers. The transcript lands in your folder of choice (mine is an Obsidian vault).
The structural thing competitors can't ship: Daisy exposes a local MCP server on 127.0.0.1. Claude Desktop and Cursor can query your transcripts directly — "summarise everything I discussed with Acme this quarter" — and Daisy answers from your own disk. No copy-paste, no upload, no API token sitting in someone else's database.
It's open source on GitHub under Apache 2.0 — OSI-approved, no commercial carve-outs. Built native on macOS, signed and notarised, with Sparkle auto-updates. Free during beta, no account, no subscription gate, no telemetry.
I'd love to hear:
— What's your current meeting-capture stack, and what would have to change for you to try Daisy?
— For developers: what's the ideal local-MCP query you'd want to run?
— For privacy-aware folks: any missing assurance you'd like me to address?
I read every comment. Thanks for taking a look.
— Egor (Addicted Studio)