How we use this on our own hosts
Optics is free and self-serve on GitHub.
Vantio-operated environment
We run Optics and Phantom Engine on the agent infrastructure we operate, and we publish clearly labeled operational evidence. That shows how we use the system.
- Optics
- Attached to the agent processes we run
- Enforce
- Enforcing the policy we configured
- Phantom Engine
- Protection enabled on the enrolled Linux hosts
- Continuous Assurance
- Checking that those controls are still on
- Prompts and completions
- Not stored
This is evidence from infrastructure Vantio operates. It is not a customer deployment, it is not an independent audit, and it does not stand in for validation on infrastructure Vantio does not operate.
What this does not cover
- No customer deployment has been independently validated.
- No design partner has run this on their own infrastructure yet.
- Certifications and authorizations are separate programs and are not held.
- Robotics, drone, industrial, and vehicle deployment do not exist.
Read the full evidence record
Vantio protects the Linux hosts that agents and planners run on, including lab boxes and fleet servers next to physical systems. It does not own motors, safety loops, or clinical or vehicle certification. Formal certifications and authorizations remain a separate program. Detail lives on Compliance.
Solutions
How we design Vantio
These are the design principles we use when we build Vantio. They describe how we work. They are not a guarantee of every deployment.
- An agent cannot approve its own authority expansion.
- Unknown state is never shown as protected.
- Application controls stay distinct from host Control.
- Optics does not retain prompts or completions.
- Evidence is exportable.
- Customers can stop, verify, recover, and leave.
- Certifications are separate from product evidence.
Product and install questions: hello@vantio.ai. Phantom Engine and Enterprise: sales@vantio.ai. Vulnerability reports: security@vantio.ai.