Oanax started with a simple frustration from the practice of regulated work: the work was done well, and yet it took weeks to prove it. Not because the evidence did not exist — but because it lived everywhere and nowhere.
In every organisation we saw from the inside, two worlds existed. In one world, people worked: technicians, nurses, operators who knew their craft and proved it every day. In the other world, people administered: spreadsheets of initials, binders of signed forms, mailboxes full of 'please confirm'.
Those two worlds did not know each other. The training was done, but the evidence was missing. The procedure was revised, but nobody knew who was still following the old version. And every audit opened with the same sentence: 'could you just show that…'
We decided the gap itself was the problem. Not the people, not the auditor, not the quality system — but the fact that doing and proving were two separate systems. So we built one.
People learn their craft on the floor, not in a classroom. Software should follow that learning where it happens — in steps, with a mentor looking on, with craftsmanship made visible.
Every minute a craftsman spends administering his work is a minute the work did not get. When the system is set up right, the evidence writes itself.
No invented figures, no features promising more than they do, no AI taking decisions that belong to people. What is off stays out of sight, and what we cannot do we say out loud.
Oanax is built by a small team you can simply reach. Ask a question and you will hear back from someone who makes the system.

Founder
Every organisation needs a brain - and in our case we have a Brian.

Head development
Aptly nicknamed Snelle Jelle for his quick delivery of optimal code.

Business developer
Remko is to our business plans what coffee is to the rest of our organization: pretty important.

Creative director
Still doesn’t understand what UX design really is, but is too afraid to admit it.