Components

a10y is composed of three layers: UI, Core, and Data. Each component is independently deployable and communicates via NATS.

Data Layer Dashboards

The first interfaces operators use. Each Data Layer component ships with its own built-in dashboard — no custom UI needed to get started.

OpenObserve :5080Logs, metrics, traces dashboard. SQL & PromQL queries, custom dashboards, alerting.
Keep :3001Alert management console. Correlated alerts, workflow editor, 110+ integrations.
Qdrant :6333/dashboardVector DB explorer. Collections, embeddings, similarity search.
NATS :8222Messaging monitor. Connections, JetStream streams, message rates.

See Deploy for access URLs and credentials.

UI Layer

aether-ide is the unified entry point for a10y. It provides a network topology view and links to all Data Layer dashboards — no need to remember individual ports.

aether-ide

Custom :8080

Lightweight portal with two responsibilities:

Network Topology

Live network topology view from active-inventory. Visualizes devices, links, and interfaces. Shows impact scope during incidents.

Service Portal

Links to all Data Layer dashboards from a single page. Each service's built-in UI does the heavy lifting — aether-ide just ties them together.

Imageghcr.io/autonomously-io/aether-ide
Connects toactive-inventory (topology), links to all Data Layer UIs
RoadmapAI chat, causal chain visualization, incident timeline

aether-term

Custom :3000

Terminal-based interface for operators who prefer CLI workflows. Query the AI engine, inspect alerts, trigger actions — all from the command line. Suitable for SSH-only environments and automation scripts.

Imageghcr.io/autonomously-io/aether-term
Connects tocorrelation-engine
Use caseCLI investigation, scripted queries, headless environments

Core Layer

The brain of a10y. The LLM engine performs causal reasoning by combining statistical AI and language models. The active inventory maintains a live graph of network topology, feeding context into every decision.

correlation-engine

Custom :8000

Multi-source correlation engine — the cognitive core. Ingests alerts from Keep, searches historical patterns in Qdrant, queries topology from active-inventory, and reasons about root causes using a dual AI approach:

Statistical AI

  • Time-series anomaly detection
  • Topology-aware correlation
  • Predictive failure models

LLM

  • Causal reasoning over unstructured data
  • RAG over runbooks & documentation
  • Natural language interaction
Imageghcr.io/autonomously-io/correlation-engine
Default modelclaude-sonnet-4-20250514
Connects toOpenObserve, Keep, Qdrant, NATS, active-inventory
SecretsANTHROPIC_API_KEY
OODA phaseOrient → Decide (+ Verify feedback)

active-inventory

Custom :8080

Live network topology graph. Discovers and tracks devices, links, interfaces, and services. Provides topological context to correlation-engine — enabling questions like "what else is affected by this fiber cut?" and blast radius estimation for remediation actions.

Imageghcr.io/autonomously-io/active-inventory
Connects toNATS (topology events)
Use caseTopology queries, impact analysis, blast radius

Data Layer

Proven open source infrastructure for telemetry storage, alert management, vector search, data pipelines, and messaging. Each component maps to a phase of the OODA loop.

OpenObserve

OSS :5080 Observe

Unified observability platform for logs, metrics, and traces. Rust-based, 140x lower storage cost than Elasticsearch. Stores all raw telemetry and provides SQL + PromQL query interfaces. Also serves as the verification layer — re-queried after remediation to confirm recovery.

Imagepublic.ecr.aws/zinclabs/openobserve
Storage200 Gi (default), Parquet on local/S3
QuerySQL, PromQL
OODA phaseObserve + Verify

Vector

OSS :9000 :6514 Observe

High-performance data pipeline. Ingests logs via syslog (TCP :9000) and Vector protocol (:6514), parses and enriches with VRL transforms, then routes to OpenObserve. Handles free5GC, perfSONAR, and network device logs with source-specific transforms.

Imagetimberio/vector:0.41.1-alpine
InputsSyslog TCP, Vector protocol
Transformsparse_free5gc, parse_perfsonar (extensible via VRL)
OutputOpenObserve HTTP sink

Keep

OSS :8080 Orient + Act

AIOps platform for alert lifecycle management. Aggregates alerts from 110+ sources, deduplicates, correlates related alerts, and executes remediation via YAML-based declarative workflows. Serves as both the alert correlation layer (Orient) and the action execution layer (Act).

Imagekeep-api + keep-ui
Integrations110+ bidirectional (Datadog, Grafana, PagerDuty, ...)
WorkflowsDeclarative YAML (GitHub Actions style)
OODA phaseOrient (correlation) + Act (remediation workflows)

Qdrant

OSS :6333 Orient

Vector database for similarity search. Stores embeddings of past incidents, runbooks, network states, and documentation. Enables "have we seen this pattern before?" queries — the memory of the system. Powers RAG for correlation-engine.

Imageqdrant/qdrant
Storage20 Gi (default)
Collectionincidents (default)
Use caseIncident similarity, RAG retrieval, anomaly pattern matching

NATS

OSS :4222 All

Cloud-native messaging backbone. Connects all components via pub/sub and request/reply. JetStream provides persistent streaming for alert events and topology changes. Sub-millisecond latency, under 20 MB RAM — the nervous system of a10y.

Imagenats:2-alpine
FeaturesJetStream (streaming), KV store, monitoring (:8222)
StreamsAlert events, topology changes, action results
OODA phaseAll — event bus connecting the entire loop