AegisOS Documentation

Complete guides for deploying, configuring, and operating AegisOS in edge and air-gapped environments.

Camera Setup Guide

AegisOS supports RTSP, ONVIF, and direct USB camera connections. The system has been tested with up to 4 cameras producing 8 simultaneous streams (main + sub per camera).

Supported Protocols

  • RTSP over TCP/UDP (primary recommended)
  • ONVIF Profile S compliant devices
  • USB Video Class (UVC) cameras
  • CSI (MIPI) cameras via Jetson native interface

Adding a Camera

Camera sources are defined in the aegis-config.yaml file under the cameras section:

cameras:
  - id: cam-01
    name: "North Perimeter"
    protocol: rtsp
    url: rtsp://192.168.1.100:554/stream1
    resolution: 1920x1080
    fps: 15
    detection: true

Resolution and Performance

For optimal AI inference performance on Jetson AGX Orin, we recommend 1080p at 15 FPS per camera. Higher resolutions are supported but will reduce the number of concurrent streams.

NVR Configuration

AegisOS includes a built-in Network Video Recorder (NVR) that stores all footage locally. No footage ever leaves the device.

Storage Configuration

nvr:
  storage_path: /data/aegis/recordings
  retention_days: 30
  max_storage_gb: 500
  compression: hammerio
  segment_duration: 300  # 5-minute segments

Recording Modes

  • Continuous: Records all camera feeds 24/7
  • Motion-triggered: Records only when motion or detection events occur
  • Scheduled: Records during configured time windows
  • Event-only: Captures clips around AI detection events

Storage Management

When storage reaches the configured limit, AegisOS automatically rotates older recordings using a FIFO policy. Detection event clips are prioritized and retained longer than continuous footage.

Alert Pipeline Configuration

The alert pipeline processes AI detection events and dispatches notifications through configurable channels.

Pipeline Architecture

Detection events flow through a multi-stage pipeline: Detection → Filtering → Deduplication → Escalation → Dispatch

Alert Configuration

alerts:
  min_confidence: 0.75
  cooldown_seconds: 30
  zones:
    - name: "Entry Gate"
      polygon: [[0,0],[640,0],[640,480],[0,480]]
      classes: [person, vehicle]
  dispatch:
    - type: local_log
      path: /data/aegis/alerts.jsonl
    - type: syslog
      host: 127.0.0.1
      port: 514

Detection Classes

  • Person detection with tracking
  • Vehicle classification (car, truck, military)
  • Object detection (backpack, package, weapon)
  • Perimeter breach (tripwire and zone crossing)

HammerIO Integration for Archival

HammerIO is the compression engine used by AegisOS for efficient video archival. It runs as a dedicated microservice within the AegisOS stack.

Configuration

hammerio:
  enabled: true
  compression_level: balanced  # fast | balanced | max
  codec: h265
  archive_path: /data/aegis/archive
  realtime: true

Compression Modes

  • Fast: Minimal compression, lowest CPU usage
  • Balanced: Good compression ratio with moderate CPU (recommended)
  • Max: Maximum compression for long-term archival

HammerIO processes completed NVR segments asynchronously, compressing and moving them to the archive path without impacting live recording performance.

Air-Gap Deployment Checklist

AegisOS is designed for fully air-gapped operation. Follow this checklist to ensure a complete disconnected deployment.

Pre-Deployment

  • Verify all AegisOS container images are loaded locally
  • Confirm AI model weights are present on disk
  • Pre-configure all camera sources in aegis-config.yaml
  • Set NVR storage paths to local or attached storage
  • Disable all network interfaces except camera VLAN (if applicable)

Network Verification

# Verify zero outbound connections
sudo iptables -A OUTPUT -j LOG --log-prefix "AEGIS_OUTBOUND: "
sudo iptables -A OUTPUT -o eth0 -j DROP

# Allow only camera subnet
sudo iptables -I OUTPUT -d 192.168.1.0/24 -j ACCEPT

Operational Checklist

  • All 16 microservices reporting healthy status
  • Camera feeds visible in local dashboard
  • AI detection active and producing events
  • NVR recording and HammerIO compression running
  • Alert pipeline tested with synthetic event
  • No DNS resolution attempts in system logs

AriaOS Integration (Optional)

If AriaOS is deployed on the same device or local network, configure the governance event feed:

integrations:
  ariaos:
    enabled: true
    endpoint: unix:///var/run/ariaos/events.sock
    events: [detection, alert, system]