One hub for the
whole fleet.
Arca Sentry stands alone on every GPU host. When you operate many hosts, Arca Nexus is the optional enterprise hub that rolls every Sentry's verdicts into one place inside your perimeter, on your terms, with no third party in the loop.
One Nexus per perimeter. Many Sentries per Nexus.
Each Sentry forwards its ledger entries to Nexus over a secured stream. Nexus stores them durably, de-duplicates re-deliveries automatically, and surfaces the fleet on a dashboard local to the server.
A small forwarder daemon on each host does the talking, with stricter privileges than the Sentry itself. The bookmark only advances on a confirmed write, so dropped connections don't drop data and reconnects don't double-count.
Four guarantees that make
fleet rollup trustworthy.
Not a SaaS pipeline. Not a third-party aggregator. A hub you run inside your perimeter, with identity and durability you can audit.
Secured, mutually authenticated stream
Sentries forward ledger entries to Nexus over a secured stream that authenticates both sides. Nexus refuses anything it can't verify. A small forwarder daemon on each host does the talking; it runs with stricter privileges than the Sentry itself, so a host-side compromise doesn't move the trust boundary.
Identity verified per entry
Every entry declares which host it came from. Nexus checks that claim against the host's own credentials on every entry it stores, so spoofing fails even if a Sentry host is compromised.
Durable and de-duplicated
Entries land durably the first time. If a connection drops and a Sentry re-sends, Nexus deduplicates for you with no double-counting and no gaps. Bookmarks advance only after a confirmed write.
Sovereign by design
License verification is offline against a signature baked into the binary. No callbacks to anywhere. The fleet dashboard stays local to the Nexus server by default. The hub needs nothing from the outside world.
Sovereign by default.
No calls to anywhere. License verification runs offline against a signature baked into the binary. The fleet dashboard stays local to the Nexus server by default. The hub needs nothing from the outside world.
License renewals are picked up automatically when you drop a new license file in place, still offline, still no callbacks.
- Every Sentry · one pane
- Verdicts · alerts · ROI
- Inside your perimeter
- Local-only by default
The fleet, on one pane.
Health, nodes, zombie alerts, exfil incidents, and VRAM reclamation in dollars, rolled across every Sentry your Nexus operates. Refreshes on its own.
Lightweight by design: no SPA framework, no outbound assets. Point your incident tooling at the same data if you prefer your own pane.
Hardened deployment. Stricter privileges than the Sentry itself.
Nexus runs under its own identity with stricter privileges than the host-side Sentry, so an issue on a Sentry host cannot move the trust boundary. Hub data and host data live in separate places, never overlapping.
Deeper technical detail lives in our deployment docs.
Put the fleet under
one hub.
Air-gap deployment, license issuance, and white-glove integration. Nexus and Sentry are signed and shipped by our engineering team, with nothing to self-serve.