How it works
Five steps. You choose the fixes. Your team makes every change.
Request & access
01
Request the assessment.
Tell us which clouds you use and roughly how your accounts are set up. No credentials in the form. Before we send the list, we send short written terms: the 90-day window, how the fee works, the billing evidence request, and how disagreements are resolved (which may include arbitration). Agreeing costs nothing and commits you to nothing.
02
Create read-only access.
We send a guide with the exact permission list. You create a role in AWS, a service account in Google Cloud, or a custom view-only role for the CloudLevy app in Azure, in your own account. You can remove it any time, including right after the assessment. We use it only for the assessment and for the check of each fix you apply. The assessment is free from us. Your cloud provider may bill small per-request fees for the read calls. Details: Security page.
Your list & choice
03
Receive your fix list.
A written, dated list. Each line: the resource, the change, and the monthly saving from your own bill, plus the evidence and our confidence. The saving is our estimate, not a guarantee. Senior DevOps and cloud engineers help run the assessments. A person reads every fix list before we send it. Yours to keep, even if you apply nothing.
04
Choose and apply.
Apply all, some, or none. Your team makes the changes. When you've applied a fix, tell us so we can run the check.
One check & fee
05
One check, then one fee per applied fix.
We check each fix once, at your next invoice after the change. Fee for that fix: 10% of the confirmed annual saving (confirmed monthly saving times 12), due once. If the check confirms less than the list, the fee is lower. It is never based on more than the list. No applied fix, or no saving, means no fee. The check happens once. If the saving later shrinks or ends, the fee stays. After the last check, we stop using your access.
01Request the assessment.
Tell us which clouds you use and roughly how your accounts are set up. No credentials in the form. Before we send the list, we send short written terms: the 90-day window, how the fee works, the billing evidence request, and how disagreements are resolved (which may include arbitration). Agreeing costs nothing and commits you to nothing.
02Create read-only access.
We send a guide with the exact permission list. You create a role in AWS, a service account in Google Cloud, or a custom view-only role for the CloudLevy app in Azure, in your own account. You can remove it any time, including right after the assessment. We use it only for the assessment and for the check of each fix you apply. The assessment is free from us. Your cloud provider may bill small per-request fees for the read calls. Details: Security page.
03Receive your fix list.
A written, dated list. Each line: the resource, the change, and the monthly saving from your own bill, plus the evidence and our confidence. The saving is our estimate, not a guarantee. Senior DevOps and cloud engineers help run the assessments. A person reads every fix list before we send it. Yours to keep, even if you apply nothing.
04Choose and apply.
Apply all, some, or none. Your team makes the changes. When you've applied a fix, tell us so we can run the check.
05One check, then one fee per applied fix.
We check each fix once, at your next invoice after the change. Fee for that fix: 10% of the confirmed annual saving (confirmed monthly saving times 12), due once. If the check confirms less than the list, the fee is lower. It is never based on more than the list. No applied fix, or no saving, means no fee. The check happens once. If the saving later shrinks or ends, the fee stays. After the last check, we stop using your access.