Sedai Kubernetes Optimization
See how Sedai autonomously optimizes K8s — across EKS, AKS, GKE, and more.
KO THE CLOUD TO ENTER OUR GIVEAWAY
WIN KEYBOARD!HPA scales pods, Karpenter provisions nodes, but neither knows whether your workloads are actually sized correctly. Sedai continuously right-sizes pod requests and tunes scaling targets based on real workload behavior, so your autoscalers are always working from accurate inputs.
Pod Interceptor
Optimize without fighting CI/CD
Autoscalers like HPA and Karpenter are reactive by design. The inputs they scale from are usually wrong before scaling even begins.
Estimates go stale, but HPA still scales from whatever they say.
Vertical and horizontal autoscaling conflict at runtime, so most teams disable VPA in production or limit it to off-hours, leaving right-sizing unaddressed.
Karpenter bins pods onto nodes based on declared requests, so inflated requests mean larger nodes, lower density, and higher spend regardless of actual utilization.
Sedai is an autonomous Kubernetes optimization platform that continuously right-sizes pod resource requests and tunes HPA scaling targets based on real workload behavior and SLOs. Unlike native autoscalers that scale from static or stale inputs, Sedai learns from live production data to eliminate resource waste, resolve HPA-VPA conflicts, and improve Karpenter bin-packing — without manual tuning or pod restarts.
Sedai adds an intelligence layer at both the pod and node level, filling the gaps that leave native autoscalers guessing.
Set the Right HPA Target, Not Just a Guess
Sedai analyzes workload behavior and SLOs to autonomously set the optimal HPA target, balancing pod size against replica count for the most cost-effective configuration.
Get Vertical and Horizontal Scaling at the Same Time
Native VPA and HPA conflict when both act on CPU or memory. Sedai's vertical scaling works alongside HPA, safely adjusting pod requests and limits in small increments — conflict-free.
Help Karpenter Pack Nodes More Efficiently
Oversized pods waste node capacity. Sedai right-sizes pods first so Karpenter bin-packs onto fewer, cheaper nodes, and recommends instance types based on usage and pricing.
Consolidate Nodes, With or Without Migrating to Karpenter
Sedai Scheduler packs pods densely on any cluster. Without Karpenter, Sedai Compactor also clears stranded pods so your autoscaler can remove empty nodes.
Move to Karpenter Without the Risk
Already decided Karpenter's the right call? The Migration Assistant automates the cutover from EKS Managed Node Groups, node pool by node pool — with a pre-flight compatibility check and automatic rollback built in.
“We’ve gone from what used to be automated, deterministic workflows to autonomous, with Sedai. The human element is indispensable, and it always will be. But more and more engineering toil is being done by AI, so as humans, we can move up the value chain. That’s how we can deliver what our customers expect of us.”

Suresh Sangiah
SVP of Engineering // Palo Alto Networks
| Without Sedai | Sedai |
|---|---|
HPA utilization targets are set manually and rarely revisited | Sedai continuously determines and tunes the optimal HPA target based on live workload behavior |
VPA and HPA conflict on the same resource metrics | Sedai's vertical scaling works alongside HPA simultaneously, without the native conflict |
Oversized pods force Karpenter to provision larger, more expensive nodes | Right-sized pods let Karpenter pack workloads onto fewer nodes at lower cost |
Node autoscalers pick from the full instance catalog without guidance | Sedai recommends a targeted instance type list so autoscalers make more cost-effective selections |
Scaling decisions are based on infrastructure metrics alone | Sedai factors in application performance and SLOs, ensuring scaling doesn't compromise reliability |
Consolidation without Karpenter is manual, and migrating to Karpenter is risky | Continuous consolidation on any autoscaler, plus a safe, automated Karpenter migration |
Sedai continuously right-sizes pod resource requests and tunes HPA scaling targets based on real workload behavior. It works alongside your existing HPA, VPA, Karpenter, and Cluster Autoscaler configurations without replacing them.
Yes. Native VPA and HPA conflict when both act on CPU or memory. Sedai's vertical scaling works alongside HPA, adjusting pod requests and limits in small increments without the native conflict.
Sedai right-sizes pods so Karpenter provisions for real demand, recommends a focused list of instance types, and Sedai Scheduler improves placement within Karpenter’s footprint. For EKS teams still on Cluster Autoscaler, the Karpenter Migration Assistant automates a safe move.
Rightsizing doesn’t force restarts. With Pod Interceptor, changes apply as pods are created during normal lifecycle events. Two capabilities do move pods, always within your guardrails: onboarding a workload to Sedai Scheduler takes one rolling restart, and Sedai Compactor evicts stranded pods through the standard eviction API, which enforces your PodDisruptionBudgets.
Rightsizing and HPA tuning support EKS, AKS, GKE, OpenShift, Rancher, and self-managed clusters. Sedai Scheduler and Sedai Compactor are available on EKS, GKE, and AKS, and the Karpenter Migration Assistant on EKS. Sedai works with any combination of HPA, VPA, Karpenter, and Cluster Autoscaler.
Not yet. Sedai detects KEDA-managed workloads so it never makes conflicting changes, but workloads scaled only by KEDA are excluded from optimization until full KEDA support is available.