Security and readiness
A strong control path is more useful than an unqualified security claim.
Vaqri is designed for supported, controlled paths. Its public posture distinguishes implemented code and test evidence from external release and production gates.
Request a private briefingControl principles
Fail closed at the boundary. Retain evidence after the decision.
- Tenant-scoped identity, authorization, and audit evidence
- Policy-controlled action decisions with explicit approval and denial states
- Signed command envelope and MQTT gateway re-verification direction
- Replay, expiry, nonce, and provenance checks in the control path
- Canary, pause, rollback, telemetry, and evidence retention capabilities
Readiness boundary
Production certification requires more than a build or a test suite.
The repository records external requirements that remain outside this public-site implementation: named production infrastructure, immutable image deployment, backup restore evidence, independent security review, and an observed rollout with approvals. Until those records exist, Vaqri should be described as a release-candidate or staging direction, not production-certified.