Real-time automated
pod rightsizing

DevZero is a Kubernetes optimization platform that applies CPU and memory limits in-place using CRIU checkpoint/restore. No restarts. No dropped connections. No eviction.
Stateless
Stateful
Background
Waste
node-1 · us-east-1a
api-gateway
control-plane
dashboard-api
webhook-server
mtls-proxy
audit-log
node-2 · us-east-1b
zxporter
dakr-op
node-operator
workload-watcher
admission-ctrl
cluster-discovery
node-3 · us-east-1c
ingestion-pipeline
metrics-collector
timeseries-db
recs-store
grpc-gateway
savings-calc
node-4 · us-east-1d
recommendation-engine
policy-engine
p99-analyzer
resource-fitter
scheduler
notifications
Default (Over-allocated)DevZero Rightsized
$2,840Before / Month
$840After / Month
67%
CPU Waste Eliminated
0
Pod Evictions

Companies who slashed their Kubernetes
spend
using DevZero

DATABAHN
Starburst
Fi
Outerbounds
Codilas
personality pool
Onnitech
OpenObserve
Parsimo
Dentira
DATABAHN
Starburst
Fi
Outerbounds
Codilas
personality pool
Onnitech
OpenObserve
Parsimo
Dentira

In-place resource updatesNo eviction, no disruption

VPA rightsizes by evicting and rescheduling pods, dropping active connections and breaking stateful workloads. DevZero uses CRIU checkpoint/restore to resize container limits in-place: the process is frozen, limits are updated, and execution resumes with no eviction and no connection loss.

CostCurrently Showing
$1,200.55

32% of workloads (72)

account for ~80% of total cost

CPU
4%request utilization

13% of workloads (30)

account for ~80% of CPU usage

Memory
19%request utilization

26% of workloads (57)

account for ~80% of memory usage

GPU
0%request utilization

50% of workloads (2)

account for ~80% of GPU usage

Cost Distribution

ml--apac-...

$24.07

ml--earth-...

$24.05

ml--emea-...

$23.97

ml--mercu...

$21.08

ml--apac-...

$20.97

ml--apac-...

$20.90

qis--apac...

$20.66

qis--previ...

$20.56

qis--previ...

$19.62

qis--nar-st...

$20.55

qis--regre...

$20.55

gossip--us...

$20.36

gossip--int...

$20.40

qis--nar-pr...

$17.62

yahoo-otel...

$16.15

qis--regre...

$17.46

gossip--u...

$15.08

node-loca...

$14.94

qis--eme...

$13.24

avengers...

$13.15

qis--apa...

$11.70

ml--nar-e...

$11.38

gossip--...

$10.19

gossip--...

$10.18

ml--eme...

$9.81

mi--eme...

$9.67

mi--nar-...

$9.67

gossip--...

$9.41

gossip-...

$9.41

gossip--...

$9.40

gossip--...

$9.39

ml--merc...

$9.39

ml--nar-...

$9.07

qis--apa...

$8.73

dz-prom...

$7.95

s1-agent

$7.97

ais--apa...

$7.57

WORKLOAD
CPU
MEMORY
GPU
BASED COST
TYPE
REPLICAS
avengers--...

0.18 / 13.04 cores

23.1 / 37.36 GiB

$13.1262
Deployment
4 pods
Optimize
csp-report...

0.01 / 1.56 cores

0.13 / 4.98 GiB

$1.6424
Deployment
1 pod
Optimize
gossip--as...

0.09 / 5.66 cores

2.12 / 59.96 GiB

$4.7762
StatefulSet
1 pod
Optimize
gossip--as...

0.15 / 4.66 cores

6.27 / 59.51 GiB

$9.3903
StatefulSet
1 pod
Optimize
gossip--in...

0.26 / 11.31 cores

11.64 / 119.84 GiB

$20.3560
StatefulSet
2 pods
Optimize
gossip--in...

0.14 / 5.66 cores

1.9 / 59.96 GiB

$10.1692
StatefulSet
1 pod
Optimize

Percentile-based forecastingby workload, not per cluster

Metrics are analyzed using percentile windows (P50, P95, P99) over configurable time ranges. Bursty batch jobs get wide limits; steady-state API servers get tight P95-aligned limits. A confidence score prevents under-provisioning below your SLO threshold.

Real-time cost visibilityper namespace, per workload

DevZero tracks optimization coverage across your workloads in real time, showing active policies, pending recommendations, and applied changes. Engineering leaders can see exactly what has been optimized, what is pending, and where savings are being generated.

Optimization StatusiView Details ›
Workload Coverage93%
190/203 optimized13 remaining
Workload Policies:5HA workloads+4
Recommendations:12741 applied86 failed
Live Node Coverage (5min)100%

474/474 nodes managed

Node Policies:4+4
Events:0

Why DevZero over native Kubernetes tools

Native Kubernetes autoscalers were designed for availability, not cost efficiency. DevZero is built specifically to eliminate waste without compromising stability.

Runningcontainer
Active
FreezeCRIU
Active
Resizecgroup
Resumecontainer

freeze window: <200ms · zero connection drop · zero eviction

In-place resizing via CRIU

DevZero applies resource limit changes to the running container using CRIU checkpointing. The process freezes for under 200ms, limits are rewritten, and execution resumes with no eviction and no scheduler round-trip.

CPU request savings · post-inference

api-server
−66%
worker
−54%
ingest
−71%
auth-grpc
−59%

avg confidence 0.93 · 14-day P95 window

Workload-aware forecasting per workload class

Forecasting models are trained per workload class, not per namespace or cluster. Bursty batch jobs get wide limits; steady-state API servers get tight P95-aligned limits. A confidence score prevents under-provisioning below your configured SLO threshold.

Anomaly detected · api-server-7f6d9XGBoost inference

CPU throttle_pct=0.82 · rec=680m · conf=0.94

GitHub PR opened · helm-values patchAdvisory mode

cpu.request: 2000m → 680m · projected $2.84/hr

Applied in-place · CRIU <200msDone

saved 1.32 vCPU · billing export updated

Full audit trail + advisory mode

Every recommendation DevZero generates is logged with timestamp, confidence score, before/after limits, and projected saving. Advisory mode raises a GitHub PR or Slack notification before touching production, your platform team stays in the loop.

Built for platform engineers

The controls your team actually needs, not a dashboard that requires a PhD to interpret.

cgroup v2 · live
CPU throttle
78%
Mem PSI stall
43ms
OOM events
0
sub-second
prometheus · 15s avg
CPU usage
38%
Mem usage
51%
Throttle visible
averaged out

P99 latency spike · api-server-7f6d9

throttle_pct=0.78 · caught in 180ms window

Detected

DevZero reads CPU throttle rates, memory pressure (PSI), and OOM events directly from cgroup v2, not 15-second Prometheus averages. Sub-second anomalies that cause P99 latency spikes are visible and actionable.

EKS
841
pods managed
GKE
519
pods managed
AKS
302
pods managed
On-prem
178
pods managed
Single tenant1,840
pods · 4 clusters
$41kMonthly Savings
3Cloud Providers
4Clusters
1Tenant

One DevZero tenant manages rightsizing across EKS, GKE, AKS, and on-prem clusters. Monthly savings and optimization metrics are aggregated in a single view across all cloud providers.

DEVZERO

cpu.request: 2000m → 680m · conf=0.94
Triggered

SLACK · #PLATFORM-RIGHTSIZING

Advisory mode · saves $2.84/hr
Posted

GITHUB · HELM-VALUES PATCH

resources.requests.cpu: "680m"
PR open

Advisory mode surfaces recommendations where your team already works. GitHub PR integration proposes changes before anything touches production. Slack integration posts to the on-call channel, keeping the right people informed.

What our customers say

Databahn logo

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

Mihir Nair

Head of Architecture, Databahn

Frequently asked questions

Technical questions from platform engineers who've evaluated DevZero.

Most clusters are overprovisioned.Let's prove yours is.

Run a free assessment to identify overprovisioned workloads, idle capacity, and your potential savings, in minutes.

Optimize now