In design Shaping it with design partners

Know who can access what, and why.

Shield is AI access governance we're building for regulated teams: a plain-language map of who can reach what, risky grants flagged with the reasoning behind them, and no change made without a person's sign-off.

// the problem

Access reviews are rubber stamps.
Auditors know it.

Permissions pile up faster than anyone can review them. The quarterly review becomes a spreadsheet people approve without reading, and when the auditor asks why someone still has production access, the honest answer is "nobody remembers." That's also the wall that stops AI projects from touching real data.

01

Granted for a deadline

Someone needs prod access "just for this release".

02

The deadline passes

The access doesn't. Nobody owns removing it.

03

2,000 rows in a sheet

Review time arrives as a spreadsheet no one can reason about.

04

Approve all

Risk stays, evidence is thin, and it repeats next quarter.

// what we're building

Same rule as PATH:
AI explains, people decide.

Shield comes from the same FDE practice and the same instinct: make the safe path the easy one, and keep a human on every decision that matters.

01

A map people can read

Who can reach what, written in sentences that a compliance lead can sign off on, not a dump of policy JSON.

02

Every flag shows its reasoning

Unused, stale, over-broad or out of policy: Shield says which, and shows the evidence behind it.

03

Nothing changes on its own

Shield proposes the narrower grant; a person approves it; the change is recorded with their name on it.

04

Evidence by default

Every review produces the artefact your auditor asks for, instead of a screenshot hunt the week before.

STATUSShield is in design, not yet available. We're shaping it with a small number of design partners in regulated industries. If access reviews are a quarterly pain for you, we'd like to talk.
// shape it with us

Become a Shield design partner.

Tell us where access governance hurts today. Design partners get early builds and a direct line to the people writing the code.

We reply to every request.