Launching today

CloudKnife
Cut your cloud bill, not your performance
95 followers
Cut your cloud bill, not your performance
95 followers
Cloud cost tools tell you what to cut, then leave the work to you. CloudKnife handles it from A to Z. AI agents learn what every Azure resource is, how it’s really used and what it’s allowed to become. A deterministic core checks every recommendation against hard rules, so your SAP VM only gets SAP-certified options. You approve, CloudKnife executes. Your cloud stays lean and your team gets its time back for innovation.







Exciting! Any insights in realistic cost savings?
@diederik_van_damme1 Thanks, Diederik! As a concrete example, one enterprise Azure deployment saved 27% in three months, with 85% of recommendations executed. Results depend on how optimized the environment already is and its workload constraints, but that gives you a real reference point. Our focus is on savings that actually get implemented and show up on the bill.
@jonas_cloudknife Interesting, thanks for the numbers. Will try it out!
Keeping approval with the team while handling the execution sounds like a useful balance. Good luck today, Jonas, Gilles and Thomas!
From an after-hours project to a full-time business. Congrats to all three of you! Hope the launch brings some useful conversations.
@marianna_tymchuk Thanks for the support Marianna!!
Congratulations
@madalina_barbu Thanks for the support!
the SAP VM only getting SAP-certified options is the detail that got me, every cost tool we tried just says "downsize this" wtih zero context
when CloudKnife makes a change and something breaks a day later, is there a one click rollback or do you revert by hand??? and is AWS coming or Azure only for now???
@thamibenjelloun That SAP detail is exactly why we go deep on context before recommending a change. “Downsize this” isn’t much help if it ignores what’s running on the VM 😅
We handle both execution and reverting if needed, that’s part of the automation. The goal is to make the analysis thorough enough upfront, including constraints like SAP certification, to avoid needing a rollback in the first place.
Azure only for now, with AWS planned!
Keeping workload rules separate from the agent's recommendation makes sense. Being able to see which rule ruled out a cheaper option would make the approval much easier to judge.
@oleksii_sekundant Exactly. “Here’s the cheaper option” is only half the story. Showing why an option was ruled out, whether that’s SAP certification or another workload constraint, gives you the context to judge the recommendation before approving it.