Skip to content

Your secret advantage

Residency
Onshore
Data plane in-country, exceptions named
Region
ap-southeast-2
AWS Sydney
Models
Zero-retention
No training on your data

Every figure links to the artifact that backs it

Who we build for

Systems that can’t go down, and can’t leak.

Health services, universities, and Australian public-sector teams don’t get to treat governance as a later phase. Neither do we.

Health systems

Clinical work runs on systems that can’t go down and can’t leak. We build inside those constraints, not around them.

What we build

Universities and research

Research data carries its own governance. The build respects the ethics approval, the corpus, and the people using it.

How we work

Government and public sector

An onshore data plane, named exceptions, and gates a reviewer can read before they’re asked to trust the system.

Our posture, in full

Sovereign environments

Where the model can’t phone home: local inference on hardware you control, air-gap capable, keys yours at handover.

Sovereign software
How we work

Three moves, repeated.

No decks, no discovery theatre. The one problem worth a build never announces itself. We go in and find it.

Immerse

We sit inside the work until the real constraints show up. The brief never lists them.

Spot

We hunt the requirement no one has written down: the gap where a system earns its keep.

Execute

We build it and ship it to production. Then you decide who runs it.

Evidence

Proof you can check.

We’re a young lab. No logo wall, no borrowed testimonials. What we can show is live: the gates every commit clears. Those gates run on our own platform, the one serving this page. They are the standard we hold ourselves to, not a client reference.

app/console · trust pack
checking
RLS isolation harness
…
live result, written by CI
-- Trust badge: founder/ops read; definer-only insert (the CI reporter); append-only.
create policy trust_select on public.trust_isolation_results for select to authenticated
  using ((select (auth.jwt() -> 'app_metadata' -> 'roles')) ?| array['founder', 'ops']);
create policy trust_definer_insert on public.trust_isolation_results for insert to postgres with check (true);
revoke insert, update, delete on public.trust_isolation_results from authenticated, anon;
row-level security · from our codebase · supabase/migrations/20260626090006Every gate, live ›
Gate · CI

Tenant isolation, run on every commit

A harness walks every tenant-scoped table and reports leaks. The verdict on this page is the one it last wrote.

Read the artifact
Open source

The gates, published

The checks we hold ourselves to are readable, runnable, and not a claim you have to take on trust.

Read the artifact
Security and sovereignty

Governed by default.

Sovereignty and security aren’t a phase at the end. The data plane runs onshore, models run with zero retention, and row-level isolation is there from the first commit. Where something sits outside the jurisdiction, we name it on the trust page rather than round it off.

  • Zero data retention
  • Row-level security
  • Data sovereignty
  • WCAG 2.2 AA
Visit the trust centreLive status
Data plane
ap-southeast-2 (AWS Sydney)
Model terms
Zero-retention
Isolation
Row-level, from the first commit
Exceptions
Named on the trust page
The next step

Bring us a problem.

Two hours. Your team, the engineer who would build it, and the work itself. You’ll leave holding the opportunity map, whether or not we build it.

Request the 2-hour immersion

No preparation needed. Bring the work as it is.