Both products keep the same shared memory across every AI tool you use. Core is the cross-platform daemon that lives quietly in your editor and chat tools. Studio is the Mac app that also sits in your meetings, catches the commitments you'd lose, and follows up on them for you.
Background MCP server. Ingests your AI sessions and git activity, serves them back to any tool.
Everything in Core, plus on-device meeting capture, deadline nudges, the NeuraVault graph, and BYOK.
Same vault, same MCP layer, same recall in every tool. The difference is how much of Becki runs on your machine, and whether it's in the room with you.
One memory across your editor and chat tools. No app, no meetings, no fuss.
Becki in the room, capturing what was decided and chasing what's still owed.
↳ everything in Core · plus the parts that only work on your machine
Open Tweaks to switch this section between a split comparison and an upgrade spectrum.
Ingest, distill, recall. Both products run the full loop across your tools. Studio adds the surfaces that only exist when Becki lives on your Mac.
AI-tool sessions, git activity, and anything you write to the vault flow in automatically. No copy-paste.
Becki extracts decisions, commitments, dead-ends and open-loops, structured, not a wall of transcript.
Any MCP client asks Becki for context instead of you re-explaining. Same recall, every tool, in milliseconds.
Auto-starts on a calendar meeting or from the menu bar. On-device transcription. Raw audio never leaves your Mac.
Studio tracks the commitments you made and the asks you're owed, then nudges you before a deadline, or when someone still owes you a reply.
Move through everything Becki holds in the NeuraVault 3D graph, and bring your own Anthropic, OpenAI or Google key so the AI spend lands on a bill you already pay.
Studio gives Becki a native Mac home: Commitments, Meetings, Asks and Dependencies, and Ask Becki, all over the same vault Core serves to your tools.
The durable bits Becki pulled from your meetings: what you committed, what you're owed, which project it belongs to.
The daemon in the terminal panel is Core's job. Studio just gives it a window. Your tools see the same answers.
Meetings transcribe on your Mac. Raw audio and voiceprints never leave the device.
No app, no window, no meetings. Core is a small MCP server that runs in the background on any OS, harvests your AI sessions and git activity, and answers your tools when they ask.
Everything Core does, Studio does too. The rows below are the parts that only show up when Becki runs on your Mac.
| Core$15/mo · win·mac·linux | Studio$25/mo · mac only | |
|---|---|---|
| Shared memory across every AI toolrecalled on demand over MCP | Yes | Yes |
| Platforms | Win · Mac · Linux | macOS 14.4+ |
| Unlimited projects, vault items and queries | Yes | Yes |
| AI session bootstrap and git sweeper | Yes | Yes |
| Native app UI | web dashboard | Full Mac app |
| Meeting captureon-device transcription and diarisation | · | Yes |
| Proactive deadline nudges and daily briefing | · | Yes |
| NeuraVault 3D graph | · | Yes |
| Bring your own AI keyAnthropic, OpenAI, Google | backend incl. | Yes |
| Support | Standard | Priority |
Everything in Studio, shared across the team. One NeuraVault everyone reads from.
Hierarchical memory and compliance · individual → team → org, in your own region.
The short version: Core if you live in your editor and chat tools, Studio if you also want Becki in the room.
Pick Core to give your tools one memory. Pick Studio to put Becki in the room. Either way, what you teach one, the others remember.