AI that handles sensitive data
De-identification before the model, fail-safe leak checks, and an architecture your compliance team can actually approve.
AI SaaS for regulated industries
Software that used to need a team of engineers — designed, built and run by a small senior studio. Two of our platforms are in production today.
The difference
The distance between a working prototype and software a regulated business will actually run is where most AI projects die. Tenant isolation. Audit trails. What happens when the model is wrong. Where the data lives and who can reach it. Billing, roles, admin tooling, support. We have built all of it, twice, and we ship to production — not to a slide deck.
What we’re good at
De-identification before the model, fail-safe leak checks, and an architecture your compliance team can actually approve.
Isolation, roles, per-tenant branding and central administration. Retrofitting this later is a rewrite.
Extraction, structuring, and turning what a business already has into something it can use.
The infrastructure under both platforms — containers, managed Postgres, CDK, CI to production.
Selected work
Built for Planfocus Consulting, an Australian advice-technology firm. Both are multi-tenant, both are live, and both solve problems that recur in every regulated sector.
Case study 01
Turns a dense 40-page compliance document into a client-ready interactive presentation in minutes — and the client’s personal data never reaches the AI.
A dedicated redaction engine strips every identifier before a single word is sent, then re-scans the result. Anything that slipped through is a hard stop.
Case study 02
Enterprise business intelligence, wrapped so a small business can use it — multi-tenant, branded dashboards built on Amazon QuickSight.
Complete data isolation per organisation, six granular roles, and dashboards embedded securely into a custom front end.
How we work
01
No layers, no handoffs to juniors. The person who scopes the work is the person who builds it.
02
We measure success by software running in front of real users, with billing, monitoring and support.
03
It is how we deliver a team’s output. It is also why our estimates look different from everyone else’s.
04
Documented handover of the code, the infrastructure and the decisions behind both.
Or what isn’t working. We reply within one business day.