Skip to content

Deployment Overview & Architecture ​

RUSEON Core is an ultra-portable, single-binary video infrastructure engine with zero external runtime dependencies. Whether deploying on edge ARM64 gateways, standalone Linux servers, or scalable container clusters, RUSEON provides predictable resource consumption and minimal CPU footprint.


Deployment Methods Comparison ​

Deployment MethodBest Suited ForKey AdvantagesConsiderations
Docker ComposeHomelab, single-server production, edge nodesDeclarative configuration, automated restart, isolated volumesRequires Docker daemon
Standalone DockerKubernetes, Nomad, container clustersImmutable images, standardized CI/CD deploymentManual port & volume configuration
Systemd BinaryBare-metal servers, embedded Linux, edge SBCsAbsolute lowest latency, direct kernel I/O access, 0 overheadRequires manual systemd service configuration
Direct ExposureIsolated appliances, direct IP setupsZero reverse-proxy latency, simplified WebRTC ICERequires opening ports directly
Reverse ProxyMulti-service hosts, enterprise DMZAutomated Let's Encrypt TLS, domain routing, WAFMust configure WebSocket & WHEP headers properly

Persistent Storage Architecture ​

RUSEON Core maintains strict separation of storage concerns across three directories:

  1. State Store (/app/data/db): Embedded BadgerDB v4 database storing camera configurations, users, JWT secrets, and archive metadata. Must be placed on fast SSD/NVMe storage.
  2. Video Archive (/app/recordings): Hierarchical fMP4 video files ({camera}/{YYYY}/{MM}/{DD}/{HH}/*.mp4). Can be mounted on high-capacity HDDs, SATA SSDs, or NAS/SAN arrays.
  3. Backup Directory (/app/backups): Scheduled daily BadgerDB snapshots for disaster recovery.

Deployment Guide Sections ​

Released under the MIT License.