a CAST AI customer?
Half your CAST bill, fixed for 24 months.
Switch to PerfectScale for Kubernetes and pay half of your current CAST bill, fixed for 24 months. Our Forward Deployed Engineers run the migration with you, including standing and perfecting your autoscaler.
The terms, in plain language
Every current CAST AI customer qualifies, and your latest CAST invoice sets your price.
PerfectScale at half your current bill
We price the full product at 50% of what you pay today, including per-customer and network cost attribution.
That price is fixed for 24 months
It is not indexed to cluster growth or to savings. The number you sign is the number you pay through month 24.
We run your migration
That covers the parallel install, side-by-side validation, autoscaler cutover, and automation guardrails.
Leaving looks hard because you rely on CAST to keep your applications resilient, reliable, and available
no more daily OOMs and CPU throttling
You pay a percentage of your own savings
Tools like CAST are commonly priced on CPU-based fees. The larger your clusters are, the more you pay. Your team did the work of adopting the platform, tolerating the pod evictions, and re-architecting for spot. The vendor bill grew anyway. PerfectScale prices savings. Under this offer you pay half of what others charge you, fixed for two years. PerfectScale also handles commitments cutting your rate another 20 percent, that saving stays with you.
Your vendor holds the keys
Tools with custom node automation require cross-account cloud IAM permissions to create and terminate compute. That is standing write access to your cloud account, held by a third party, exercised continuously. Security teams accepted it because the savings were real. The same request would have a harder time passing review today. PerfectScale observes your clusters through read-only Kubernetes permissions: get, list, watch. The agent holds no cloud-provider credentials and cannot launch or terminate an instance. When you enable workload automation, changes stay inside Kubernetes RBAC. Your IAM boundary never moves.
Leaving looks hard because CAST owns your autoscaler
CAST replaced your node provisioning, which is the part every switching pitch leaves out. Karpenter or Cluster Autoscaler is gone, and CAST decides what compute exists in your cluster. Leaving means standing that layer back up, and that is real engineering work. PerfectScale managed cloud native autoscaler, validate it against production traffic, and stay until the cutover holds. The lock-in is the reason the migration help exists.
Still mid-contract?
We'll buy your contract, so you never pay two vendors for the same cluster.
Why teams switch from CAST to PerfectScale
CAST reports what your clusters cost. The question your CFO actually asks is what your per-customer cost, and that is a different product.
Put a customer name on your network bill.
Network is often 20 percent or more of Kubernetes spend, and it is the part nobody can explain. Cross-AZ replication, inter-cluster traffic, and NAT egress land as anonymous line items because there is no tag on a packet. PerfectScale traces every traffic path to the customer and feature behind it. When cross-AZ cost jumps 27 percent, you see which feature caused it and which account to have the conversation with, instead of averaging the bill across everyone.
Manages your commitments automatically.
CAST imports the Reserved Instances, Savings Plans, and CUDs you bought elsewhere and consumes them efficiently. It does not size or buy new ones. PerfectScale executes AWS Savings Plans, AWS Database Savings Plans, and Google Cloud CUD purchases continuously, with laddering, hourly re-evaluation, spend limits, and optional approvals. Rightsizing cuts the amount of compute you need, and commitments cut the price of what remains. You need both levers, and CAST only has one.
side by side
Where the two platforms part ways
| Capability | PerfectScale | CAST AI |
|---|---|---|
| Comparison | ||
| Default permissions | Read-only Kubernetes RBAC, no cloud credentials | Read-only Phase 1; node automation requires cross-account cloud IAM write access |
| Node provisioning | Your autoscaler stays in control | CAST provisions, drains, and terminates nodes |
| Workload rightsizing | PodFit, policy-driven, in-place on K8s 1.33+ | Workload Autoscaler, in-place supported |
| Automation safety | Immediate scale-up, gradual scale-down, automatic rollback of unschedulable changes | Gradual rollout; compaction model evicts pods and removes nodes |
| Cost attribution | Per customer and per feature, observed at runtime, network paths included | Cluster, namespace, workload, and label reporting |
| Commitment purchasing | Automated, risk-aware, with guardrails | Not offered; imports existing commitments only |
| Pricing model | Published flat per-vCPU; half your CAST bill for 24 months under this offer | Commonly savings-based plus CPU-based fees; terms vary |
| Human expertise | Forward Deployed Engineers and FinOps consultants | Support and customer success |
What the migration actually looks like
Switching optimization platforms sounds risky because one of them controls your nodes. So the plan never touches your running environment until the numbers prove out.
Day 1. Install PerfectScale on one of your clusters
One Helm command installs the PerfectScale. It is read-only, requires no cloud IAM changes, and returns its first cost and resilience analysis in about five minutes. CAST keeps running on other clusters, and nothing in your environment changes.
Weeks 1 to 2. Validate.
PerfectScale reports what it would do. Your FDE walks through the deltas with your platform team: projected savings per workload, resilience findings across 30+ risk types, and the first per-customer cost breakdown your team has seen for shared services.
Weeks 2 to 4. Cut over.
The FDE stands up Karpenter or re-tunes your managed autoscaler, moves node provisioning off CAST, and enables PodFit automation with your guardrails and maintenance windows. Then you revoke CAST's cloud credentials. From that point, no third party can create or terminate compute in your account. Your 24 months at half price start here.
After. Turn on the second lever.
PerfectScale for Commitments begins sizing and executing rate purchases on the compute you kept, with approval gates if you want them.
Teams that made the switch to PerfectScale
Kubernetes cost reduction at Rapyd
implementation effort
of toil removed at Luma Health
“PerfectScale cut 40% off our total EKS spend, and the automations handle what used to take our team 20 hours a month. Now we spend that time on reliability and performance instead of chasing cost metrics.”
Caio Cristo
Director of Infrastructure/SRE, Luma Health
PerfectScale allowed us to grow capacity without growing cost. We effectively absorbed 30% more usage for free.
Thomas Comtet, Senior Staff Engineer at SNCF
Frequently asked
questions
Do I qualify?
Yes, if you are a current CAST AI customer on a paid plan. Your most recent CAST invoice proves eligibility and sets your price.
How is the 50 percent calculated?
We take your average monthly CAST spend across your last three invoices and halve it. That becomes your fixed monthly PerfectScale price for the next 24 months.
What exactly do I get for half my CAST bill?
PerfectScale for Kubernetes in full: rightsizing automation, resilience analysis, per-customer and network cost attribution, multi-cluster and GPU visibility. FDE-led migration is included. PerfectScale for Commitments is available alongside it under its own terms, and your FDE will show you the numbers before you decide.
What if my clusters grow during the 24 months?
The price does not move. It is not indexed to vCPUs, savings, or usage, which is the point of leaving a more expensive fee model.
What happens at month 25?
You move to our published flat per-vCPU pricing, and you will see that figure during onboarding, two years before it applies. If you walk away instead, the free Community tier keeps covering up to 300 monthly vCPUs.
I am mid-contract with CAST. Should I wait for renewal?
No. Install read-only now, validate in parallel, and cut over when you are ready. Your 24 months at half price start at cutover, so the overlap period costs you nothing on our side.
Who does the migration work?
A DoiT Forward Deployed Engineer, in your environment, with your platform team. The heavy piece is re-establishing node provisioning through Karpenter or your managed autoscaler, because CAST currently owns that layer. That work is included.
What permissions do you need, and when?
Read-only Kubernetes RBAC on day one: get, list, watch. No cloud credentials, ever. If you enable workload automation later, changes run through Kubernetes RBAC and an admission webhook. The agent cannot launch or terminate an instance at any point.
If I add clusters from other business units to my PerfectScale tenant, will my price stay the same?
No, the 24 months at half price applies only to the clusters that were managed by Cast and covered under their contract. New clusters will still be priced at half of Cast's pricing, and they'll land at a similar price point ($x per monthly vCPU) to the clusters already onboarded.
Start with five read-only minutes.
The install touches nothing, and the first analysis lands the next day.