We didn't miss
the network.
eBPF taps the kernel. Every byte tagged source-AZ → destination-AZ, priced by zone. The 30% of the cloud bill nobody owned, now visible.
Query your network
like a database.
Write CEL. Filter on any field. Group by any dimension. Same syntax you already know from Kubernetes admission webhooks.
| Source → Destination | Port | Bytes | Cost / mo |
|---|---|---|---|
acheckout-apiborders-db | 5432 | 1.8 TB | $486 |
banalytics-workercfeature-store | 8080 | 2.4 TB | $362 |
binventory-svccsearch-indexer | 9200 | 920 GB | $184 |
afrontend-apibml-inference | 50051 | 640 GB | $128 |
The hidden 30% · cross-AZ + egress
Samebytes.9×theprice.
The packet doesn't know it crossed a zone. AWS does, and bills you $0.01/GB. Push it to the internet and that's $0.09/GB — same byte, 9× the cost. Below: every TB of traffic in one cluster, priced.
Where the
bytes go.
Four services concentrating most of their egress on a single cross-AZ destination. We surface them. You decide.
Read-only. Kubeadapt does not write to your cluster — apply via your own GitOps or kubectl pipeline.
Architecture · how we see
eBPF. Not sidecars.
Service meshes give you network visibility at the cost of injecting a proxy into every pod. We hook the kernel once per node and watch every packet flow through it. Same data. 200× less weight.
12 pods × ~200 MB sidecar
1 agent. Kernel hook.
Requires kubeadapt-daemonset deployed inside the cluster. AWS pricing integration is in active rollout — cost figures shown for AWS today; GCP and Azure pricing land next quarter.
Stop paying for unused capacity.
Connect your first cluster in 5 minutes. The first 100 vCPU is on us, forever. Above it, the rate tiers from $1.99 down to $0.60 — same features, every plan.