Inventory, risk tiering and controls that survive contact with fifty models — plus the evidence an auditor asks for and most programs cannot produce
On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.
Last updated:
Most AI governance programs work at five models and break at fifty. The failure is structural: controls designed around manual review committees do not scale, so teams route around them and the program becomes a document rather than a control.
The programs that hold share three properties. They know what exists, because there is a real inventory. They apply proportionate controls, because not every model warrants the same scrutiny. And they generate evidence automatically, because evidence assembled by hand at audit time is evidence that will not exist.
This guide covers that sequence, and the technical prerequisite most governance frameworks omit: you cannot enforce what you do not control.
Governance that cannot say no is advisory. The sponsor needs authority to block a deployment, which is what makes the rest of the program credible.
Including shadow AI. A program built on the sanctioned inventory alone governs a fraction of the actual exposure.
Sector rules, the EU AI Act where relevant, and internal policy. Scope disagreements surface late and expensively if not settled at the start.
Governance requires enforcing constraints and producing logs. If both live inside a vendor's platform, your program depends on their roadmap.
You cannot govern what you have not enumerated. Most organizations discover materially more AI in use than they expected, much of it embedded in vendor products nobody classified as AI.
This is the category most often missed entirely.
Punitive framing guarantees an incomplete inventory.
Uniform controls fail in both directions: too heavy for low-risk uses, so teams route around them; too light for high-risk uses, where the real exposure sits.
If everything is high-risk, nothing is.
A control that depends on a person remembering is a preference. Prefer controls the platform enforces: scoped permissions, routing rules, mandatory logging, human confirmation on consequential actions.
Audit evidence assembled by hand at audit time is evidence that will not exist. The program must produce its record as a by-product of normal operation.
The EU AI Act sets a six-month floor for high-risk deployers.
Manual review committees are the bottleneck that kills governance at scale. Reserve human review for the top risk tier and automate assessment for everything below it.
Slow governance is the leading cause of shadow AI.
Approval at launch governs a system that no longer exists six months later. Models change, usage drifts, and new integrations appear without a fresh assessment.
A review process measured in weeks against an alternative available in a browser tab guarantees shadow AI. Turnaround time is a control, not an administrative detail.
Enforcing constraints and retaining evidence both require control of the platform. A program built on a hosted product is bounded by that vendor's feature set and retention terms.
The EU AI Act's Annex III high-risk deadline was moved from August 2026 to December 2027 by a provisional agreement approved in June 2026. The direction is settled; the dates are not.
Manual assessment cost scales linearly with AI adoption. Programs that do not automate become the reason AI adoption slows, which is not a defensible outcome.
Periodic discovery sweep compared against the recorded inventory
Median days from submission to decision, tracked per tier
Sampled audit reconstruction on real historical requests
Egress monitoring for known endpoints plus anonymous survey
Consequence: The policy governs the AI you knew about, which is usually a fraction of what is running.
Prevention: Enumerate first. The inventory almost always changes the policy you would have written.
Consequence: Low-risk uses route around a process that is too heavy, and high-risk uses get scrutiny calibrated for the average.
Prevention: Tier by consequence and make the lowest tier genuinely lightweight, so the process is worth following.
Consequence: Systems are approved once and then drift — models update, usage changes, integrations appear — with no reassessment.
Prevention: Schedule re-review and monitor for model version changes and usage drift as ongoing controls.
Consequence: The audit trail lives in a vendor platform, so ending the contract or a dispute with the vendor removes your ability to answer a regulator.
Prevention: Store audit evidence inside your own boundary in a schema you control and can export in full.
ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.
Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.
Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.
Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.
Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.
ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.
See how ibl.ai deploys AI agents you own and control—on your infrastructure, integrated with your systems.