An animated diagram on warm paper. A drawn boundary marks the edge of your infrastructure. Inside it, scattered documents, chat messages, PDFs, images, emails, spreadsheets and voice notes drift in disorder — some duplicated, some faded and lost. As the page scrolls, they flow inward and organize into a single connected lattice: one brain. A question travels through it and returns an answer, with lines drawn from each part of the answer back to the exact source it came from. Nothing ever crosses the boundary.
On-premise knowledge infrastructure
One brain for every file, chat, image and call — deployed entirely inside your infrastructure.
The problem
It is in a thread from March. In a PDF someone renamed. In a voice note nobody transcribed. In the fourth version of a file called final.
Buried
The answer exists. It is nine tools and two departments away from the person who needs it.
Duplicated
Four versions of the same document. Three are wrong. Nothing says which.
Lost
The person who knew left in April. Their knowledge left with them.
Unsearchable
Search matches filenames, not meaning. It cannot read the image, the audio, or the scan.
The turn
CompanyMind ingests every source your company owns and organizes it into a single connected index. Duplicates merge. Formats stop mattering. What was scattered becomes one thing you can ask.
And none of it left your walls.
Trustworthy
Answers are constructed from what your data actually says. Every clause carries a citation to the artifact it came from — click it and you are looking at the source.
What did we commit to on data residency in the Meridian contract?
All customer data stays in-region with no cross-border transfer1 and the retention window was negotiated down to 18 months2 after Legal flagged the original 36-month term.3
No source, no claim. If the data does not say it, CompanyMind does not either.
- 1meridian_msa_executed.pdfSchedule 2 · §4.1 · p.14
- 2contract_terms_tracker.xlsxRow 87 · "Retention (mo)"
- 3re: Meridian redlinesLegal · 12 Mar · 09:41
Sovereign
CompanyMind runs where your data already lives — your datacenter, your VPC, or a machine with no route to the internet at all. There is no vendor cloud to trust, because there is no vendor cloud.
- Outbound
- Nothing calls home. No telemetry, no phone-home, no model API.
- Inbound
- No inbound path from us. We have no access to your deployment.
- Air-gap
- Runs fully offline. Models and index ship with the deployment.
Capability
- 01
Ingest everything
Documents, spreadsheets, PDFs, email, chat, images and audio. Scans get read. Calls get transcribed. Formats stop being a reason things go missing.
- 02
Cited answers
Every clause traces to the artifact it came from. Open the original in one click and verify it yourself. Grounded in your data — not in what a model remembers.
- 03
Permission-aware
The brain honors the access control you already have. People get answers only from what they were already cleared to see. Nothing is flattened into one index everyone can read.
- 04
Air-gap capable
Deploy on a network with no internet route. Models, index and interface all run locally. Nothing in the system requires an outbound connection.
- 05
Audit trail
Every question, every answer, every source consulted — logged in your systems, queryable by your auditors, retained on your schedule.
Proof
We are pre-launch, so these are not customer counts. They are properties of the architecture — things that are true on day one of any deployment, because they follow from how it is built.
- Data egress
- 0 bytesData egressNothing calls out. There is no outbound path to have a number greater than zero.
- Source formats
- 0Source formatsIngest adapters implemented today, from .docx to .m4a to scanned .tiff.
- Answers carrying a citation
- 0%Answers carrying a citationAnswers are assembled from retrieved spans. An uncited claim cannot be constructed.
- Deployment — yours
- 0Deployment — yoursSingle-tenant by design. No shared index, no pooled infrastructure, no neighbours.
Design partners
CompanyMind is being built with a small number of regulated teams who have this problem badly enough to help us solve it properly. If your knowledge is scattered and your data cannot leave, we should talk.