Software and AI that holds up.

Three products for work that has to be provable — and people who build to order when none of them fits. For organisations where a mistake is expensive.

Start a conversation See the products

Aegis · Praxis · IatrosCanada · works anywhere

See it working — one problem, start to finish

Our products

Three products, each for work someone will check later.

Each one replaces a job people currently do across spreadsheets, email and a filing cabinet. They share an engine underneath, so one fix can serve all three.

Aegis

Health & safety

Everything that happens to people and places on your site, in a history you can hand to a regulator.

Each entry seals the one before it. Edit any of them and the seal no longer matches — a history that cannot be quietly edited, verifiable on the spot.

Hazards, injuries and near misses reported from a phone — photo, sticker, send, or just say it
Inspections where a failed line becomes tracked work — and a finding can close the room it condemned
Permits, chemicals, lone working, committee walks, return to work
Chemical labels and door placards printed from the record, so the paper matches the data

Designed and tested to WCAG 2.2 AA

Universities · laboratories · manufacturing · public sector

Everything Aegis does

Praxis

Regulated change

For plants where a change has to be screened, approved and provable before anyone touches anything.

Whoever raises a change can never approve it. The refusal sits under the application, so there is no override to hand out.

Changes screened against your own rules, held as versioned data
A reissued regulation is a content update, not a software release
Temporary modifications tracked until restored, and the restore checked
Every signature the record carries — who, when, what it meant, how they signed in — in plain words, re-checked one by one
You decide what a signature means. The software offers no vocabulary of its own.

Ships with no AI — by design

Nuclear · process industry · institutional governance

Everything Praxis does

Iatros

Service & support

A service desk that is honest about time.

Two clocks, on your working calendar. Except on urgent tickets, the resolution clock does not run while you are closed, and the queue is ordered by whichever commitment is closest to running late.

A missed commitment is recorded once and survives being fixed later
Customers see progress, never your internal notes or the countdown
A drafted reply lists what only a person may promise — a price, a time, “it is fixed” — before it is sent
A resolved ticket becomes an article in one step, and later replies cite it

Customers never see the countdown

Any team with service commitments to keep

Everything Iatros does

One engine behind all of it — the same permissions, the same clock and the same kind of history, whichever product the work is in.

One platform

One engine. Three products. AI only where wanted.

The forms, the workflow, who may act and the audit trail are shared. That is why the second product did not start from zero — and why the assistant can be left out entirely.

AegisPraxisIatrosAssistantShared engine

Praxis carries no assistant at all, and our answer to your security questionnaire says so in writing. Anyone forcing AI into a nuclear change process to tick a box has misunderstood the buyer.

Aegis, step by step

What “provable” looks like, step by step.

A workplace safety product we built. Watch one problem travel from the shop floor to an inspector’s question eleven months later.

01 Reported02 Logged03 Assigned04 Blocked05 Signed06 Verified

A maintenance worker, on the floor

“The guard rail on the Bay 4 platform is loose.”

He photographs it, scans the sticker on the door frame and sends it. The room, its hazards and the person responsible for it fill in by themselves.

Why it mattersThe form fills itself in from the photo while it is still uploading, so he is not standing on the platform typing. If the sticker is missing he types the area — an unclear location never stops someone reporting a hazard.AI

The record’s history1 entry

#1184Hazard reported · 1 photoMon 10:42

—waiting

—

The photo keeps the time it was taken, not the time it finished uploading.

The safety coordinator, seconds later

It arrives as a numbered job, not an email.

Categorised and on a clock — so it cannot sit unread in someone’s inbox while they are on holiday.

Why it mattersThe category arrives already suggested, and a person confirms it in one tap. The job, the alert and the history entry are then saved together or not at all. AI

The record’s history2 entries

#1184Hazard reported · 1 photoMon 10:42

#1185Logged · seriousMon 10:43

—

Each entry is sealed against the one before it, so removing or editing one later shows up the moment anyone runs the check.

The safety coordinator

She gives the fix a name and a date.

One person is assigned it, due Friday. Not “the team will look at it”.

Why it mattersThe deadline survives a restart. If everything goes down overnight, the clock is still running in the morning.

The record’s history3 entries

#1184Hazard reportedMon 10:42

#1185Logged · seriousMon 10:43

#1186Fix assigned · due FridayMon 11:15

—

Who may assign the work and who may later sign it off are two different permissions.

The same worker, Thursday

He fixes it, then tries to sign it off himself. The system says no.

Most software lets this through. That is why a second sign-off so rarely proves anything.

Why it mattersWhoever raised or worked on something cannot be the one who approves it. The rule belongs to the workflow itself, not to a setting. Nothing is saved, so there is nothing to explain later.

The record’s historyBlocked

#1184Hazard reportedMon 10:42

#1185Logged · seriousMon 10:43

#1186Fix assigned · due FridayMon 11:15

—Sign-off blocked · same personno entry

Shown here so you can see it. The real history has no such line: nothing happened.

The shift supervisor

A second person checks the work and signs.

Different person, own login. The entry records who checked the rail, and when — not just that a button was pressed.

Why it mattersThere is no override to hand out, so there is no override to explain. That is the whole point of the second sign-off.

The record’s history5 entries · closed

#1184–85Reported · loggedMon 10:43

#1186Fix assigned · due FridayMon 11:15

#1187Repair done · 1 photoThu 15:20

#1188Signed off · supervisorThu 16:05

Two separate rules do this: the owner of a job cannot approve it, and neither can anyone who already worked on it.

Eleven months later — an inspector, unannounced

“Show me the Bay 4 guard rail.”

One page. Who reported it, the photo with its real timestamp, who was responsible, when it was fixed, who signed it. Checked in front of them, in seconds.

Why it mattersThe history can be checked on demand. Change a single character and the check fails.

VerificationIntact · nothing altered

#1184Hazard reported✓

#1185Logged✓

#1186–87Assigned · repaired✓

#1188Signed by a second person✓

An inspector does not have to take anyone’s word for it.

PausePlayor choose a step to take overChoose a step to see it

We build the same way for quality, regulated change and service work. If your process has forms, steps, someone who decides and a deadline, it fits.

The day, in one list

Sorted by what is closest to going wrong.

Not by what arrived last. Whatever the work is, the thing about to be late sits at the top — and the assistant has already flagged what looks like a repeat.

Open work · everything · one site2 due today

KindJobDueState

InjuryChemical splash while decanting · left forearmDrafted from one photo and a sentence AI2h 10mFiling window

PermitHot-work permit · welding, roof plant roomToday 16:00Awaiting sign-off

InspectionMonthly walk · Block C, levels 1–3FriIn progress

HazardLoose handrail reported near Bay 4Looks like the same problem as the Bay 4 rail — link or keep separate? AIMonPossible duplicate

SDS14 safety data sheets received this weekFields drafted · 3 need a closer look AI14 Oct3 to review

Hazardous wasteWaste collection booked and documented18 OctScheduled

Injuries · near misses · inspections · permits · chemicals · hazardous waste · lone working · accommodation · committee walks · return to workone list

When something runs late, the history says so. Closing it later does not erase that it was late.

Inspections

A finding is work with someone’s name on it.

Walk the list, fail a line, and that line becomes a tracked job. Photograph the problem and the assistant writes the first draft of the finding while you keep walking. A finding severe enough to stop work can close the room, from the finding itself.

Monthly walk · Block C · 12 of 18 checked2 findings open

✓Emergency lighting tested this monthFire Code 2.7.3

✓Eyewash station clear and flushedANSI Z358.1

!Guard rail secure on raised platformsFinding drafted from your photo · owner set · due Friday AIReg. 851 s.13

✓Extinguishers sealed and in dateNFPA 10

!Chemical store ventilation runningDrafted · nobody assigned yet AIReg. 833

Ladder tags currentnot yet walked

Cannot be marked Pass while 2 findings are still openPass · Pass with findings · Fail

The clause beside each line is the rule that line exists to satisfy. The clauses are data, so a reissued regulation is an update to the list, not a release.

Before anything goes live

Fail on a Tuesday afternoon, not at 03:00.

When somebody designs a new process — who reviews, who approves, what happens if nobody acts — it gets checked before it can touch real work.

Checking “Contractor hot-work permit”2 problems · cannot go live

blocked

A step nobody can ever reach“Escalated” exists, but no route through the process arrives there.

blocked

An approval nobody is able to giveThe sign-off step has no role attached that anyone holds.

warning

A timed step with no time setAllowed — but flagged, because it will never fire on its own.

passed

Every path can finish, and finished means finishedNothing loops back out of a completed state, and no route dead-ends.

The checks run in the designer’s browser, again at publish, and again while the work runs — so a process cannot mean one thing when it is designed and another when it runs.

Warnings never block. Real problems always do.

You have already seen it working.

Every mark labelled AI in the screens above is the assistant drafting. It is built into the product, not beside it: it reads what your people already produce and turns it into finished work for a person to approve.

It drafts from a photo

Someone snaps a picture and writes — or says — one line. It comes back as a complete, correctly categorised entry with the right fields filled in, ready to check and send.

It reads documents

Safety data sheets, procedures, contracts, old binders. The assistant pulls the fields out and files them where they belong, instead of someone re-typing them for a fortnight.

It answers in plain language

“What is still open in Block C?” “Which permits expire this week?” Answers drawn from your own records, with the ones it used shown beside the answer.

It spots duplicates

The same problem reported twice by two people becomes one thread, not two half-finished ones. It offers the link; a person decides.

It says when it is unsure

On the fields that matter, a low-confidence guess is worse than none. It leaves them blank and tells you why, rather than inventing something plausible.

It never acts alone

Nothing is applied on its own, and every AI-assisted item is labelled as one on the record. That is what lets you run it somewhere an inspector will look.

One photo and “splash on my arm while decanting”ready for review

AI draft — waiting for a person

What happenedChemical splash while decanting

Where on the bodyForearm, left

What was involvedToluene, decanting

How seriousleft blank — not confident

Seriousness decides whether this escalates to a manager tonight, so the assistant will not guess it.

Confirm & create Edit firstor press ⏎

The person is the one who decides. The AI is the one that does the typing.

Services

When no product fits, we build to order.

The products cover the common ground. When the problem is yours alone, the same people build it, to the same standard.

Software, start to handover

Web and mobile products built to be handed over, documented so the next engineer does not need us. We take new builds and rescues of things that stalled.

Products · platforms · integrations · migrations

AI inside your systems

Assistants, agents and automation wired into the systems and permissions you already have — not a chat window on the side. Built so every answer shows the records it came from and who confirmed it.

Assistants · agents · document AI · automation

Work an auditor will ask to see

Where the work has to be provable — safety, quality, regulated change, anything a regulator or a customer’s auditor will one day ask to see. Records that cannot be altered after the fact, approvals that cannot be shortcut, and every route decided for every role — kept as a test.

Health & safety · quality · regulated change

Advisory

The security questionnaire you have to answer, the standards nobody reads, the AI policy your risk officer is waiting for. We do the work and leave you the documents.

Security posture · standards · AI governance

Built for universities, laboratories, manufacturing, nuclear and the public sector.

How we work

Three ways in. Start with the free one.

You should be able to judge us before you pay us.

01 · Free

Take the handbook

Our engineering handbook, written to be handed out. Use it without speaking to us. If it is useful, you already know how we think.

No call, no form

02 · Two weeks

A paid review

We read your system and your process and come back with findings you can act on, each pointing at the exact place it lives. No commitment beyond it.

Fixed fee

03 · Phases

We build it with you

Phased, with something working at the end of each phase. Your code, in your repositories — ownership terms set out in your agreement.

Fixed fee per phase

Engagements

Every engagement ends in something you keep.

Every job runs the same way and ends with something working, in your name.

Build it

Build

A product, built in phases, then yours.

AI layerAI core

An assistant wired into the systems you already run.

Rescue

A stalled codebase made shippable, with an honest read first.

Prove it

Security posture

The questionnaire your biggest customer is about to send, answered.

AI you can deployAI core

An assistant with a register your risk officer can sign.

Raise your floor

Engineering standards

“We have standards” turned into checks that fail the build.

Your rules as data

Your binder, turned into something your systems can install.

Build itProve itRaise your floorAI included — the assistant works inside the deliverableAI core — the engagement itself

Fixed fee wherever the deliverable can be named in advance. You own the source.

Let’s talk

Tell us the awkward one.

Not the tidy project — the one that has stalled twice, or the process nobody wants to touch. That is the conversation worth having, and it costs you nothing to start it.

Start a conversation Take the handbook