Capability without code change
05- 01
Change your AI vendor without changing your application
Every team that shipped an AI feature is married to whichever model they integrated first. It does not have to be a code change.
- 02
Nobody switches models, because nobody can defend the quality risk
The reason your AI bill keeps growing is not that cheaper models do not exist. It is that no engineer will stake their name on one without evidence.
- 03
Approval for software you cannot change
Step-up approval is straightforward to add to software you are actively building. Most software is not that. There is another way in.
- 04
Get your API keys out of your applications without editing them
Every organisation knows where its credentials are. In configuration files, inside software nobody wants to open.
- 05
What does AI actually cost you, per team?
Most organisations can tell you their total AI bill and almost nothing else about it. That is a reporting problem with an expensive shape.
The person's data
01Governance and refusal
06- 07
Your agent should never hold a credential
We have spent two years asking how to watch what AI agents do with access. The better question is why they have it.
- 08
Asking a human without holding the connection
Every design that puts a person in the path of a request eventually meets the same wall. Here is the way through it.
- 09
A caller must not choose its own policy
A defect family that shows up in almost every gateway, proxy and policy engine, including ones built by careful people.
- 10
Deny by default is a claim you can test in ten seconds
Almost every platform claims it. Very few survive the obvious experiment. Here is the experiment.
- 11
Govern the web, and leave everything else alone
The most useful thing a gateway can tell you is what it does not touch. Three questions that find out.
- 12
What an audit trail actually has to answer
Most audit logs are built to satisfy retention. Then something goes wrong and you discover what you needed instead.