Skip to main contentSkip to main content
Back

Caelex Sentinel

Autonomous compliance
evidence collection.

A lightweight, cryptographically-sealed compliance data extraction layer that transforms raw operational telemetry into verified, regulation-mapped evidence — without ever exposing sensitive data to the outside world.

2 TB
raw data per day
12 KB
evidence transmitted
147,832
sealed packets
0
inbound ports

The Problem

Compliance in space is manual, unverifiable, and a snapshot of one day per year.

01

Manual

A human copies numbers from Mission Control into a spreadsheet, emails it to a compliance officer, who manually enters it into whatever tool they use. This happens quarterly if they're diligent. Annually if they're not.

02

Unverifiable

A regulator asks "What was your orbital altitude on March 15?" — the operator provides a number. Was it real? Was it current? Did anyone modify it? There is no chain of custody, no cryptographic proof, no independent verification.

03

A Snapshot

Annual audits capture one moment in time. What happened the other 364 days? An operator could be non-compliant for months — a decaying orbit, a failed thruster, an unreported cyber incident — and nobody would know until the next audit cycle.

Sentinel eliminates all three problems simultaneously.

Compliance Extraction

2 TB12 KB

99.9999994% of operational data stays inside your network. Only structured, signed compliance evidence is transmitted.

Architecture

Your data never leaves your perimeter until it's compliance evidence.

sentinel-topology.txt
Source Systems
Mission Control
SIEM / SOC
Ground Station
Document Store
READ-ONLY
Caelex Sentinel
Collect
4 collector modules
Extract
Regulatory rule engine
Seal
SHA-256 + Ed25519
Transmit
mTLS 1.3 → HTTPS
outbound only · HTTPS 443 · no inbound · no SSH · no tunnels
Ingest API
Verify signature, validate hash chain, store
Cross-Verification
Space-Track · ESA DISCOS · LeoLabs · CelesTrak
Evidence Engine
119 articles · 51 NIS2 req · 10 jurisdictions

Collector Modules

Four specialized collectors. Each reads everything. Transmits almost nothing.

/01

Orbit & Debris

Mission Control System, Flight Dynamics, Conjunction Assessment

CCSDS MO · REST API · PostgreSQL · TDM

Data Point
Regulation
Frequency
Orbital altitude
Art. 68
15 min
Remaining fuel mass
Art. 70
1 hour
Thruster status
Art. 66
15 min
CA events (Pc > 1e-4)
Art. 102
Real-time
Estimated orbital lifetime
Art. 68
Daily
Deorbit capability
Art. 72
Daily
800 MB/day4 KB/day1 : 200,000
/02

Cybersecurity

SIEM (Splunk, Sentinel, QRadar), EDR, Vulnerability Scanner, Patch Management

REST API · Syslog · STIX/TAXII · SNMP

Data Point
Regulation
Frequency
Security incidents (30d)
NIS2 Art. 21
Real-time
MTTD / MTTR
NIS2 Art. 23
Daily
Critical vulns (unpatched)
NIS2 Art. 21(2)(e)
Hourly
MFA adoption rate
NIS2 Art. 21(2)(j)
Daily
Backup verification
NIS2 Art. 21(2)(c)
Daily
Encryption status
NIS2 Art. 21(2)(h)
Daily
1.2 TB/day6 KB/day1 : 200,000,000
/03

Ground Station

Ground Station Management (ATOS, Kongsberg), Antenna Control, Network Management

REST API · SNMP · Syslog · DB Read

Data Point
Regulation
Frequency
Contact success rate
Art. 64
Per pass
Ground station availability
Art. 64
Daily
Command uplink success
Art. 66
Daily
Time since last contact
Art. 64
Real-time
Signal margin (dB)
ITU RR
Per pass
Frequency coordination
Art. 70
Monthly
50 GB/day1.5 KB/day1 : 33,000,000
/04

Document Watch

Network Drives, SharePoint, Confluence, Certificate Stores

inotify · SharePoint API · REST API

Data Point
Regulation
Frequency
Certificate expiry dates
Art. 7
Event
Insurance policy renewal
Art. 8
Event
Export license status
ITAR/EAR
Event
Training certifications
NIS2 Art. 21(2)(g)
Event
Audit report metadata
Art. 29
Event
Policy document hashes
NIS2 Art. 21
Event
Variable0.5 KB/eventDocs never leave

Cryptographic Integrity

Every packet is sealed. Tampering is mathematically impossible.

Every evidence packet contains a SHA-256 content hash, an Ed25519 signature from the agent's private key, and a reference to the previous packet's hash — creating an unbroken, tamper-evident chain.

Modify any packet — the chain breaks. Delete any packet — the gap is detected. Insert a fake — the signature fails. The regulator can verify the entire history is authentic, unmodified, and complete.

#147830
hash: a1b2
#147831
hash: c3d4
#147832
hash: e5f6
#147833
hash: g7h8
evidence_packet.json
{
  "packet_id": "sp_2026031514320744_58421_orbit",
  "sentinel_id": "snt_a7f3d09e-4b21-4c89-9e67",
  "data": {
    "altitude_km": 548.317,
    "remaining_fuel_pct": 57.66,
    "thruster_status": "NOMINAL",
    "estimated_lifetime_yr": 4.2
  },
  "regulation_mapping": [
    { "ref": "art_68", "status": "COMPLIANT" },
    { "ref": "art_70", "status": "COMPLIANT" },
    { "ref": "art_72", "status": "COMPLIANT" }
  ],
  "integrity": {
    "content_hash": "sha256:a7f3d09e...",
    "previous_hash": "sha256:059669e4...",
    "chain_position": 147832,
    "signature": "ed25519:MGUCMQCxN8T7..."
  }
}

Trust Score

Not all evidence is equal.

A Verified Score of 61% built from Level 5–6 evidence is vastly more meaningful than a Declared Score of 82% built from Level 0 self-assessment. Sentinel creates Level 5 and 6 evidence — the highest achievable trust.

60.98Agent + Cross-Verification
50.92Agent-Collected
40.90Platform-Generated
30.88Public API Only
20.75Operator Push
10.65Manual Upload
00.50Self-Assessment

Deployment

One command. 512 MB. Zero inbound ports.

terminal
$ docker run -d \
--name caelex-sentinel \
--restart unless-stopped \
--memory 512m --cpus 0.5 \
-e SENTINEL_TOKEN=snt_xxxxxxxxxxxx \
-e COLLECTORS=orbit,cyber,ground,documents \
registry.caelex.eu/sentinel:1.4.2
CPU
0.5 cores
RAM
512 MB
Disk
1 GB + 10 GB buffer
Network
Outbound 443 only

Read-only access

Never writes to source systems. Never modifies operational data. Read-only database connections and API calls only.

No inbound ports

Zero attack surface from the internet. No SSH, no reverse shells, no tunnels. Outbound HTTPS only, certificate-pinned.

Rootless container

Runs as unprivileged user. Immutable filesystem. Container isolation prevents lateral movement. Build from source if you want.

Deploy autonomous compliance infrastructure.

Start with a free compliance assessment. Then deploy Sentinel to automate evidence collection across the EU Space Act, NIS2, and 10 national space laws.