Commitment Manager

Our primary use case for Zesty  is automated AWS  cost optimization across compute, storage, and cloud commitments. We were spending significant engineering hours manually reviewing Reserved Instance coverage and Savings Plans every quarter, which was not scalable. Zesty  took over that entire Commitment Management workflow and separately handles dynamic rightsizing for our Kubernetes  clusters through Compass. The core value for us is eliminating manual FinOps overhead while keeping infrastructure costs aligned with actual usage.

The best features that Zesty offers include the Commitment Manager automated RI and Savings Plan management, the Hyber-scale technology inside Compass, and the ZestyDisk persistent volume auto-scaling. What makes them exceptional is that they are not just recommending actions; they are executing them continuously without requiring human sign-off every time. The AI-driven demand forecasting is genuinely impressive, as it analyzes historical and real-time patterns and adjusts resources before a spike hits, not after.

Out of those features, the one that saves me the most time or money is the Commitment Manager, which significantly streamlines our process. Before Zesty, our FinOps analyst was spending close to ten to twelve hours a week on commitment review, RI purchase, and coverage analysis. That is now essentially zero. Our DevOps engineers also have reclaimed time they were spending on Kubernetes  resource tuning and storage incident response. Collectively, I estimate Zesty freed up somewhere around fifteen engineering hours per week across the team, which we have redirected into product work. It is one of those tools that pays for itself in recovered bandwidth alone before you even count the direct dollar savings.

One feature that I do not think gets enough attention is Zesty's Spot Instance confidence layer within Compass. Using Spot Instances for Kubernetes nodes used to feel risky because a sudden interruption could impact availability. Zesty's combination of Hyber-scale and advanced automation gave us real confidence to run a larger fraction of our nodes on Spot, which provides substantial additional savings on top of the rightsizing. We went from approximately twenty percent of Spot coverage to over sixty percent safely.

Zesty has positively impacted our organization across engineering, finance, and leadership. Engineering is happier because they are not babysitting infrastructure anymore. Finance now gets clean monthly reports showing optimized cloud spend trends rather than unpredictable bills. From a leadership perspective, it has allowed us to scale our cloud infrastructure significantly. We have grown our workload by over forty percent in the past year without a proportional increase in cloud spend. That kind of efficiency is hard to put a price on. Zesty has genuinely changed how our team thinks about cloud cost from a reactive manual chore to an automated, continuous background process. It is one of the clearest examples I have seen of an AI-driven platform delivering on its promise in a measurable way. If you are running significant workloads on AWS  with Kubernetes and you are not using a tool to this effect, you are almost certainly leaving meaningful money on the table every single month.

The biggest gap in Zesty's offering is multi-cloud coverage. We run a small portion of workloads on Google Cloud , and Zesty simply does not support GCP  meaningfully right now. That means we still have a manual optimization process for that environment, which creates some inconsistency in our FinOps workflow. A unified experience across AWS, Azure , and GCP would make Zesty a near perfect solution for our team.

The documentation has improved over time but it could still go deeper on edge cases. For example, what happens when Compass interacts with custom Kubernetes admission controllers or how Commitment Manager behaves during account consolidation scenarios. These are not deal-breakers, but when you are troubleshooting something unexpected at eleven PM, more detailed runbooks would save considerable back and forth with support.

I have been working with Zesty for a little over two years now, primarily in a cloud infrastructure and FinOps capacity.

In terms of specific outcomes, we have seen roughly a thirty-five to forty percent reduction in our overall AWS infrastructure costs since fully deploying Zesty's suite. Kubernetes costs specifically dropped by close to fifty percent once Compass was fully tuned. Storage costs went down by around twenty-five percent thanks to ZestyDisk. As mentioned, we reclaimed about fifteen engineering hours per week. The ROI calculation was very clear within the first ninety days. Zesty's fees were well covered by the savings generated.

My advice for others looking into using Zesty is to start with Commitment Manager if you are AWS heavy and not already maximizing Savings Plan coverage. The ROI is almost immediate with very little setup friction. Then layer in Compass if you are running Kubernetes because that is where the biggest cost reduction potential typically lives. Do not try to boil the ocean on day one; get comfortable with one module, see the savings, and then expand. Zesty's team is also really willing to work with you on onboarding, so lean on them. I would rate this product nine out of ten.

We predominantly use Zesty  to manage our spend in AWS , specifically around reserving instances for our compute workload. Our workload is dynamic, and it would be cumbersome and difficult for us to maintain and manage the reserved instance profiles ourselves. We leverage Zesty  to programmatically adjust our reserved instance purchases and sell off RI contracts as they are no longer needed.

Zesty reduces our monthly bill. On average, between 85% and 95% percent of our environment is covered by some form of reserved instance, and each of these agreements reduces the spend by 30% to 35% percent. This results in a material impact on the bill and allows us to allocate savings to other areas.

The turnkey aspect of Zesty is very valuable. I set it up, spend around 15 minutes granting access, and from there, it operates automatically. Zesty manages the workload, and their pricing is structured in a way that incentivizes them to save us more money.

There are different resource types that we would like to leverage and get reserved instances for, such as RDS  instances. Currently, no mechanism within Zesty allows this, but this may be due to AWS  limitations. Another point is that Zesty needs to react to any changes AWS makes, but they have been proactive in their communication regarding material impacts.

It's probably been about five years since I began using Zesty, back when they were Cloudvisor.

I have never had any issues or experienced a bug. Occasionally, I might need help understanding the UI to ensure I'm interpreting the data correctly, however, my customer care representative is always there to help. I've never experienced stability or outage issues.

I would rate scalability a ten out of ten. The necessary scaling is transparent to me, and I don't observe any issues.

The customer support has been great. There has been some turnover due to turmoil in Israel, where Zesty is headquartered. However, they transition well across account representatives. In the few instances I've needed support, they have been available despite the time zone difference.

Positive

The setup is straightforward. They walk you through the process, and it's as simple as copying and pasting into the AWS console. Once it's set up, you're done.

We see a return on investment every month.

Their pricing is brilliant. It is a percentage of what they save us by using reserved instances. If they save us $25,000, they might charge five percent of that, which is work we wouldn't do on our own. It's a no-brainer.

I advise that while it may seem like managing reserved instances is something you can do on your own unless you are extremely disciplined, you won't achieve the same consistency and regularity as Zesty would. Not using Zesty leaves money on the table.

I'd rate the solution ten out of ten. 

We use the solution for savings plans, reserved instances, and automation. We customize the reserved instances of savings plans depending on the account type.

What I like about Zesty is that it's basically being completely hands-off. It does what's expected of it, and you don't have to worry about cost or cost savings. You just automate that part of the cloud, and the buying and selling of all the little businesses and savings plans will be done for you.

One of the things Zesty recently launched was Windows reserved instances because they needed support until recently. One of the reasons we decided to onboard Zesty was that it started supporting Windows instances.

Zesty helped reduce our cloud cost without needing a FinOps team to constantly look at cloud costs. Managing all of that is completely automated now.

I would like to get RDS-reserved instances that I could buy and sell, but that's a limitation on AWS.

I have been working with Zesty in my current company for about three months, but I worked with it for a year in a previous company.

We haven’t faced any issues with the solution’s stability.

Zesty is a scalable solution. Around four people have access to the dashboard in our organization.

The solution’s initial setup is straightforward. To deploy the solution, you need to add an AIM role on the accounts you need to onboard. We enabled SSO on the portal. The SSO is just a question of negotiating the service and sharing the certificates and private keys with them, which was very easy. The initial setup took around five minutes.

We got around 48% cost savings with Zesty.

The solution’s pricing is reasonable.

Before choosing Zesty, we evaluated other tools like Cloudability. We tried other solutions, but Zesty turned out to be the best because of its insurance plan. If Zesty makes a mistake and over provisions the commitment, we don't pay their bill until the commitment is credited to us.

The way we're using it is completely hands-off. We just trust that they do the automation to buy the reserved instances and the same instance for us. The solution has other features like the storage explorer, which can save you money on new storage. It also has the Zesty disk, but I never use those because I never had the use case for them.

The solution's AI functionality is really easy to use and automatic. Since it's all automated, we don't see what the AI is doing. We just keep the savings at the end of the month and pay the bill. It is not difficult to maintain the solution. I would recommend the solution to other users because it is very easy to use.

The solution is easy to use and onboard, and its support team is really good.

Overall, I rate the solution a nine out of ten.