Skip to content

ERPAIIntegration

Menu

Case studies Governance Lessons Watch it work The journey How it's built Live health Contact

Questions we answer

Can we trust AI to act on its own?Governance and guardrailsWho allowed the AI to do that?Identity travels with every requestCan someone talk the AI into something risky?Risk-graded autonomyCan we see who did what, and why?One thread from request to resultWhere are the keys kept?One vault, no shared secretsWhy did the AI bill jump, and who spent it?One counted doorwayIs every task getting the right model?Right model, right taskWhat if our AI vendor goes down or raises its price?No single point of supplyAre we paying for tools that do the same job?One tool per jobDoes the AI forget everything between conversations?Governed shared memoryIs this producing real work, or just answers?The digital factoryWhich work should run itself?Managed, not scriptedCan we get more from the Copilot licences we already pay for?Copilot proposes, the platform verifiesWill people actually use it?Meet people where they workHow much time do people lose sorting inbound information?Intake to insight, untouchedCan the same platform run a real business?One governed foundation for every productWhat happens when it breaks at night?Detect, fix, escalateWhere is the list of what is open, and who owns it?One list, closed with evidenceCould we recover if we lost everything?Proven by restoringCan you prove it to an auditor?Challenge before acceptanceDoes it get better over time, or just older?Every lesson becomes a ruleWill this still work after the next upgrade?Clean Core for AIDo our documents match what is actually running?Documentation as a by-productCan we trust AI to act on its own?Governance and guardrailsWho allowed the AI to do that?Identity travels with every requestCan someone talk the AI into something risky?Risk-graded autonomyCan we see who did what, and why?One thread from request to resultWhere are the keys kept?One vault, no shared secretsWhy did the AI bill jump, and who spent it?One counted doorwayIs every task getting the right model?Right model, right taskWhat if our AI vendor goes down or raises its price?No single point of supplyAre we paying for tools that do the same job?One tool per jobDoes the AI forget everything between conversations?Governed shared memoryIs this producing real work, or just answers?The digital factoryWhich work should run itself?Managed, not scriptedCan we get more from the Copilot licences we already pay for?Copilot proposes, the platform verifiesWill people actually use it?Meet people where they workHow much time do people lose sorting inbound information?Intake to insight, untouchedCan the same platform run a real business?One governed foundation for every productWhat happens when it breaks at night?Detect, fix, escalateWhere is the list of what is open, and who owns it?One list, closed with evidenceCould we recover if we lost everything?Proven by restoringCan you prove it to an auditor?Challenge before acceptanceDoes it get better over time, or just older?Every lesson becomes a ruleWill this still work after the next upgrade?Clean Core for AIDo our documents match what is actually running?Documentation as a by-product

Portfolio / Secure by Design

The business question · Secrets and certificates

“Where are the keys kept?”

The concept

One vault, no shared secrets

Keys live in one governed place and never travel through code or chat.

How it works: One vault holds every key, services receive their keys from it automatically, and every save is scanned so a key cannot slip into code or chat.
Why it matters: The most common way automation leaks is closed, and changing a key becomes routine instead of risky.
The result: Nobody needs to know a password to run the platform day to day, and saved work is checked for secrets before it leaves the server.

See it workingOne vault, no shared secretsAnimation

One vault holds every key, services receive their keys from it automatically, and every save is scanned so a key cannot slip into code or chat. Animated from the platform's real setup.

The business problem

Keys scattered across files make every change a risk.

Keys pasted into scripts, chats and shared drives are the most common way automation leaks. Many services needed keys and certificates. Spreading them across files would make every change a risk and every rotation a manual job.

▶ Watch the answer: Who is your AI acting for?

Why this concept

One secrets vault as the source of truth, with settings written from it on a schedule

One source of truth means one place to govern, audit and rotate.

Also considered

Keep keys in each service's own settings

How it works

One vault, no shared secrets

Vault

The one place keys live

Services

Receive their keys automatically

Scanner

Checks every save for keys

Certificates

Renew themselves

Result

No key in code or chat

What we put in place

Moved settings into a secrets vault that writes each service's settings on a schedule.
Added a secret scanner that checks every save to the code repository.
Certificates are issued and renewed automatically, with an alarm well before expiry.

The result

Before

Keys scattered across files make every change a risk.

After

Nobody needs to know a password to run the platform day to day, and saved work is checked for secrets before it leaves the server.

I treat security hygiene as an operating routine, not a one-time project.

In your organization

One simple standard for where secrets live that every team can follow.

Related case studies

Agent and user authentication

“Who allowed the AI to do that?”

The conceptIdentity travels with every request

Read the case study

Approvals and guardrails

“Can someone talk the AI into something risky?”

The conceptRisk-graded autonomy

Read the case study

Next case study

One counted doorway

Lessons learned

Contact

Looking for someone to lead AI from pilot to production?

I would be glad to walk you through any part of this live and talk about the role you have in mind.

Email me LinkedIn One-page brief

j.walters@erpaiintegration.com

Go deeper: Lessons · The journey · How it’s built · Live health