Pharos is a second brain your AI agents can actually use, that you own outright, and that can connect to your collaborators' brains without anyone handing over their notes. Notes apps remember what you typed. Pharos remembers what you know, who said so, and who is allowed to use it.
You now work with AI agents, with people outside your company, and under rules about where your data may live. Every second brain on the market fails at least one of those. Pharos was designed around all three.
You paste the same background into Claude, ChatGPT and Cursor every morning. Your second brain has it all, and none of them can read it.
Every agent you run gets the same memory, with sources attached. Ask a question and the answer tells you which facts it used.
A summary a model got wrong sits next to a fact you checked, in the same font, with the same confidence.
AI output is marked as draft. When you approve it, it is signed with your key. Your agents only act on what you approved.
Your partner gets a stale copy of your page. You get a stale copy of theirs. A month later nobody knows which one is current.
Their fact appears in your brain, updates when they change it, and stops updating when they pull the permission. No shared wiki anyone has to own.
Your second brain lives in someone else's database and is read by their model. Leaving means an export that loses half of what made it useful.
Run it on our servers or on yours. Leave whenever you like, with everything, including who said what and when.
Claude Code, Codex, a custom agent or three. They forget everything between sessions. You are the context window. Pharos gives them one memory they can read, cite and add to, without being able to pass off their guesses as your facts.
Half of what you know came from a partner, and half of what they know came from you. Pharos lets facts move between firms with permission and attribution attached, so nobody has to run a shared wiki or email a spreadsheet.
Same product, on your hardware, with your keys. Start on our hosting if you like and move later; it is a restore, not a migration. Your partners' connections survive the move.
Scroll each story. The panel on the left is your Pharos brain at that moment. The people, numbers and dates are invented.
The lookout in your browser sees 41 minutes on one preprint and records it as attended. It sits in working memory marked as what it is: something you paid attention to, not something you believe yet.
Your research agent, scout, proposes three claims from the paper. Each is signed by scout and points at the section it came from. All three sit in draft. Nothing an agent writes is treated as true.
You promote the two claims the paper supports. The third you leave in draft with a note. Promotion signs with your key, and the claims move to canonical memory with their sources still attached.
Your coding agent is asked about planning horizons. It cites the two settled claims and never mentions the draft. Its answer is signed and traceable to exactly the claims it used.
At a partner studio, Mara load-tests a vendor API and signs what she found. It lives in her ledger. You cannot see it, and neither can we.
Mara's grant to you is a fact on both ledgers: read only, project Tern, until 31 December. Her claim appears in your ledger still signed by her, still pointing at her load test. It is not a copy. It is her claim, seen from your side.
The vendor upgrades. Mara measures 60 per second and settles the new figure. On your ledger the old claim is marked superseded and the new one arrives, and your batch planner reads 60 that night. Nobody emailed anybody.
The project ends and Mara revokes grant 41. What crossed stays in your history, signed and dated. Nothing further arrives, and your agents can see exactly why.
Your studio signs for work that cannot sit in anyone else's data centre. With most tools that is a migration project. Here it is a restore.
Every claim, every signature, every crossing, in the open format. Verification runs against the signers' public keys. It does not need us to say the export is good.
Your agents reconnect to the same claims. Mara's grant still holds, because it was never an account on our server. It is a fact on her ledger and on yours.
The hosted copy is retired. Hosting was custody, and custody ended. Nothing about who signed what has changed.
The category has three shapes, and none of them can share a fact with someone outside the box without copying it.
Notion, Obsidian, Roam and their cousins. One filing cabinet for one person. AI is a plug-in that reads your pages; sharing is a link to a copy.
Can't connect · AI can't tell fact from draftThe model keeps a few sentences about you inside one vendor's product. You cannot read it, move it, or share it with anyone.
Can't export · can't share · one vendorEveryone inside one database, under one owner's keys. Works until a partner from another company needs in, or someone needs out.
One owner · one exit for everyoneEvery export, share link and "sync to team" in the category today.
Pharos, by construction.
Every serious memory tool should offer these three things. Most sell them as an enterprise plan. In Pharos they come with the product.
A fact is yours because you signed it, not because it is in your account. Nobody, including us, can sign for you.
Use your own keys for Claude, OpenAI or whoever you already pay. Or run open models on your own machines.
Our hosting or your hardware, same product, same file format. Moving between them is a restore. Your partners' connections come with you.
Own it. Share it on your terms. Let your AI use it.
Get early access