System Architecture

Tetrapus is a modular, real-time telemetry platform built in Rust. Data flows from edge SDKs through a QUIC transport layer into the ingestion pipeline, where it is validated, deduplicated, and persisted before being broadcast to GPU-accelerated visualization layers.

Data Flow

graph TD SDK["SDK Client"] -->|QUIC| ING["nerve_ingester"] ING --> VAL["validate()"] VAL --> DED["DedupeFilter"] DED --> WAL["WAL"] WAL --> BUS["EventBus"] BUS --> CH["ClickHouse"] BUS --> LS["LayerStore"] LS --> GPU["GPU Renderer"]

Crate Dependency Map

  • tetrapus-sdk — Client SDK (QUIC transport, codec, reconnect)
  • tetrapus-domain — Shared domain types, DomainCodec trait
  • tetrapus-config — YAML config loading, feature flags
  • nerve_ingester — QUIC listener, validation, dedup, WAL
  • visual-mapper — Scene layer mapping, GPU upload
  • control-bus — Bidirectional command channel, policy engine
  • tai-engine — Telemetric Action Intelligence pipeline
  • tetrapus-server — Headless server binary

Multi-Tenancy Architecture

Tetrapus splits the install into a public-facing gateway, one or more per-Org data planes, and a small control plane that owns the routing table. Data planes register with the control plane over mTLS and heartbeat periodically; the gateway pulls assignments and forwards by Org slug.

graph TD CLIENT["Client"] -->|TLS| GW["Gateway"] GW -->|cache miss| CP["Control Plane"] CP -->|select assignment| GW GW -->|reverse-proxy| DPA["Data Plane: acme<br/>region us-east-1"] GW -->|reverse-proxy| DPB["Data Plane: globex<br/>region us-east-1"] GW -->|reverse-proxy| DPC["Data Plane: initech<br/>region eu-west-1"] DPA -->|mTLS heartbeat| CP DPB -->|mTLS heartbeat| CP DPC -->|mTLS heartbeat| CP

Legend — for the components, CRDs, and operator workflows that build this topology, see /docs/multi-tenancy.

Deep Dives

Questions?

Reach out for help with integration, deployment, or custom domain codecs.