Present in the inspected product or runtime source. Deployment still requires version-specific validation.
A documented customer-facing boundary or responsibility. A signed agreement takes precedence.
An intended product path, not a current universal capability or delivery commitment.
Not established by the reviewed source, documentation, or published run evidence.
Who can approve a new runtime release?
The Trust Console keeps the customer approval key on the customer machine and signs exact hashes. Manual and allowlist modes preserve a practical customer veto; auto signs every control-plane-requested hash and gives up that per-release veto while enabled.
Does Infraveil need custody of application source?
The answer depends on mode. Managed source-upload deployment stores selected application source and packages on the hosted side. Fresh no-source attach uses a manifest-only package and observes existing systemd units; it leaves their deployment and restart ownership with the existing system. Changing modes does not prove that older hosted files were removed.
Does “no-source” mean nothing is stored on disk?
No. The runtime stores the manifest/package and can store local state, caches, logs, receipts, runtime dependencies, and customer-configured persistent paths. Inspect the actual host paths and cleanup behavior.
What happens if the hosted plane is unavailable?
Reachability loss does not itself stop or revoke running local agents. Current or cached local state can support continued supervision, but new coordination, approvals, reporting, and revocation delivery can be delayed. Queues and storage are bounded. This is local continuity, not full offline management or automatic cross-host failover.
Does the gateway protect all application traffic?
No. Its controls apply to traffic that traverses configured managed routes. Direct origin access, an alternate listener, or another network path can bypass it unless the customer restricts those paths.
Is this upstream DDoS protection?
Not by the gateway alone. Infraveil-hosted public endpoints currently use OVHcloud upstream Anti-DDoS infrastructure and Cloudflare for configured proxied web traffic, while the gateway applies origin-side controls to managed routes. Those provider layers do not cover every customer workload, direct origin address, unproxied hostname, non-HTTP service, or bypass listener. Customer deployments should retain appropriate upstream mitigation and restrict direct origin access.
What remains the customer's responsibility?
Application correctness, host hardening, infrastructure accounts, network exposure, dependencies, secrets, persistent data, backups, capacity, health definitions, recovery compatibility, user access, and workload-specific incident response remain customer responsibilities unless an applicable agreement says otherwise.
What does a receipt mean?
A receipt records a defined step and its reported state. Intent, customer approval, byte integrity, process execution, health, reachability, and recovery are separate facts. The signed agreement and current product documentation define the applicable retention and support boundary.
Will every operational tool be replaced?
That is not a product commitment. The direction is to reduce coordination across deployment, runtime supervision, gateway policy, evidence, incidents, and recovery where one operating model adds value. Specialty tools may remain appropriate.
Are self-hosted management and full air gap planned?
Private deployment options can be evaluated as product direction, but this page does not present a self-hosted management plane or full air-gap operation as a current universal capability.
What reliability has the Validation Protocol demonstrated?
This chapter publishes no completed request-bearing Validation Protocol run. Its historical smoke attempt failed with zero requests and establishes no reliability result. Other tests support only their recorded scenarios, builds, and conditions; they do not become a completed protocol run by association.
Which enterprise controls are universally available?
Fine-grained RBAC, SSO/SCIM, SOC 2 status, data residency, contractual SLA, regional topology, and support-access details are not established here as current universal capabilities. Confirm each requirement for the current offering and agreement.
Ask for the record that matches the claim.
For runtime behavior, request a dated execution bundle. For hosted controls, request current product documentation and contractual terms. For a delivered component, inspect its exact source and hash. If the evidence cannot distinguish intent, execution, and outcome, keep the answer unknown.