Your data has the answers.
Your systems keep them apart.
Most institutions can't answer basic operational questions about themselves — not for lack of data, but because it lives in systems that were never built to speak. Every report is a reconstruction. Every decision waits on someone who remembers where things are.
One system. Three layers.
Raw signal enters at the bottom and ascends — resolved into a living graph, made operational by the platform, reasoned over and acted upon at the top. Not four products. One stack.
Run the organization
from one place.
Obsidian Core is the operating system for your institution — the ontology made operational. One platform that consolidates the work, connects the tools you already run, and grows new capability on top.
Built on the map, not beside it
Every module reads and writes the same ontology. Add a capability and it inherits every relationship already modelled — no re-integration, no parallel truth.
Meets your systems where they are
Connectors to the ERP, the legacy database, the spreadsheets and the archives. Obsidian unifies them into one operating picture instead of replacing them overnight.
New functions, not new vendors
Stand up new apps and workflows on the platform as needs emerge. Forward-deployed engineers build them with you, against your reality.
Decisions on evidence, not instinct
Live operational state, traced to its source. The questions you could not answer yesterday become a query — and the answer carries its provenance.
Already operational
in the work of assurance.
Obsidian is infrastructure for institutions — not a vertical tool with a platform story bolted on. One place that infrastructure already runs is professional assurance: engagements, evidence, and sign-off as objects on O2, operated through Core, assisted by Cortex.
Assurance on the ontology.
Not a fourth product. A deployment of the stack for firms and teams that run regulated assurance work — the same graph language as government and enterprise operations, specialised to the engagement lifecycle.
The work unit — scoped, staffed, and governed as an object in the graph.
Source material linked to procedures and findings, with provenance attached.
The record of work performed — signed, versioned, and audit-ready by construction.
Exceptions and conclusions that write back into the same model, not a side spreadsheet.
The product login lives on firm subdomains. The company brand remains the platform. Audit is how we prove the stack under real governance pressure — and how assurance organisations put it to work.
Built for institutions
that can't afford failure.
The organizations we serve operate where software failure has consequences beyond inconvenience. Obsidian is engineered to that standard — and deployed by people who stay.
Your data stays under your jurisdiction and your control. Residency and access governed to the standard your mandate requires.
Cloud, on-premise, or air-gapped — deployed to the security posture of the environment, not ours.
Architecture reviewed against institutional requirements. Access, encryption and isolation enforced end to end.
Every action leaves a trail that satisfies the most demanding examination. Provenance is the default, not a feature.
Engineered for mission-critical operation, where downtime has consequences beyond inconvenience.
We don't ship software and leave. Forward-deployed engineers build the platform into your reality and stay to make it land.
Bring the answers
your data already holds.
We work with institutions navigating genuine complexity — not organizations shopping for commodity software. If conventional approaches haven't solved it, we should talk.