Home / Editions

Commercial or Sovereign

Same console, same agents, two very different postures. Choose the delivery model that matches who you answer to — a board, or a nation.

Side by side

The full comparison

Everything that differs between the two editions — and nothing else does. Feature parity is a design rule, not a roadmap item.

CommercialSaaS SovereignOn-prem / air-gap
Deployment Managed cloud, operated by the CFC team Your facility — on-premise or fully air-gapped
Data residency Regional cloud residency options In-country, in-facility — data never leaves
Raw logs Stay on your premises; only normalized telemetry egresses, encrypted end-to-end Never cross any boundary — collection, normalization and analysis all inside
Tenant isolation Logical — schema-per-tenant Physical — dedicated hardware, classified-workload capable
Updates Continuous delivery, standard SLA Signed offline update packages on your change schedule
Argus agents Full fleet — CORE, TITAN, PACT, TIAID — à la carte or suite Full fleet — identical capabilities, air-gap-safe model updates
Language EN / AR bilingual console, full RTL EN / AR bilingual console, full RTL
Ideal buyer Commercial MSSPs & enterprises Government, defense & sovereign SOCs
Sovereign edition

Built for buyers who answer to a nation

Sovereign isn't Commercial with a VPN. It's a delivery posture designed for national SOCs, ministries and defense — where "where is my data" is a constitutional question, not a support ticket.

SOV / 01

Air-gap by design

The full stack — console, bus, agents, storage — runs inside your perimeter. No callbacks, no telemetry, no "phone home." Updates arrive as signed offline packages you verify and apply.

SOV / 02

Whole-of-state view

One national console over many sub-entities — ministries, agencies, operators — each isolated, each self-service, with cross-entity oversight reserved for the roles the state authorizes.

SOV / 03

Procurement-ready

EN / AR bilingual with full RTL, framework-aligned reporting (ISO/IEC 27001:2022, ISO 27005, Jordan NCSC), and an audit trail built for government assessors.

Commercial edition

Built for MSSPs that sell outcomes

Multi-tenant from the first line of code: onboard customers fast, keep them strictly isolated, and let the agent fleet carry the alert load your analysts shouldn't.

COM / 01

Multi-tenant operations

Schema-per-tenant isolation with cross-tenant dashboards for your SOC leads — every customer sees only their world; you see all of yours.

COM / 02

Isolation tiers

Choose the data-isolation level per customer — same console, three tenancy models:

SILVER — schema-per-tenantGOLD — dedicated databasePLATINUM — dedicated cluster
COM / 03

SaaS without data anxiety

The Commercial edition keeps the Sovereign principle: raw logs stay on customer premises — only normalized telemetry crosses the boundary, encrypted end-to-end over mTLS.

The boundary

What crosses, what never does

Raw logs

Stay on premises — always, in both editions

Normalized telemetry

The only thing that egresses — Commercial edition, encrypted end-to-end

CFC console

In our cloud (Commercial) or entirely in yours (Sovereign)

In the Sovereign edition, nothing crosses any boundary at all — normalization, analysis and the console itself all run inside your perimeter. And AI is a source, not middleware: Argus agents ingest through the same connector contract as every other source — they never sit on the ingestion path.

Choose your posture

Not sure which edition fits?

Tell us who you answer to and what your data may never do — we'll recommend the edition and show you both in a live walkthrough.