Local-first AI meeting notetaker
Nod records, transcribes, and writes the notes on your computer. There is no account, and no server that can read them. Your meetings are encrypted on your device, synced between your devices end to end, and shared only with the people you choose.
- macOS, Windows, and Linux
- iPhone and Android to follow
- Open source at launch
- No account
While you record
This is all that stays on your screen while Nod records: a small widget at the edge of the display, above your other windows. The app itself can stay hidden.
The bars move with the sound. Click the mark to open the app, or the bars to pause.
1Transcribed on your device
Both models run on your computer: the one that listens and the one that writes the notes. Audio stays in memory and is never written to disk.
2Encrypted on your device
Every meeting is one encrypted file. The key lives in your operating system's keychain, and nowhere else.
3Synced end to end
Your devices share meetings through a folder or a relay. Both only ever see encrypted files. The key is twenty-four words that you keep.
How your devices share a meeting
Your laptop
Records, transcribes, and writes the notes
Folder or relay
Holds encrypted files only. No key, nothing to read
Your other computer
Opens them with the same twenty-four words
What a relay sees
On your device
- Me: This is transcribed on my laptop. The audio isn't kept, and your name never appears.
- P07: I don't mind the app knowing. I mind not knowing who else does.
- Me: Would it matter to you where the data is stored?
On the relay
Encrypting in your browser…
Encrypt the same lines again, and you get a different file every time.
Share notes with your team
Sometimes a meeting's notes belong to more people than you. You can share a meeting with one colleague, or with a team. Either way, nobody in between can read it.
1Only the notes travel
You share a meeting's title and summary. The transcript stays on your device, so a participant's exact words never leave it.
2Encrypted for each person
You and a colleague add each other's identity card and compare a short code. A team's notes are encrypted for its members, and the relay only sees encrypted files.
3You decide who's in
Every team member has a role: owner, admin, writer, or reader. Owners and admins add and remove people. Readers can read, but not change anything.
Ask the assistant you already use
Nod runs a small MCP server on your computer. Any assistant that speaks MCP can search your meetings and read the parts you allow. That includes Claude Desktop, Qwen Chat, Kimi Code, LM Studio, and others.
1You choose what it reads
Each assistant gets its own key and reads only what you allow: notes, transcripts, or both. Names and dates are always visible. You can disconnect it at any time.
2Only from your computer
Assistants connect on localhost, and only while Nod is open. Nothing is exposed to the network. They can read, but never change anything.
3Local or cloud, your call
An assistant that runs on your computer keeps what it reads there. A cloud assistant sends it to its company. Nod tells you this before you connect.
| A typical hosted notetaker | Nod | |
|---|---|---|
| Where audio goes | Usually to the vendor's servers | Nowhere. It is never stored, not even on your disk |
| Who can read the transcript | You and the vendor | You |
| Works offline | Usually not | Yes |
| Sync between devices | Through the vendor's account | End to end encrypted, through a folder or a relay |
| Sharing with colleagues | Through the vendor, who can read it too | Encrypted for each person or team. The summary only, never the transcript |
| Works with your AI assistant | Usually only the vendor's own | Any that speaks MCP, with the parts you allow |
| Account required | Usually | No |
| Source | Usually closed | Open, Apache 2.0, at launch |