Most of the work
If it repeats, automate it.
An LLM builds the automation quickly. Once it is built, it runs without one.
Secure Innovation
Secure Innovation Governed AI for regulated work
Radmis is built to get it through. AI runs as a permissioned user, on your premises or your cloud. Every action has an owner, an approval and a trail your auditor verifies without us.
In two weeks your risk owner has a go, fix or stop answer, with the evidence behind it. Defined outcomes at a fixed price. Stop after any stage.
Built for organisations including NSW Health · NSW Department of Education · NSW Telco Authority · Optus
What the risk review asks
Most pilots stall because nobody can answer them with a record. The platform keeps the record for each one.
01 Who owns it, and for what?
The AI Register holds one entry per AI system: its owner, purpose, risk band and review date. A check finds any AI co-worker or workflow that is not registered, registers it and raises a ticket.
02 What is it allowed to do?
An AI co-worker is an account with an access level, on the same access tree as your people. It reaches your data only through two controlled entrances, and only through calls you have registered. A call above its level does not exist for it.
03 What did it do?
Every change to audited data is recorded by the database itself in a chain of SHA-256 hashes, so a change made outside the screens is recorded too. Each AI turn is kept with its request, its response, the tools it called and its sources.
Your trail on this page · held in your browser, sent nowhere
04 Who checked?
A workflow stops at its approval step until a person decides, and the decision is recorded with their name. A workflow that mails what an AI wrote cannot be saved unless an approval stands on every path.
A co-worker's work is held for approval
05 How do we stop it?
The AI Kill Switch stops the gates, the models and the classifier from one screen. Each flip is recorded and mailed.
This page's switch · not yet tested
Why it passes review
The less of the work a model does on its own, the less there is to defend at the risk review.
Illustrative. The split varies by organisation.
Most of the work
An LLM builds the automation quickly. Once it is built, it runs without one.
The edge cases
Keep the LLM for the complex cases your current systems cannot cover.
Always
Access levels, human approval and an audit trail on both. The compliance report comes out of the same record.
The demo, step by step
We run this build live when we meet.
Outside the platformThe only way inInside, with your data
@sketch 1
@record
@table gifts
@width 900
The gift:
'Received by' fullname*: text | 'Email' email: text | 'Department' department [select: finance, operations, sales, board]: code
'From' giver*: text | 'Date received' received* [date]: date | 'Value' amount*: money
'What it was' description* [textarea]: long
The decision:
'Manager' manager: text | 'Decision' decision [select: pending, kept, returned, donated]: code
'Why' reason [textarea]: long
Nobody asked for what came with it
From the first request.
Personal data found and inventoried.
Old rows removed on schedule.
Every change in the hash chain.
AI stays outside. Your data stays in. See the security design
What you can do with it
Track record
Every capability in the platform was built for a real system first, in health, government, telecommunications and payments.
of research and development behind the platform.
deployments of data management systems and services.
Telecommunications · infrastructure audit
Government · Department of Education
Technology partners



How we engage
We agree what done means, what it costs and what evidence comes with it before work starts. Then we carry the delivery risk.
A controls document your reviewers can sign, and a go, fix or stop answer.
The outcome, acceptance criteria, access boundaries and a fixed price.
Fixed price. Weekly evidence, not status reports.
Your risk owner runs five checks. Failures are fixed at our cost.
Monitoring, a monthly evidence pack and kill-switch drills.
Coverage
Thirteen regulations and guidelines, point by point, against the code on 28 October 2026. We show what is not met yet, because your reviewers will ask.
MetIn partNot yet
Product roadmap
No dates are promised on this page. Ask us where each one stands.
Today it is set per co-worker.
Not ready to talk yet?
Tick the ones you cannot answer yet and see which team owns each one: legal, privacy, compliance, security, risk or commercial.
Five to ask any AI vendor. Including us.
Yes. The trail is a hash chain written by the database itself. A change made outside the screens is recorded too.
Only what its access level opens, through calls you have registered.
No. The AI describes and the platform builds.
To a local model first. Before an outside model, through the sanitiser where it is set.
About an hour to install. A first register can be on screen the same day.
For your risk committee
For government · PDF · 8 pages
For accountable officials. Monitoring AI policy, and a secure, compliant gifts register as the worked example.
Product paper · PDF · 8 pages
The five questions, the worked example, the security design and coverage regulation by regulation.
Technical paper · PDF · 8 pages
For architects, reviewers and auditors. The architecture, the full feature list, the ISO mapping and coverage with every count.
Next step
Tell us what is stuck. In two weeks you have a controls document your reviewers can sign, and a go, fix or stop answer. Then you decide whether to go further.