Console · QUANTOM DOM · AEGIS-Q architecture

Two desks. One fleet.

The Protection console is for people who own endpoints. The SOC view is for people who hunt. AEGIS-Q does not make this marketing host a login: there is no standing vendor account to sign into here. Activation is accountless and one-time. Deploy documentation goes to waitlisted operators.

Deploy & docs Request a tenant

Protection console

Operate the fleet.

Inventory

Hosts, build digests, last pack version, isolation mode, one-time TRELYAN activation state, and whether the agent has an outstanding evidence queue. A dark host is a state, not a green lie.

Policy

On-access posture, scan windows, quarantine dual-control, kill-switch sensitivity, and tamper rules. Changes in managed mode are dual-controlled and themselves evidence events.

Packs

Definition and policy packs are signed for air-gap ferry as well as connected update. The console shows what was signed, by which key, and which hosts have applied it.

Exceptions

Exclusions are scoped, expiry-bound, and noisy on purpose. Permanent global excludes require a second operator. That is the point.

SOC view

Hunt without a trophy wall.

Detections, kill-switch trips, tamper events, Algorand nullifiers, and QRL Merkle receipts land in one timeline. The SOC view does not invent MITRE coverage heat maps we have not measured. It shows what the agent actually emitted, and whether the nullifier and the Merkle inclusion agreed on the digest.

Console preview · illustrative, not a live tenant

Hosts reporting

—

Waitlist fleets only

Kill-switch (24h)

—

No public telemetry

Nullifier + Merkle

—

Receipts after GA

Pack lag > 7d

—

Air-gap expected

Tamper events

—

Dual-control review

Quarantine open

—

Restore is two-party

Access

There is no hidden /login.

This website is the public trust surface. A production console will live on a separate host when the first design-partner fleets exist. Operator identity there is not a substitute for the accountless one-time TRELYAN activation on the endpoint. Until then, the working action is the waitlist and the deploy brief.