One engine. Every surface.
One Rust engine. Nine deployment surfaces. Six distribution channels. Three open protocols. This is how a single codebase defends consumer, developer, and enterprise without forking. This is the architecture.
One engine runs identically everywhere AI acts.
Every mode we ship, every deployment surface, every enterprise integration, every partner embed. Same Rust binary. Same detection pipeline. Same VOAF audit format. Same revocation primitives.
No forks. No lite versions. No separate consumer and enterprise codebases drifting apart. The engine you run on your laptop is the engine a Fortune 500 CISO gets behind their firewall. The difference is the admin layer above it, not the defense underneath.
This is what makes coverage the enterprise, consumer, developer, and partner at the same time structurally possible. It is also what makes every line of this platform page provable.
Four layers. One contract.
Every piece of Vigil fits into one of four layers. The engine runs every deployment. Every deployment plugs into every channel. Every channel is bound by the same open protocols. No part of the stack can drift from the others.
The Rust monorepo. 11 crates. One binary.
This is the only piece of Vigil that is not optional. Every surface, every channel, every partner embed runs this exact code. Deterministic enforcement. Sub-10ms policy path. Zero LLMs in the decision loop.
No single model catches everything.
Four orthogonal detection models run inline on every AI action. Each one is blind to failure modes the others catch. Together they cover statistical anomaly, behavioral drift, prior-informed risk, and change-point events in a single pass.
Intent is not the target. Action is.
Most AI security reads the prompt and asks whether the user should say this. That is the wrong surface. A poisoned prompt plus a compliant action is harmless. A clean prompt plus a runaway action is catastrophic. Vigil scores both and enforces on the one that can hurt you.
- › Agency category
- › Scope class
- › Sensitivity tier
- › Baseline lookup
- › Composite risk score
- › Policy evaluation
- › Pre-execution hold
- › User approval path
- › Outbound action analysis
- › Agency score
- › Post-response visibility
- › VOAF sealing
Two-surface analysis pipeline. Provisional filed. Protects the architectural separation between intent parsing and action scoring, the composite-risk Gate decision, and the deterministic enforcement contract. Foundational IP that cannot be replicated by a provider who cannot sit on the outside of their own API.
Pre-submit hold on any action above the agency threshold. Mobile approval in seconds. VOAF evidence sealed either way. No provider ships this because no provider can hold their own outbound request.
The Gate is the reason Vigil works. The full breakdown lives on the Defense page.
See the Gate in actionNine surfaces. One engine underneath.
Wherever AI runs, Vigil meets it. On your laptop. In your browser. In your cloud VPS. In your mobile app. In a partner's embedded agent. The engine is the same. The surface changes.
Six channels. One API contract.
The same engine reaches a solo user buying Guardian on Stripe, a startup running 500 agents on Gateway, an enterprise buying a CISO-grade deployment behind SSO, and a bank bundling Vigil into its consumer app. One API contract across all of it.
Three open standards. Two directions of leverage.
The protocols are open. Anyone can implement them. Adoption outside Vigil is the point. It makes the category real and makes us the default implementation. FICO, SSL, DigiCert. Publish the standard. Become the issuing authority.
Every claim has code underneath it.
This is not a deck. Every capability on this page is in production today, on device, under test, and running in v2.1.0.
Unit, integration, soak
P99, on device
Fly.io Singapore, healthy
Multi-day, chain intact
One engine. Every surface. Your move.
Platform explains how. Defense explains what happens when AI acts. Download runs the engine on your device today.