“We were essentially able to reduce the cost of that cluster by about 75%. On AWS, DevZero demonstrated they could achieve significantly higher savings than we initially thought possible.”

Mihir Nair
Head of Architecture, Databahn
See workload health, network traffic and cost for every cluster on every cloud, with alerts in Slack, Microsoft Teams, Discord, email or webhooks.
Companies who slashed their Kubernetes
spend using DevZero
Use one way to monitor workload health across every cluster and cloud.
See traffic between your workloads and the external services they call.
Choose the problems you want to hear about and get an alert when they happen on any cluster.
Send alerts to Slack, Teams, Discord, email or any webhook.
Profile workloads to see CPU and memory percentiles and behavior patterns for every container. Each workload gets a clear classification.
See runtime metrics for Java, Node.js, Go, Rust, Python and other runtimes with no code changes. DevZero detects the language for you.
Trace traffic between workloads with eBPF and map service dependencies without sidecars.
Track startup behavior and health signals for every workload, and spot unhealthy apps before your users do.
See request rate, errors and latency for every container with no instrumentation.
Get instance type and size suggestions based on how you really use each node group.
Find node groups you can merge or compact, and see the estimated savings before you act.
See what every workload costs over any time period, and roll costs up by team or department.
Split cross-AZ, internet egress and NAT gateway spend, and see which workloads drive it.
Price persistent volumes per storage class and attribute them to the workloads that use them.
Reflect your Savings Plans, Reserved Instances and Committed Use Discounts, so you see what you actually pay.
Where each approach is stronger, and what DevZero adds out of the box.
“We were essentially able to reduce the cost of that cluster by about 75%. On AWS, DevZero demonstrated they could achieve significantly higher savings than we initially thought possible.”

Mihir Nair
Head of Architecture, Databahn
Questions from platform engineers and SREs evaluating Kubernetes monitoring.
It monitors workloads such as Pods, Deployments and StatefulSets, plus nodes, storage and networking. Node and container metrics come from a small agent on each node.
DevZero reads information about your workloads, nodes and storage. The install also grants some write permissions, for example for its own settings. You can review the full list in the install files before you approve it.
Cost Threshold (30-day cluster cost reaches a USD amount), Cost Anomaly (the latest daily cost is well above earlier days), Cluster Disconnected (no report for a set number of hours), Application Restart, Out of Memory and CPU Throttle. Rules run every 15 minutes by default.
Slack, Microsoft Teams, Discord, email and generic webhooks. By default only Critical alerts are sent to these channels, and you can change that minimum severity. Alerts that fall inside quiet hours are skipped, not sent later.
No. A threshold is set once per alert rule and applies to every cluster connected to your team. Cost alerts are still raised separately for each cluster.
Prometheus with Alertmanager is the better fit if you need alert rules on any custom metric, PromQL or PagerDuty and Opsgenie receivers, and DevZero does not replace it for those. DevZero adds cluster cost alerts in USD, cost by department and ready-made workload restart, OOM kill and CPU throttle alerts, with no Prometheus, exporters or Alertmanager to run. It does not collect pod logs or application traces.
These are default requests, not measured usage. The main component requests 200m CPU and 2Gi memory per copy, with 2 copies by default, and each node also runs a small agent.
Yes, on nodes labelled nvidia.com/gpu.present=true it collects NVIDIA GPU metrics. This is monitoring only.
A department groups workloads by namespaces, workload kinds, labels, annotations or name patterns, and none of these depend on the cloud provider. A shared workload counts in full for every department that claims it, or is split evenly in the apportioned view.
Install DevZero in each cluster and set up cost, workload restart, OOM kill and CPU throttle alerts.