Family Offices
Private AI for the family archive.
Decades of correspondence, legal structures, asset reports, philanthropy records, minutes, and estate files — searchable and answerable, without any of it leaving the family’s control.
The quiet problem
A family office’s knowledge lives in people, mailboxes, scanned folders, and the memory of long-serving advisers. Succession makes it fragile: the next generation inherits the documents but not the recall. Public AI tools could help — but no family should place its archive in systems it does not control. The point of a private system is continuity without exposure.
What it answers, day to day
The system reads the archive you already hold — and answers from it, with the source attached.
Structures & entities
“Why is this holding structured this way, and which deed says so?” The governing documents and the reasoning behind them, found in minutes.
Assets & mandates
The history of a property, a mandate, or a banking relationship — reconstructed across reports and correspondence, each claim cited.
Governance & minutes
What the council decided, when, and on what basis — board packs and resolutions summarised with sources, ready for the next meeting.
Philanthropy & estate
Grant histories, foundation records, and estate files answerable in the family’s own words, without re-reading the folder.
What the system does
- Answers questions across the whole archive — with citations to the underlying documents
- Finds the history of a structure, a property, a mandate, or a relationship in minutes
- Summarises board packs and prepares meeting material with sources attached
- Supports succession: institutional memory becomes a system, not a single person
- Separates access by family branch, entity, or adviser role
- Writes an audit trail the family council can inspect
Access, separation, and control
A family is not one audience. Branches, entities, and advisers see only what their role permits, and every retrieval is logged — so the principal can see who asked what, and the archive is never a single undivided pool. Access rules are written with you during the review, not assumed. When an adviser relationship ends, so does the access; the archive stays with the family.
How an engagement runs
- Confidential architecture review1–2 weeks, fixed scope We map the archive, the sensitivity classes, the right custody model, and the operating cost — on paper, before any hardware and before any ingestion.
- Proof node2–6 weeks A sanitised part of the archive runs on hardware you control. You see citations, refusals, and audit logs on your own material — then decide to stop, expand, or productionise.
- Private vault and managed operation6–16 weeks, then ongoing Warrantied hardware, hardened deployment, family and adviser roles, monitored backups, an evaluation pack, and support that keeps it dependable across the generations that will use it.
Custody posture
Family deployments are typically air-gapped or on-premises — in the family’s own building, with offline updates where warranted. Nothing is uploaded to test it: the proof node runs on sanitised material on hardware you control. If a Swiss-hosted dedicated node suits you better, that choice and its trade-offs are set out plainly before anything runs.
What we deliberately do not do
The system supports your people. It does not make investment, tax, or legal decisions, it does not act on its own, and it will decline to answer where your archive gives it no basis — visibly, in the log. Judgement stays with the family and its advisers; the system gives them faster, sourced recall to judge from.