Zero-instrumentation monitoring
One Helm command, 30 seconds to deploy. No code changes, no external databases, and no cloud account. Your telemetry data never leaves your network. Apache 2.0.
A monitoring tool that watches your servers from the operating system level — no SDKs to install, no code changes, no cloud account required.
See every request, error, and slow response across your services. aacyn uses eBPF to observe traffic at the kernel level — no agents or SDK installs needed.
Runs on your hardware — a mini PC, a server rack, or a Docker container. Your telemetry data never leaves your network. No cloud vendor lock-in.
No per-host fees. No per-GB surcharges. No surprise invoices. Apache 2.0 licensed — use it, modify it, ship it. All features included, no tiers.
One command installs the eBPF probes on every node and the dashboard aggregator. Works alongside any CNI — no migration needed.
Most monitoring tools parse JSON on every incoming request, which limits throughput. aacyn accepts a compact binary format that skips parsing entirely — the bytes from your HTTP request go straight into storage.
The result: over 5 million events per second on a single box. That's 16× faster than JSON-only ingestion.
aacyn stores data in a format optimized for analytics — instead of reading entire rows, it reads only the columns you need. Combined with modern CPU acceleration, this makes searching, filtering, and aggregating nearly instant.
aacyn runs on your hardware and stores everything locally. There is no cloud backend, no telemetry, and no phoning home. Your data stays on your machines.
Everything included. No tiers, no locked features, no enterprise upsells.
RED metrics (rate, errors, duration) per service, computed automatically from kernel probes. No configuration required.
Automatic span generation with W3C traceparent propagation. Trace waterfall view for every request.
Auto-discovered service dependency map from kernel-level TCP connection tracking. Pod names, namespaces, deployments enriched via K8s API.
Error budgets and burn rate alerts per service. Google SRE workbook model. Multi-window burn rate detection.
Bridge existing OpenTelemetry instrumentation. Accept OTLP traces and export to any OTLP-compatible collector.
Push metrics to Datadog (Metrics API v2), Splunk (HEC), or any OTLP collector. Use your existing observability stack.
Kernel-level gRPC protocol parsing — service name, method, status code — without sidecars or proxies.
Native Grafana data source plugin. Query aacyn topology and golden signals from your existing Grafana dashboards.
5 rules out of the box: latency spikes, error rate thresholds, connection failures, SLO burn rate, and ring buffer drops.
Apache 2.0. No tiers, no limits, no phone calls from sales.