James "Hirsty" Hirst - Blog Post Header for article about building AI Governance

AI governance is an architecture decision, not a purchase

You can’t buy AI governance.

You can buy software with “governance” written on the box.

You can buy dashboards. Policy engines. Risk registers.

But governance itself isn’t for sale.

It’s like fitness.

You can buy the gym membership. The trainers. The watch that counts your steps.

None of it makes you fit.

What makes you fit is what you do, every day, without thinking about it.

AI Governance is the same.

It isn’t a product. It’s a consequence.

It’s what you end up with when you’ve built things a certain way.

Try this.

Take one AI call in your business. Any one.

An app asking a model a question.

An agent calling a tool.

A developer on a Friday afternoon, pasting code into a chatbot.

Now ask two questions.

Could we have stopped it?

Could we prove what happened?

If the answer is no, you don’t have AI governance.

You have a policy.

A policy is a promise.

Governance is the promise being kept. Every time. Without anyone having to remember.

That only happens one way.

Every call goes through a place where the rules get applied.

Who’s calling. What they’re allowed to do. What it costs. What gets written down.

One place. Every time.

That isn’t something you buy. It’s something you design.

And like most design decisions, it’s cheap to make early and expensive to make late.

We’ve been here before.

Fifteen years ago every team put its APIs out its own way.

Security was a checklist. Rate limiting was somebody’s side project.

Then something went wrong, and suddenly everyone wanted “API governance”.

The companies that got it had put a front door in. Everything came through it.

The companies that didn’t bought tools to audit a mess they couldn’t control.

AI is the same film. Bigger budget.

Even the experts can’t agree what it is.

Gartner and Forrester have both written about AI governance this year.

Read them side by side and they’re describing different things.

One is mostly about paperwork. Policies, assessments, accountability.

The other is about controls in the traffic, applied as each request happens.

One of our team read both and said: “Can’t imagine how confusing it is for buyers.”

He’s right.

But I don’t think either of them is wrong.

They’re holding different ends of the same elephant.

When the experts can’t agree what a category is, it usually isn’t a category.

It’s a property. It shows up wherever you’ve built for it, and nowhere else.

So if the board asks you to buy AI governance, don’t start with a shortlist.

Start with a whiteboard.

Draw every path an AI call can take through your organisation.

Mark where you could stop it.

Mark where you could prove it.

The gaps are your governance problem.

No product fixes a gap you haven’t drawn.

You don’t buy governance.

You build it in.

Or you bolt it on later, badly, and pay twice.

Further reading

Share the Post:

Related Posts

Start for free

Get a demo

Ready to get started?

You can have your first API up and running in as little as 15 minutes. Just sign up for a Tyk Cloud account, select your free trial option and follow the guided setup.