a10y is composed of three layers: UI, Core, and Data. Each component is independently deployable and communicates via NATS.
The first interfaces operators use. Each Data Layer component ships with its own built-in dashboard — no custom UI needed to get started.
| OpenObserve :5080 | Logs, metrics, traces dashboard. SQL & PromQL queries, custom dashboards, alerting. |
| Keep :3001 | Alert management console. Correlated alerts, workflow editor, 110+ integrations. |
| Qdrant :6333/dashboard | Vector DB explorer. Collections, embeddings, similarity search. |
| NATS :8222 | Messaging monitor. Connections, JetStream streams, message rates. |
See Deploy for access URLs and credentials.
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.
Lightweight portal with two responsibilities:
Live network topology view from active-inventory. Visualizes devices, links, and interfaces. Shows impact scope during incidents.
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.
| Image | ghcr.io/autonomously-io/aether-ide |
| Connects to | active-inventory (topology), links to all Data Layer UIs |
| Roadmap | AI chat, causal chain visualization, incident timeline |
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.
| Image | ghcr.io/autonomously-io/aether-term |
| Connects to | correlation-engine |
| Use case | CLI investigation, scripted queries, headless environments |
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.
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:
| Image | ghcr.io/autonomously-io/correlation-engine |
| Default model | claude-sonnet-4-20250514 |
| Connects to | OpenObserve, Keep, Qdrant, NATS, active-inventory |
| Secrets | ANTHROPIC_API_KEY |
| OODA phase | Orient → Decide (+ Verify feedback) |
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.
| Image | ghcr.io/autonomously-io/active-inventory |
| Connects to | NATS (topology events) |
| Use case | Topology queries, impact analysis, blast radius |
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.
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.
| Image | public.ecr.aws/zinclabs/openobserve |
| Storage | 200 Gi (default), Parquet on local/S3 |
| Query | SQL, PromQL |
| OODA phase | Observe + Verify |
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.
| Image | timberio/vector:0.41.1-alpine |
| Inputs | Syslog TCP, Vector protocol |
| Transforms | parse_free5gc, parse_perfsonar (extensible via VRL) |
| Output | OpenObserve HTTP sink |
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).
| Image | keep-api + keep-ui |
| Integrations | 110+ bidirectional (Datadog, Grafana, PagerDuty, ...) |
| Workflows | Declarative YAML (GitHub Actions style) |
| OODA phase | Orient (correlation) + Act (remediation workflows) |
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.
| Image | qdrant/qdrant |
| Storage | 20 Gi (default) |
| Collection | incidents (default) |
| Use case | Incident similarity, RAG retrieval, anomaly pattern matching |
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.
| Image | nats:2-alpine |
| Features | JetStream (streaming), KV store, monitoring (:8222) |
| Streams | Alert events, topology changes, action results |
| OODA phase | All — event bus connecting the entire loop |