# akvorado/akvorado

Flow collector, enricher and visualizer

Repository: https://github.com/akvorado/akvorado
Canonical: https://ross.abutalabs.com/products/akvorado
Homepage: https://demo.akvorado.net
Language: Go
License: AGPL-3.0
License Family: copyleft
Topics: collector, netflow, sflow, ipfix, clickhouse, kafka
Last push: 2026-08-24T04:59:04+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 97, longevity 100
- inputs: {"age_days": 1527, "days_push": 9, "days_rel": 21, "gap_med": 28.0, "n_releases_24m": 17}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2321, forks 178 (observed 2026-08-28T04:06:37.137669+00:00)

## What it is
Akvorado is a self-hosted network flow collector, enricher, and visualizer that ingests NetFlow/IPFIX and sFlow data, enriches it with SNMP interface names and IP geolocation, and stores it in ClickHouse. It provides a web console with timeseries and Sankey graphs for exploring network traffic, plus a Grafana plugin.

## Use cases
- collect and analyze netflow traffic from routers
- visualize network traffic with sankey diagrams
- self-hosted network flow monitoring
- enrich ipfix flows with interface names and geolocation
- store network flow data in clickhouse for analysis
- monitor isp or datacenter traffic patterns
- export netflow data to grafana dashboards

## When to choose
- you need to collect and analyze NetFlow/IPFIX or sFlow exports from network equipment
- you want a self-hosted alternative to commercial flow analyzers like Kentik or ElastiFlow
- you need flow enrichment with SNMP interface names and IP geolocation
- you want timeseries and Sankey visualizations of traffic without building your own stack
- you run an ISP, datacenter, or large network and need per-flow visibility

## When to avoid
- your network devices do not export NetFlow, IPFIX, or sFlow
- you only need simple SNMP-based bandwidth graphs rather than per-flow analysis
- you cannot operate the ClickHouse and Kafka dependencies
- you need a lightweight agent-based solution rather than a centralized collector
- you require a permissive license - Akvorado is AGPLv3

## Facets
- artifact type: service
- maturity: active
- function: monitoring, analytics, data-visualization, streaming, search-engine
- domain: networking, monitoring, analytics, self-hosted
- platform: self-hosted, go
- tags: netflow, ipfix, sflow, clickhouse, kafka, flow-collector, network-observability, snmp, geoip-enrichment, grafana-plugin, traffic-analysis, sankey-diagrams, devops, docker, web-server, linux

## Member repositories
- akvorado/akvorado (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:37.137669+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:38:46.658486+00:00, confidence not recorded.
  - readme: https://github.com/akvorado/akvorado (fetched 2026-08-28T04:06:37.137669+00:00, sha 1f12693b9c83)
  - homepage: https://demo.akvorado.net (fetched 2026-08-29T10:18:53.119808+00:00, sha 70aafd1ee63d)
- Data as of 2026-08-30T08:39:29.467469+00:00.