Public website
neovail.com and www.neovail.com serve static marketing pages, legal notices, and trust materials. No customer evidence, product state, or operational telemetry belongs here.
Architecture
NeoVail keeps the public website separate from the SaaS control plane, regional telemetry intake, and customer-local enforcement layer. Each surface has its own trust boundary, data responsibility, and deployment cadence.
The public marketing site does not host product governance, telemetry intake, or runtime enforcement. Those responsibilities live in separate services so security, compliance, and procurement can reason about them independently.
Static marketing pages, legal notices, trust pages, and demo entry points.
Policy administration, AI asset graph, evidence review, and customer workflow management.
Sentinel telemetry intake with customer-selected residency, handling, and retention rules.
Local enforcement boundary where verification, policy checks, and blocking happen before actions proceed.
This is the practical split behind the product and the website. It keeps public-facing content, governed operations, and customer-local controls from collapsing into one mixed trust zone.
neovail.com and www.neovail.com serve static marketing pages, legal notices, and trust materials. No customer evidence, product state, or operational telemetry belongs here.
app.neovail.com is the operator surface for AI asset inventory, policy administration, evidence review, and customer workflow management.
ingest.eu.neovail.com and other regional endpoints receive Sentinel telemetry under customer-selected residency and data-handling rules.
Sentinel runs next to models, agents, and MCP servers to make runtime decisions before actions are allowed to proceed.
The path is intentionally narrow: observe locally, classify centrally, enforce locally, and export evidence when asked.
Sentinel observes model, agent, and MCP activity inside the customer environment where the action originates.
Regional control planes correlate assets, identities, policies, and runtime events to determine the applicable governance posture.
Decisions are applied at the runtime boundary, gateway, or policy hook before the action can proceed.
Administrators can export records that show what happened, which policy applied, and what the outcome was.
neovail.com and www.neovail.com host static marketing pages with no customer evidence, no database, no authentication, and no backend dependency.
app.neovail.com is the product surface for regional governance, policy administration, asset graph review, and evidence workflows.
Regional intake endpoints receive Sentinel telemetry under the deployment and residency model selected by the customer.
Sentinel operates in the customer environment alongside models, agents, MCP servers, and runtime systems.
Future private deployment options can support stricter network, identity, and residency constraints.
Future support is planned for AKS, Azure Arc, AWS, GCP, and other enterprise runtime environments.