zoorikctl
RecommendedSets up the cloud permissions too.
$ brew tap getzoorik/tap $ brew trust getzoorik/tap $ brew install zoorikctl
Or: curl -fsSL https://get.zoorik.com/macos | sh
Built for Azure and AWS
Supported on AKS and EKS
Kubernetes cost optimization
Available in Coral in AWS Marketplace (opens in a new tab) and Coral in Microsoft Marketplace (opens in a new tab)
Compatible with your native
- Karpenter
- NAP
- Cluster Autoscaler
- KEDA
Coral
40–50%off AKS and EKS cost
Coral and Amoeba together
20–30%off your overall cloud bill
Estimated ranges, not a promise.
What is Coral?
Coral is a Kubernetes cost optimization platform for Azure Kubernetes Service (AKS) and Amazon Elastic Kubernetes Service (EKS). It continuously finds and removes the capacity your clusters don’t need, while your workloads keep serving. It sizes each container’s CPU and memory requests to what it really uses, and empties spare nodes one at a time so your autoscaler can remove them.
Coral helps platform and engineering teams cut AKS and EKS cost with no application code changes. It monitors every workload and node, recommends right sizes and spare nodes with the saving, and applies them safely: pods resize in place or restart one at a time within their PodDisruptionBudgets, and nodes drain one at a time. Coral works alongside native Kubernetes autoscaling: the Horizontal Pod Autoscaler, KEDA, Karpenter, Node Auto Provisioning (NAP) and the Cluster Autoscaler.
With Coral, you see where your Kubernetes spend goes, which capacity sits unused, and what each change saves at your cloud’s list price. Pod sizing starts when you switch on “Automatically optimize” for a policy or a workload. Node optimization is on from install, and you choose the node pools it works on.
What Coral does?
Monitoring
Cost tracked always, every action logged.Recommendations
Right sizes, spare nodes and the saving.Workload optimization
CPU and memory requests sized to real use.Node optimization
Spare nodes drained one at a time; never creates machines.
Runs on
- AKS
- EKS
How it works
Connect a cluster
Connect the cluster with one command. Coral reads six nodes and seventy-seven workloads, with no code changes.
Read from the cluster6nodes77 workloads across them
- Code changes
- none
See the waste
Every node, workload and volume, priced. The gap between what you hold and what runs: 22 CPU held, and 3.09 CPU carrying the real work.
Carrying the real work3.09CPUof 22 CPU held
- Requested
- 15.53 CPU
Optimize
Capacity moves to match demand and keeps moving. In this cluster $608.76 a month on 22 CPU becomes $194.88 on 16.
Bill at the optimum$194.88/modown from $608.76 /mo
- Removed
- 67.99%
Example: Zoorik’s own AKS cluster, not a customer result.
Install your way
Open sourceHelm
For teams on Helm, Argo CD or Flux.
$ helm install coral-agent \ oci://ghcr. io/ getzoorik/ charts/ coral-agent \ --namespace default \ --set controlPlaneUrl= <control plane origin> \ --set connectToken. value= <connect token>
Coral is in early access — book a demo (opens in a new tab) for a console account.
Terraform
Cloud permissions as code.
# AKS source = "getzoorik/zoorik-coral/azurerm" # EKS source = "getzoorik/zoorik-coral/aws"
Then install the agent with Helm.
Find your own number
One line in your cloud console. One PDF report with your estimated saving at list price.
Estimate your savingTalk to the builders
Thirty minutes with the people who build Coral.
Book a demo (opens in a new tab)Or write to founders@zoorik.com