Zero-egress diagnosis
Keep raw logs, signatures, incident records and monitoring inside the controlled network boundary.
For regulated and isolated environments
Air-gapped and on-premises GPU failure diagnosis
Air-gapped reliability work cannot depend on uploading a proprietary training log or calling a hosted model. The diagnostic path, pattern corpus, incident record and monitoring output must operate inside the environment and remain useful when no external service is reachable.
Denpex local mode runs its deterministic diagnosis engine on the host, stores incident JSON locally and exposes Prometheus metrics. Hosted research and AI fallback are unavailable offline, so the evaluation must test whether deterministic coverage is sufficient for the environment's real failure mix.
Who this is for
- Defense and national laboratory teams
- Regulated enterprise AI teams
- On-premises ML platforms
- Security architects
- HPC administrators
- Data center infrastructure engineers
The failure surface
These incidents look adjacent in the final alert, but they require different owners and different proof before recovery.
Offline software supply
Verify agent, engine and pattern artifacts with the published checksum manifest before import.
Existing monitoring
Expose local Prometheus metrics for the environment's approved collection and dashboard stack.
Coverage boundaries
Measure deterministic coverage explicitly because hosted fallback and live research are not available offline.
The operating loop
- 1
Import verified artifacts
Transfer the agent, local engine and pattern database through the approved software supply process.
- 2
Audit zero egress
Run dry mode and network controls to verify what the selected deployment can and cannot transmit.
- 3
Diagnose and record locally
Wrap jobs or inspect saved logs while incident files remain in the configured local directory.
- 4
Export only approved metrics
Route Prometheus output and reports through the organization's existing security boundary.
What Denpex contributes
- On-host deterministic diagnosis with no API key in local mode
- Local incident JSON and Prometheus fleet-health output
- Client-side masking and strict signature-only modes for connected deployments
- Published checksums and documented Kubernetes, Slurm and bare-metal installation paths
Measure this in an evaluation
Use your incidents and timestamps. These are measurement definitions, not Denpex customer-outcome claims.
| Metric | Measurement |
|---|---|
| Zero-egress verification | Observed outbound connections and payload inspection under the organization's own network controls. |
| Offline coverage | Resolved historical incidents correctly routed by the deterministic path without hosted assistance. |
| Update effort | Operator time to verify, import, deploy and roll back a signed pattern or agent release. |
| Local resolution time | Time from incident capture to verified action while disconnected from external services. |
Start with the technical evidence
Self-hosted installation
Review the documented in-VPC and zero-egress paths, prerequisites and metrics.
Trust Center
Inspect current controls, subprocessors, responsibilities and document requests.
Architecture brief
Request the deeper data-flow, deployment and evaluation material.
Evidence policy
See the current evaluation status and limitations before procurement.
Frequently asked questions
What leaves the cluster in Denpex air-gapped mode?
The documented DENPEX_LOCAL path performs deterministic diagnosis on the host, writes local incident records and serves local Prometheus metrics. It does not require an API key and does not send logs, signatures or heartbeats to the hosted service.
What functionality is unavailable without outbound access?
Hosted AI fallback and live external research are unavailable. The bundled deterministic matcher, causal pipeline, local incident records and metrics remain available. A pilot should quantify which historical incidents require evidence beyond that offline path.
How are software updates moved into an isolated environment?
The organization controls transfer and approval. Denpex publishes the agent bundle and checksum manifest; the operator verifies artifacts before import and should test both update and rollback in the target deployment process.
Does the public site prove qualification for our compliance regime?
No. The Trust Center documents current controls and status, while organization-specific accreditation, hosting, contractual and support requirements require procurement and security review. Denpex should not be represented as approved for a regime solely from a marketing page.
Prove it on incidents your team already resolved
Freeze the expected owner and outcome, replay the evidence, then compare operator time and decision quality with your current process.
Build the evaluation plan