Solutions Comparison

Choose the right products for your infrastructure.

Quox consists of five complementary products. This page helps you understand what each one does and which combination you need.

At a Glance

What Each Product Does

QuoxCORE — The Brain

QuoxCORE is the self-hosted control plane you interact with. It provides:

• AI chat interface powered by Claude (Anthropic)
• 16 specialist AI agents with automatic delegation
• 6-layer persistent memory (episodic, semantic, entity, working set, preference, observation)
• Organization hierarchy (orgs, divisions, teams) with RBAC
• 25+ dashboard views for monitoring, files, workflows, and more
• AOCL 11-layer audit protocol and AEE audit envelopes
• Integration layer that calls out to QuoxAgent and QuoxBastion APIs

You always need QuoxCORE. It's the central platform. Everything else is optional infrastructure that QuoxCORE can connect to.

QuoxAgent — Per-Host Daemon

QuoxAgent is a lightweight Go binary deployed on every host you want to monitor:

• Pushes real-time metrics (CPU, RAM, disk, network) every 30 seconds
• Accepts remote command execution with full audit trail
• Tracks AI agent sessions (Universal Agent Monitor)
• Self-registers with QuoxCORE's Collector service
• DEFCON safety levels gate which commands require approval

Deploy QuoxAgent when you want real-time visibility into individual hosts and need AI-assisted command execution per host.

QuoxBastion — Fleet Command from the Jump Host

QuoxBastion runs on your bastion/jump host and manages the entire fleet via SSH:

• Maintains a registry of every host (IP, FQDN, groups, tags, metadata)
• Executes commands across individual hosts, groups, or the entire fleet in parallel
• Uses your existing SSH setup — no agent installation on managed hosts
• Token-based API with command sanitisation and strict SSH host key verification
• Full-screen TUI for interactive fleet operations

Deploy QuoxBastion when you have an existing bastion host and want API-driven fleet management without deploying an agent binary to every host.

Qluster — The Fleet Control Plane

Qluster is a multi-instance control plane that sits above a fleet of QuoxCORE boxes. It does not replace QuoxCORE — it governs many of them together:

• Fleet health at a glance: live CPU, memory, and disk gauges for every box (the datacenter view)
• A NOC status wall for the whole estate
• Cross-instance drift detection (version, config, WARD-verify)
• Secure enrollment (Ed25519-signed, scoped, org-bound)
• Centralised encrypted backup pull
• Governed delegation — task any box's agent from the console, always with human approval, while the box applies its own policy and keeps its sovereignty
• Colonel Qluster, a fleet meta-agent that answers questions across the whole fleet
• QLOGS — a tamper-evident, cryptographically verifiable record (AEE/AOCL/VOLT/WARD) of everything the fleet does

Deploy Qluster when you run more than one QuoxCORE box — split by task (research, security, dev, compliance), by client, or for blast-radius isolation — and want one console over all of them without collapsing their independence.

QuoxBox — Governed Mac Actuator

QuoxBox is a different kind of product from the four above: instead of managing Linux/server infrastructure, it turns a Mac into a governed digital employee that can do the work that has no API — log into no-API web portals, send iMessages, drive Mac-only apps:

• Default-deny actuation — nothing runs on the Mac unless policy explicitly allows it
• Human-in-the-loop approval on every high-risk action
• Effect verification — never trusts the backend's own success flag
• Tamper-evident, hash-chained evidence trail an auditor would accept
• Governed workflows — named, parametric, replayable multi-step recipes
• Runs on-prem on a Mac mini you already own; credentials and screen never leave your hardware

Deploy QuoxBox when your business depends on no-API portals, Mac-only apps, or iMessage/SMS comms, and you need an agent that can touch them under human oversight with an audit trail — not just automate servers. See the QuoxBox promo page for the full picture; the natural-language chat-to-Mac agent is on the roadmap, the governed gateway and evidence chain are built and tested today.

Comparison: QuoxAgent vs QuoxBastion

Both products enable remote command execution. Here's when to use each:

Rule of thumb:

• Use QuoxAgent for per-host monitoring and AI session awareness
• Use QuoxBastion for fleet-wide operations and host registry management
• Use both for complete infrastructure visibility and control

Deployment Combinations

Minimal: QuoxCORE Only

Good for teams that use Quox as an AI assistant without infrastructure integration.

QuoxCORE (dashboard, AI chat, memory, workflows)

Standard: QuoxCORE + QuoxAgent

Good for teams managing a fleet of servers that want real-time metrics and AI-assisted operations.

QuoxCORE
└── QuoxAgent on each host (heartbeat → Collector port 9848)
    ├── nw-web-01:9847
    ├── nw-db-01:9847
    └── nw-hv-01:9847

Full Stack: All Three Products

Complete infrastructure management. QuoxBastion is the canonical host registry; QuoxAgent provides per-host telemetry; QuoxCORE orchestrates everything.

QuoxCORE Dashboard
├── QuoxBastion (bastion host, port 9850)
│   ├── SSH → nw-web-01  (fleet-wide commands)
│   ├── SSH → nw-db-01
│   └── SSH → nw-hv-01
└── QuoxAgent Collector (port 9848)
    ├── Heartbeat ← nw-web-01:9847  (real-time metrics)
    ├── Heartbeat ← nw-db-01:9847
    └── Heartbeat ← nw-hv-01:9847

Who Needs What

Next Steps

• QuoxCORE — Full product overview
• QuoxAgent — Per-host agent documentation
• QuoxBastion — Fleet management documentation
• Qluster — Multi-instance control plane
• QuoxBox — Governed Mac actuator
• Quickstart — Get QuoxCORE running in minutes