For teams · Company Brain
Slack, Google Workspace, your LinkedIn Page, Notion, Jira, Salesforce, HubSpot and the rest — 14 company sources — become one Company Brain on a machine you control: who knows whom, what happened, where it lives. Answers come with receipts.
Done-for-you onboarding is in early access · or build it yourself with the free desktop app
Who knows this
Every account, channel, deal and document links to the people behind it — across every tool, matched by name. Ask in plain English; Studio suggests the questions this brain can answer:
Sell from the same brain. The Sales Agentv0.2.0 · developer preview reads these accounts — deals that stalled in the CRM export, the people who already know the buyer — and works them every weekday on its line in Runtime: new leads, a strategy per account, the buying team, sequences sent from your own mailbox through a send guard, the first real send always asked, a dated Sell today note and a weekly review. The Fundraising Agentv0.4.0 · preview runs its daily on a company brain too — new programs and investors, applications behind the gate, never a send. Their Inbox items sit under this brain’s name beside your personal one’s. How it sells
Runtimedeveloper preview
Who is working, on which account, and which send is waiting for your yes — every step in plain words.
this computerRuntime shows the runs on the computer where Studio runs the agents; the hosted demo has none. The first real send always waits for your yes.
When people leave
What someone knows is spread across a dozen tools. Studio pulls those exports into one note per person — so who they worked with, which accounts they touched and which channels they bridged stay readable after they go.
A routine on Acme’s braindeveloper preview
A routine can rebuild the ownership map on a schedule and leave the digest in the Inbox — single points of knowledge first: the people who are the only link to an account, a channel or a project.
Planned next: a Continuity Agent that writes the handover brief when someone leaves — planned, not shipped.
Day one
No integration project and no live connector to approve. Your tools already let you download your company’s data — the law makes them — and that archive is the raw material.
Does it work for my company? If your tools can export — and almost all must, under GDPR Article 20 and similar laws — yes. Start with two or three sources; every new export joins the same brain. The 14 company sources
What it’s made of
The Ontology tab counts every kind of note the exports produced and the labelled relations between them — derived from the data, not guessed. From the Acme demo:
14 company sources
A decommissioned tool’s export still holds who did what. Drop it in; it joins the same brain.
Link a docs repository or a Google Drive folder and every file is sorted into the brain without being copied. A local scanner checks each one first: anything that looks like credentials, secrets or dense personal data stays a metadata-only stub — its content never enters the brain.
best effortText is pulled from PDFs where it can be — there is no OCR — so a scanned page stays a stub with its name and folder.
Receipts
An unchecked brain is a confident liar. This one shows its work: every answer cites the notes it stood on, every chart says what it counted, and when the exports don’t know, the answer says so.
# Brain health Nodes: 704 · edges: 1417 · cross-source edges: 74 ## Snapshot freshness (per source) Exports are snapshots — sharp on history, blind to this week. The latest record date each source actually carries: (no dated records found)
known_contacts: 0; no name is guessed to look complete.snapshot · name-onlyExports are snapshots — sharp on history, blind to this week until the next Update — and people are matched across tools by name, deliberately strictly.
How does it know two records are one person? By name. When two tools agree on a person’s name they become one note, marked Resolved — exact after normalising, and no AI decides a merge. Where the tools disagree about a field, both values are kept.
What about live data? Studio reads exports, not live connections — nothing to approve, nothing streaming out. Press Update with a newer export; hosted, scheduled sync is on the roadmap.
Where it sits
Enterprise search and company brains model the systems you run today. Second Brain Link builds the brain from the history you already exported and hands it back as files. Different input, different job: it complements them.
| Second Brain Link | Glean | Microsoft 365 Copilot | GBrain | |
|---|---|---|---|---|
| Starts from | Export archives you already own: Slack, Workspace, LinkedIn, CRM, mail headers, docs | Live connectors to workplace appschecked 10 Oct 2026 | Live organisational data via Microsoft Graphchecked 10 Oct 2026 | Notes and ongoing signal you feed itchecked 10 Oct 2026 |
| People across tools | One note per person, matched by name across exports; who supplied each field is recorded | People search over connected appschecked 10 Oct 2026 | People and documents from the Microsoft 365 tenantchecked 10 Oct 2026 | Whatever notes you writechecked 10 Oct 2026 |
| Slack, mail, LinkedIn history | Yes — who talked to whom and when (message text is never read) | Live, via connectorschecked 10 Oct 2026 | Teams and Outlook, livechecked 10 Oct 2026 | If you import itchecked 10 Oct 2026 |
| Runs | On your machine — no account, no database, no network calls in the build | Cloud servicechecked 10 Oct 2026 | Microsoft cloud, per-user licencechecked 10 Oct 2026 | Your machinechecked 10 Oct 2026 |
| What you keep | Plain Markdown + a typed graph.json — opens in Obsidian, Claude Code, Codex, GBrain | A search indexchecked 10 Oct 2026 | Answers inside Microsoft 365checked 10 Oct 2026 | A repository of noteschecked 10 Oct 2026 |
| Open source | MIT | Nochecked 10 Oct 2026 | Nochecked 10 Oct 2026 | MITchecked 10 Oct 2026 |
Compared on 10 October 2026 from each product’s public documentation and repository; every cell carries the date it was checked. Names are their owners’ trademarks; no affiliation is implied. Second Brain Link can write a GBrain repository, so the two work together. Complements, not replaces.
Inside your walls
Your company’s history already sits in a dozen vendors’ databases. Bringing it home is the end of an exposure, not a new one — and because the build makes no network calls, the security review becomes one answerable question: which of our machines is it on?
data-handling.md note; the brain builder and the agents are MIT, so your security team reads the rule rather than our word.roadmapSSO, an audit trail, private deployment and a compliance pack are on the roadmap — not shipped. We will keep saying so until they are.
# common.py — the Collector every adapter writes through def add_person(self, source, name, …, email="", phone="", …): if not name or EMAIL_RE.search(name): return # never store a "person" whose name is an email # PII only enters in full mode; otherwise coerced to "" email = (email or "").strip() if self.full else "" phone = (phone or "").strip() if self.full else "" def add_message_signal(self, source, party_name, date="", ts=""): """Records ONLY that a message exchange happened + when. Never the body.""" # company/slack.py # NOTE: m.get("text") deliberately NOT read. # company/google_workspace.py QUARANTINE = {"payroll", "salaries", "loginaudit", "passwords", …}
Enforced in source you can read. View it on GitHub
Is anything uploaded? Not to us. The build runs where you put it; chat goes only to the AI provider you choose — or nowhere, with a local model. The privacy model
Start
Two ways in. Both end with a Company Brain on infrastructure you control.
Hand us your company’s exports — Slack, Google Workspace, the CRM, the LinkedIn Page, the wiki — and get back a populated, deduplicated, privacy-clean Company Brain with its health report and data-handling note. Built locally, never on a server you don’t control; you own the result.
Tell us which exports you haveDownload Studio, add your company, drop the exports and press Build. Of the agents, the Fundraising Agentv0.4.0 · preview and the Sales Agentv0.2.0 · developer preview work on a company brain today — each with its own daily, goal and line, running beside the ones on your personal brain.
Try it
Start with Acme’s demo brain in your browser, or build your own with the free desktop app.
Second Brain Studio · Mac (Apple silicon and Intel), Windows and Linux · free · MIT
Just looking? Open Studio in your browser — two demo brains, nothing to install