The Cockpit · The software
Enterprise AI cockpit: run and prove every AI system you use
Available
The Cockpit is 56North's software: the registry of every AI system in the company, a score from 0 to 100 on five dials, a sealed monthly flight report and dated evidence, whatever the vendors.
What the Cockpit does
A company now runs the AI in its CRM, the one in its office suite, the one in its ERP and the one in its ticketing tool. Each vendor shows its own dashboard. None shows the whole picture.
The Cockpit sits above them, on the company's side. It brings together in one place:
- the registry of your AI systems, each with its purpose and a named owner;
- their risk class under the EU AI Act, kept over time;
- the timeline of the regulation's stages that apply to you;
- evidence attached to the articles of the AI Act, with a log of who did what;
- the airworthiness score and the monthly flight report.
Five dials, one score from 0 to 100
A published, versioned methodology, identical for every client. Each score carries the version of the method that produced it and the scope it covers.
| Dial | What it measures |
|---|---|
| Reliability | The quality of the answers, assessed on your real conversations. |
| Costs | The cost per case handled, and its trend. |
| AI Act evidence | The registry, the evidence, the deadlines that apply. |
| Usage | Who actually uses each AI system. |
| Reference sources | How fresh the knowledge your AI systems rely on is. |
A score from 0 to 100, a grade from A to E, a 30-day trend. What can be measured is measured automatically; what rests on a declaration is flagged as such. The scope always comes with the score: a score calculated on four AI systems out of six says so.
The monthly flight report
Every month, the flight report is frozen when published and sealed with a fingerprint that shows it has not been altered since. A third party can check that fingerprint. It is a content fingerprint, not an electronic signature.
An executive committee reads the report in two minutes: the score, its trend, the gaps, the missing evidence.
Dated evidence, with its author
A dashboard shows the state of today. Evidence shows what was true on a given date and who established it. In the Cockpit, every piece of evidence carries a recording date and its author, and is attached to the article of the regulation it documents. The AI Act compliance page sets out which evidence to build.
Up and running in three steps
- Declare. A few questions per AI system, and the registry fills itself.
- Connect. One address and one key to change in the software.
- Measure. The dials light up with the first calls.
AI built into a software suite, which cannot be connected, still enters the registry: it is classified and receives its evidence.
Two deployment modes
- SaaS, hosted by 56North: a dedicated instance, quick start, updates included.
- On-premise, installed at your site: for regulated sectors, installation led by our team.
The same scoring method in both cases. One instance and one database per client, never shared. User identities are pseudonymised on arrival, irreversibly.
What the Cockpit does not do alone
Software alone proves nothing. Two offers complement it and can be bought separately: Human in the Loop, to have your AI tested by people, and the Factory, to connect and maintain the systems you already run.
Do you know which AI systems run in your company, and who answers for them?
Request an assessmentA free 30-minute first conversation, no commitment.
Frequently asked questions
Does the Cockpit replace the vendors' governance tools?
No. Native tools remain necessary: they govern each AI from the inside. The Cockpit sits above them, on the company's side, and consolidates what they produce into one registry, one score, one evidence file.
What about the AI built into our software suite, which we cannot connect?
It enters the registry, is classified and receives its evidence. The regulation asks you to govern it, not necessarily to measure it. The score always states the scope it covers.
Can we install the Cockpit ourselves?
Yes. As SaaS, on a dedicated instance, or on-premise, in your own infrastructure. The method and the score are strictly identical.
Updated 12 October 2026