How it works
Two systems. One brain.
OrbaOS is built from two parts that fit together — or stand alone. One is the place you work and govern. The other is the engine that reads your evidence and interprets it against the doctrine. Here is the whole picture, in plain terms.
The simplest way to picture it
Think of a governance review with two roles working side by side.
The platform
OrbaOS Instruments
The boardroom & the filing cabinet
Where you and your team actually work: enter data, keep history, control who sees what, and publish board-ready reports. It remembers everything.
The engine
OrbaOS IntApp
The analyst in the room
Reads the evidence, scores the coordination load, and explains what the result means against The Coordination Capital Doctrine. It thinks, answers, and forgets — it stores nothing.
What each one does
OrbaOS Instruments — the platform
The system of record people log into.
- Sign-in, organisations, roles and permissions
- Structured data entry: CCR runs, structural floor, classifications, routing
- Drift monitoring against approved baselines
- Governance reports with review & publication controls
- Full history and audit trail — every figure traceable
- Evidence data room
OrbaOS IntApp — the engine
The methodology and judgement, as a service.
- Ingests raw evidence (documents, exports, even a whole project zip)
- Runs the deterministic CCR diagnostic — no black box
- Identifies coordination-load drivers and evidence gaps
- Holds the doctrine as its “polar star”
- Interprets results: what it says, what it means, what to do next
- Stateless when used by the platform — it keeps nothing
How they work together
You stay in Instruments the whole time. When analysis or interpretation is needed, Instruments quietly asks the engine and saves the answer.
OrbaOS Instruments
You work here · data is stored here
OrbaOS IntApp
Analyses & interprets · stores nothing
Two quick calls: Analyse (evidence → figures) and Interpret (figures → doctrine reading). Everything you see and keep stays in Instruments.
- 1
You add evidence
In Instruments, you upload or paste the evidence for an assessment and click Analyse.
- 2
The engine analyses it
Instruments sends the evidence to the engine. The engine scores it in memory and returns the figures and findings — then forgets them.
- 3
Instruments saves the result
The result becomes a draft CCR run in your account, with full history and audit trail. Your data lives here.
- 4
The engine interprets it
Click Interpret on any run or report. The engine reads just the figures, grounds them in the doctrine, and streams back a board-ready reading.
How they work on their own
Neither one needs the other to be useful. You can adopt one today and add the other later.
Instruments on its own
A governance platform without the engine.
Enter your CCR figures, structural floor and classifications by hand. Instruments still gives you history, review controls, drift monitoring and board-ready reports. The engine simply isn't called.
The engine on its own
A private, local appliance.
Point the appliance at a folder or a zip of evidence and get a diagnosis, a board report and a doctrine-grounded assistant — running entirely on one machine, with no data leaving the room. Ideal for a single analyst or an air-gapped review.
Where it runs
The same software, packaged three ways — you choose based on how sensitive your data is and who needs to use it.
Cloud
For most teams
Hosted by OrbaOS · browser
Log in to a website. We run the platform, the engine and the database. Nothing to install or update.
Data in our secure cloud, isolated per organisation.
Self-hosted server
For regulated, enterprise & air-gapped
Docker bundle · your servers
Install the whole platform — app, engine and database — inside your own network as one bundle. Your team uses it in the browser; by default nothing leaves your firewall.
Data never leaves your infrastructure.
Desktop app
For a single operator
Windows / macOS app
Just the engine, as a desktop app you install on one machine. Diagnose and interpret with its own simple interface — fully offline.
Data stays on that one machine.
The desktop app is a single‑operator appliance you double‑click. The self‑hosted server is the full multi‑user platform your whole team logs into — same brain, different reach.
How you get set up
OrbaOS is delivered and maintained by Rondanini Publishing, publisher of The Coordination Capital Doctrine, under the OrbaOS™ imprint. Whichever edition you choose, the path from order to your first board-ready run is short.
- 1
Choose your edition
A cloud plan, an annual licence, or the local edition — self-serve for cloud, a short call for on-premise and air-gapped.
- 2
We provision it
Cloud accounts are ready the same day. For on-prem or air-gapped, we package the platform and engine to run inside your environment.
- 3
Onboarding & calibration
We set your doctrine baseline, roles and report templates so your first CCR run lands board-ready — not a blank slate.
- 4
Support & doctrine updates
Methodology improvements flow to every edition as the doctrine evolves. Support and review cadence follow your plan.
Included when you subscribe
- Doctrine-aligned configuration of scores, thresholds and structural floor
- Your organisation’s branding on published board reports
- Deployment in the model you choose — cloud, on-premise or air-gapped
- Methodology and engine updates as the doctrine is revised
- Named support and a review cadence matched to your plan
- A hardcover of the doctrine with every paid plan (founder offer)
Deeper customisation — bespoke report layouts, custom integrations or private doctrine extensions — comes with annual licences and enterprise plans. Talk to us →
Why it's built this way
One methodology, maintained once
The doctrine and the scoring live in a single engine. Improve it once and every customer — cloud, on-prem or local — gets smarter at the same time.
Your data stays where it belongs
The engine computes and forgets. Storage, access and audit all sit in the platform you control.
Deploy it anywhere
The only thing that changes between cloud and on-prem is where the engine lives. The product doesn't fork.
Buy what you need
Start with a local diagnostic, the full platform, or a private appliance — and grow into the others without rework.
See it on your own evidence
Run a diagnostic, then ask the engine to interpret it against the doctrine — in plain, board-ready language.