Hubble tells you what talked to what.aacyn tells you if it's breaking.

Side-by-side comparison of capabilities, setup complexity, and the metrics you can actually act on.

Get started in 30 seconds →

Already using Cilium? Deploy aacyn alongside it in 30 seconds — no migration needed.

aacyn vs Hubble / Cilium

Two approaches to Kubernetes observability: network flows versus service-level Golden Signals. aacyn also compares favorably to Pixie, Coroot, and Grafana Beyla — see the README for the full competitive matrix.

CapabilityaacynHubble
Setup time30 seconds (helm install)Hours (CNI migration)
Requires CNI changeNo — runs alongside any CNIYes — requires Cilium CNI
Golden Signals (RED metrics)Built-in — rate, errors, duration per serviceManual — network flows only
SLO trackingError budgets + burn rate alertsNo
Pre-configured alerts5 rules out of the boxRequires external tooling
Distributed tracingeBPF span generation + W3C traceparentNo
HTTP & gRPC visibilityMethod, path, status, service name — kernel-levelL3/L4 only (IP:port)
K8s pod enrichmentPod names, namespaces, deployments on topology edgesYes — via Cilium identity
OTLP ingest + exportBoth directions — bridge existing OTel instrumentationNo
ForwardersDatadog, Splunk, OTLPNo
Grafana pluginNative data source pluginYes — but flow logs only
No external database requiredYes — self-contained single binaryYes — in-memory flow store
SIMD-accelerated storeAVX-512 / NEON — 5M events/secNo
Open source license✓ Apache 2.0✓ Apache 2.0
DashboardCanvas 2D topology + golden signals + SLO gaugesService map + flow logs

Get started in 30 seconds.

Zero code changes. Zero CNI migration. Zero vendor lock-in.

Quickstart →

Already using Cilium? aacyn runs alongside any CNI — deploy it on your existing cluster with helm install and your Hubble data keeps flowing.