“Did we stop it?”
Stopped cold.
Killed at the driver boundary. Zero bytes left the host.
Arca/Sentry watches GPU activity at the NVIDIA driver boundary and enforces your policy on the host → allow, alert, terminate ← recording every decision to a continuous, append-only audit ledger you can export for an auditor. Air-gapped, on-host, no third party in the trust path.
For teams that control the host kernel — owned hardware or dedicated / bare-metal instances (CoreWeave, Lambda, and the like). Not for hosted-API or serverless GPU tenants.
A 26-program eBPF layer (uprobes + ioctl tracepoints) taps the NVIDIA driver boundary; every GPU operation streams into the on-host Sentry — no code changes, no SaaS.
Each event is scored against the persona template you choose — DoD IL5/IL6, HIPAA, Custom. Your threshold decides allow, alert, or terminate the offending process. (Model-driven scoring requires the SLM entitlement build; the default install runs heuristic detection.)
Every decision writes to a continuous, append-only audit ledger you can export as a report for your auditor. Nothing phones home.
Watch GPU activity at the NVIDIA driver boundary and enforce your policy on the host. Record every outcome to a continuous, append-only ledger you can export as a report for a regulator or auditor. One operator persona governs the whole loop — host-native, air-gapped, no third party in the trust path.
Built for the autonomous frontier. Designed for CISOs, infrastructure leads, and sovereign AI operators.
The Sentry enforces your policy on the host. The Ledger is what it produces — automatic, tamper-evident proof of every decision. Nexus rolls that proof across many hosts once you outgrow one or two. One kernel-level engine; Linux + NVIDIA, on hardware you control.
The kernel-level agent. In-kernel policy, operator-armed enforcement.
Every device→host transfer of proprietary weights, CUI, or PII is scored against your persona and recorded; your threshold decides allow, alert, or block — before bytes leave the host.
DoD (IL5/IL6) · HIPAA · Custom — via on-host SLM. The persona is the policy: you own the decision, we enforce it.
Detects hung GPU processes the moment they start burning your bill; your persona decides whether to alert or, when you've armed enforcement, block.
Four fronts. One engine. We deploy where the model is the asset and the records have to hold up for an accrediting official, a board, or a safety review.
Run AI on classified and CUI workloads with a kernel-grade audit ledger your accrediting official can read. Model-weight and CUI transfers are scored at the NVIDIA driver boundary and sealed into the ledger — your policy decides allow, alert, or block. Fully air-gapped, no phone-home. Space and national-security programs included.
When the model is the IP, the weights are the target. Every oversized ioctl is scored at the driver boundary and sealed into the ledger; your persona threshold decides allow, alert, or block. For AI labs, fintech, and any shop where the model is the business.
Health-AI vendors prove how PHI was handled on every GPU. Each launch and ioctl is scored at the driver boundary and sealed below the application as kernel-grade evidence for HIPAA and FDA SaMD review — the tamper-evident ledger you hand to every hospital customer's auditor.
Kernel-level policy gates for the specialized AI accelerators inside autonomous fleets, where software lag is a safety risk, not a performance issue. Same Sentry, smaller footprint.
The same kernel event, mapped to the question you're paid to answer. CISO, compliance, CFO: pick the lens, read the receipt.
A short-lived process tried to copy 14 GB of model weights off the GPU. Arca scored it and stopped it at the driver — before a byte left the host.
“Did we stop it?”
Killed at the driver boundary. Zero bytes left the host.
“Can I prove it?”
Matched to HIPAA §164.312(e)(1) and signed into a tamper-evident chain.
“What did it save?”
GPU-hours reclaimed and +12% VRAM headroom freed — on a single H100.
Standard tools report 100% GPU utilization and call it healthy. We time GPU memory-staging at the driver to estimate how much of that time is your fleet waiting on memory rather than computing — often a large share, and much of it reclaimable.
We see every kernel launch on every host. The Ledger seals it. Below is one normal week on a sample 24-GPU fleet. The dim stretches are where your CFO is paying for nothing — and where Sentry's zombie policy reclaims VRAM in real time.
The Sentry and its Ledger are live and deployed today. Nexus is the fleet hub you add once you run more than a host or two. The same kernel-level engine is next being retargeted at the LLM cores inside humanoids and drones.
FLEET HUB · OPTIONAL · INSIDE YOUR PERIMETER
For teams operating many Sentries, one hub per perimeter rolls every host’s verdicts into one place: air-gap deployable, inside your environment, no third party in the loop.
White-glove deployed by our engineering team. You don’t install it. We do. Browse the surface first; talk to us when you’re ready.