Regional tenancy
Control planes are designed around regional deployment boundaries for enterprise residency and governance requirements.
Security
Built for enterprise AI governance boundaries.
NeoVail separates public marketing, SaaS control, regional ingestion, and customer-local runtime enforcement so sensitive evidence and policy decisions stay on the right side of the boundary.
Last updated: May 15, 2026
Security posture
NeoVail is designed for regulated environments that need controlled tenancy, strong identity alignment, and evidence-grade auditability.
Customer-local Sentinel
Sentinel nodes run near customer models, agents, and MCP servers to verify runtime state without embedding enforcement in the website.
mTLS-ready architecture design
Runtime intake and enforcement paths are designed to support mutual TLS, certificate rotation, and service identity controls.
Managed identity friendly
NeoVail is intended to align with enterprise identity patterns across cloud and Kubernetes environments.
Least privilege
Access to assets, evidence, and policies is modeled around scoped roles and minimal operational permissions.
Audit trails
Runtime decisions, administrative changes, and MCP access outcomes are recorded for review and evidence export.
Marketing site separation
This public website is not the NeoVail control plane. It has no authentication, database, customer evidence store, enforcement path, Supabase dependency, secrets, or product backend logic.
No sensitive customer evidence is stored on the public website. Control plane operations, telemetry intake, and Sentinel enforcement belong to separate product infrastructure. Security architecture statements on this page describe intended product design and should not be read as a third-party audit certification.