Hero Section

Sovereign Deployment

Sovereign & Air-Gap

Sovereign means you control the infrastructure, the keys, and the evidence. Stella Ops runs without mandatory external dependencies and produces verifiable proof for every release decision.

What Sovereign-Ready Means

What sovereign-ready means

Self-hosted control plane

No forced SaaS dependency. Deploy the entire suite on your infrastructure — on-premises, private cloud, or air-gapped network.

Air-gap / offline-first operations

Vulnerability feeds and verification data move via signed bundles. Core decisions stay offline; nothing leaves the network unless you manually opt in to telemetry.

Bring your own keys

Customer controls trust anchors. Pluggable crypto profiles support your signing and verification infrastructure.

Regional crypto profiles

Plugin architecture for compliance-driven cryptography. FIPS-aligned, GOST R 34.10, SM2/SM3, or eIDAS-compatible signing (validation depends on your key provider).

Deterministic replay

Same inputs produce identical outputs. Auditors can verify decisions offline months later with frozen feeds and manifests.

Exportable evidence

Decision Capsules package evidence for audit — not scattered across logs. Portable, verifiable, independent of Stella infrastructure.

Auditable core (source-available)

The suite is source-available (BUSL-1.1). Evidence formats and verification tooling are open source (Apache-2.0). Auditors can verify decisions independently — no vendor lock-in for trust.

Local intel aggregator

Run your own CVE + VEX intelligence service. Aggregate sources, dedupe, snapshot, and sign — all inside your boundary.

Crypto Profiles

Crypto profiles

Stella supports pluggable cryptographic profiles for regional compliance and organizational requirements.

FIPSFederal Information Processing Standards - U.S. government cryptographic standards for secure systems · GOSTRussian national cryptographic standards (GOST R 34.10/34.11) required for government systems · SM2Chinese national public key cryptography standard (part of ShangMi suite) required for regulated industries · eIDASElectronic IDentification, Authentication and trust Services - EU regulation for electronic signatures and trust services

ProfileAlgorithmsUse case
defaultECDSA P-256, SHA-256Standard deployments
fips-140-3ECDSA P-384, SHA-384US federal / FedRAMP
gostGOSTRussian national cryptographic standards (GOST R 34.10/34.11) required for government systems R 34.10-2012, StreebogCIS region compliance
smSM2Chinese national public key cryptography standard (part of ShangMi suite) required for regulated industries, SM3Chinese standards
eidasRSA-PSS, ECDSA (QES)eIDASElectronic IDentification, Authentication and trust Services - EU regulation for electronic signatures and trust services-compatible signatures
Deployment Modes

Deployment modes

Connected mode

Standard deployment with optional feed updates from public sources.

  • Live vulnerability feed sync (NVDNational Vulnerability Database - the U.S. government repository of standards-based vulnerability data, OSVOpen Source Vulnerabilities - a distributed vulnerability database for open source projects, vendor advisories)
  • Opt-in telemetry for fleet analytics (disabled by default)
  • Automated signature verification

Air-gapped mode

Fully isolated deployment for regulated or sensitive environments with no outbound traffic unless telemetry is manually enabled.

  • Signed feed bundles imported via sneakernet or DMZ relay
  • Zero external network dependencies
  • Customer-controlled update cadence
Air-gapped data flow: feeds and evidence move via signed bundles
Air-Gapped Data FlowExternal NetworkNVD/OSVAdvisoriesFeed BundleSigned TransferTransferAir-Gapped NetworkStella OpsGate DecisionCapsuleEvidence stays internal
Minimal Offline Workflow

Offline operations

Import signed feed bundle

Terminal
$ stella feed import vuln-feed-2025-01.bundle --verify
Verifying bundle signature... OK
Signer: CN=Stella Feed Signing Key (customer-owned)
Feed version: 2025-01-15T00:00:00Z
Feed imported successfully
CVEs added: 847 | Updated: 2,341 | Total: 234,892

Run decisions offline

Terminal
$ stella gate decision --env prod --offline
Using local feed snapshot: 2025-01-15T00:00:00Z
Analyzing artifact: sha256:a1b2c3d4...
Reachable CVEs: 8 (of 312 in dependencies)
Policy: production-strict v2.1.0
Gate passed — all reachable CVEs below threshold

Export for external audit

Terminal
$ stella capsule export --bundle audit-pack.zip --include-feeds
Packaging Decision Capsule...
Including: SBOM, reachability graph, VEX state, policy, approvals
Including: Feed snapshot (frozen at decision time)
Signing with: GOST R 34.10-2012 (sovereign profile)
Audit pack exported to audit-pack.zip
Bundle can be verified and replayed on any Stella installation
Who This Is For

Who this is for

Defence & government

Classified networks requiring national crypto profiles and zero external dependencies.

Critical infrastructure

Energy, transport, and telecom operators who must prove every deployment decision to regulators.

Financial institutions

Banks and insurers needing FIPS-aligned crypto (validation depends on your key provider) with auditable, deterministic release gates.

Healthcare & pharma

Organisations handling sensitive data that require offline-first operation and signed evidence chains.

Bottom CTA

Ready for sovereign release control?

Evidence & Audit · All features · Offline Kit