PROVOST BY IGNITE9 · SECURITY AND CONTROL
AI agents that cannot act beyond the authority you give them.
Provost by Ignite9 is the governed AI operating system. Its controls are part of how every action runs, not a setting someone can forget to switch on.
GOVERNANCE AND ISOLATION
Ten controls on every piece of work.
Policy engine on every action
Each agent action is allowed, held for approval or refused before it runs.
Named human approval
Anything that changes a system waits for a named approver on your side.
Separation of duties
Nobody approves their own request, and one person counts as one party even when they sign in with several identities.
Multi-party approvals
Sensitive changes can require more than one approver.
Tamper-evident audit trail
Every event is hash-chained, so any later edit to the record shows.
Freeze and kill switch
Each tenant can be frozen, or all agent activity stopped, in one action.
Isolated sandboxes
Each agent action runs in an isolated process sandbox (Linux namespaces, seccomp and AppArmor).
Write-only credential vault
System credentials sit in a vault the agents never see.
Read-only by default
Each system connection starts read-only. Write access needs a second approver.
Connectors stay in their lane
Each connector can reach only its own vendor’s hosts.
DATA BOUNDARY GATEWAY
Your business data does not leave as itself.
Before anything reaches an outside AI model, sensitive business data is replaced with placeholders. The real values are restored only in the answer, inside your boundary. Each client chooses the gateway mode: off, code-only or consented. Every call is audited.
REPLACED BEFORE ANY OUTSIDE MODEL
- Names
- Email addresses
- Bank and account numbers
- Tax IDs
- Card numbers
- Amounts
- Your own term lists
RELEASES YOU CAN VERIFY
Signed releases, staged rollouts, one-action rollback.
Releases are signed images with a software bill of materials. Changes to policy or configuration get an impact analysis and multi-party approval, then roll out in stages (sandbox, then pilot, then everyone) with freeze windows and one-action rollback.
STATED PLAINLY
- SOC 2 and ISO 27001 have not started; we claim neither.
- Micro-VM sandboxes and confidential computing are on the roadmap.
- Connecting to your real systems is a pilot step, with your security team.
NEXT STEP
See Provost on one of your own processes.
In a briefing we walk through Provost on a process you choose, answer your security and risk team’s first questions, and agree whether a design-partner pilot makes sense.