# What our first licence says

18 November 2025 · News · 3 min read

By [Ahsan Fazal](https://axiomatic.digital/en/about#ahsan), Founder and CEO

On 18 November 2025 the first care organisation signed its licence for Inora. Not one line in it counts hours. It does say where Inora stops, that the organisation’s knowledge stays its own, and that this knowledge never improves Inora for another customer.

Our first care organisation has worked with Inora since 4 September, and its licence runs from that day. As of today, what we promise each other is on paper. I read the text once more this afternoon. Not for the amounts, which stay between us and the organisation, but for what it says and what it leaves out.

## No line that counts hours

No hourly rate for the implementation, no bundle of support hours, no item for project management.

That is not a detail. A supplier paid by the hour earns more when a team needs more help. A difficult implementation then pays better than a good one. In the end everyone does what they are paid for, so we choose what we are paid for: not our time.

There are hours in it, but they are ours. If Inora is down, the organisation can report it day and night. During office hours we respond within an hour, and we resolve 95% of outages within four hours. Those are the only hours we are held to.

## Where Inora stops

The licence sets down in an article of its own where Inora stops: Inora is not a medical device. It makes no diagnosis, raises no alarm and calculates no dose. Where a decision about a client begins, Inora stops, and the care professional decides.

This month I had Inora’s position under the EU AI Act and the Medical Device Regulation reviewed by an outside adviser. So why put the line in a contract as well? A line that lives only in the software can move with the next version. A line in the licence moves only when both parties sign again.

## The knowledge stays the organisation’s

Every protocol, guideline and handbook the organisation puts into Inora stays its property. And what it puts in makes Inora better for that organisation, never for another customer. The licence says it in the language of contracts, which in English reads: “The licensor does not use this information and data of the licensee to optimise the functioning of the software for the benefit of other licensees.”

That has a price. A system that learns from all its customers at once gets better faster. We pay that price. A care organisation must be able to hand us its quality handbook without wondering where it ends up tomorrow.

## The template for every one after it

No hours. The line on paper. The knowledge stays with the organisation that wrote it. And what an organisation puts in never makes Inora better for anyone else.

This is our first licence. Every one after it starts from this text.

## Postscript, 2 November 2026

Inora is not a medical device. Inora supports triage: the professional triages, scores and decides. Inora puts the organisation’s own protocol beside the professional, flags what is missing and records the source and version of every answer; it does not diagnose or decide on treatment. Its intended use keeps it outside the medical device rules ([The professional decides](https://axiomatic.digital/en/trust#medical-devices)).

## Do you work in care and use Inora?

Sign-in and help go through your own organisation: your team’s project lead and ambassadors can help you.

## Read on

- [The gap is not the model. It is the knowledge.](https://axiomatic.digital/en/updates/the-gap-is-not-the-model.md): The knowledge care runs on lives in the protocols and in the heads of the few people in every team who quietly do the work better. A general model does not bring the two together, not even with your documents added. A knowledge system does.
- [The line lives in the code](https://axiomatic.digital/en/updates/the-line-lives-in-the-code.md): Most AI in care draws its line in a disclaimer: the user stays responsible. Our own answers of October 2025 did the same. The new architecture fixes Inora’s safety rules in its core, when it is built. Why the line belongs there, and how we count the errors at it.
- [One product, set up for each organisation](https://axiomatic.digital/en/updates/one-product-set-up-for-each-organisation.md): In July 2025 I wanted no custom implementations; by November I saw the value of implementing for each organisation. Both hold at different levels: one codebase and one knowledge model, and for each organisation its own sources, order, answer policy and formats. Every implementation makes the next one smaller.
