Shadow mode first
See every consolidation the engine would make — which nodes, which pods, how much saved — before any of it is enabled.
Node Consolidation
An autonomous bin-packing engine that plans safe consolidations inside your cluster — and refuses to execute any plan that doesn't actually save you money.
6 nodes · avg 38% utilized
Consolidation only saves money if nothing breaks and the math holds. Both are checked before a single pod moves.
Real usage vs. current layout — find the cheaper packing your workloads fit into.
PDBs, affinity, topology, and volumes respected at planning time, not discovered at execution.
The never-lose-money gate: if a plan doesn't actually save money, it doesn't run.
A settle audit after execution confirms the savings actually landed.
The OptOps node engine stays stock-Karpenter-compatible. Your NodePools are real Karpenter NodePools — not a proprietary controller you'd have to rip out under pressure.
And on Google Cloud, you get the same engine — including the GCP provider upstream Karpenter never shipped. EKS and GKE, one brain.
$ helm uninstall optops
release "optops" uninstalled
$ kubectl get nodepools
NAME NODES READY
default 12 True
▶ still Karpenter. still autoscaling.
See every consolidation the engine would make — which nodes, which pods, how much saved — before any of it is enabled.
Aggressiveness, cooldowns, and disruption budgets are tunable per cluster from the dashboard — while every decision still executes inside your cluster.
One click to the mathematically cheapest layout for the entire cluster — with every safety gate still in the loop.
Consolidation pairs with container live migration — that's what makes the moves disruption-free.
Book a demo and we'll show you how many nodes your workloads actually need — and how OptOps gets there without an incident.
Book a Demo