Savings Analyzer
What Would You Have Saved?
Connect your AWS account read-only and we'll run Nucli8's real optimization strategies over your actual cost history: no estimates, no projections.
Analyze your real AWS history
In a few minutes you'll see, month by month, what Nucli8's convertible-RI and Compute Savings Plans strategies would have saved on your actual usage.
- Read-only access. A cross-account IAM role with an external ID, deployed via a one-click CloudFormation stack. Your credentials stay in your account.
- Your real data. We analyze up to 38 months of Cost Explorer history, however much AWS makes available for your account.
- Revoke anytime. Delete the CloudFormation stack and our access goes with it.
Connect your AWS account
Deploy our read-only IAM role with the CloudFormation quick-create link, then paste the Role ARN from the stack's Outputs tab.
1. Deploy the stack
Open CloudFormation Quick-Create
If the console asks for the ExternalId parameter, copy it from below, because AWS may not pre-fill it.
External ID
2. Paste the Role ARN
Read-only access. The role can read cost and usage data and nothing else. Revoke anytime by deleting the CloudFormation stack.
Scanning your cost history
This usually takes a few minutes. AWS Cost Explorer can be slow for deep history, so keep this tab open.
Starting your scan…
Your Savings Report
Actuals only, no projectionsGross Savings Identified
over your real history
Your Net After Nucli8's Fee
our fee already deducted
Months Analyzed
of real history
ACTUAL VS OPTIMIZED MONTHLY COST
Total actual AWS spend
Gross savings
Nucli8 fee
Net savings to you
Convertible RI Coverage
stable EC2 baseline, gross
Compute Savings Plans
Lambda / Fargate, gross
This is a look-back, not a forecast. Every figure above is what Nucli8 would have saved on your real, historical AWS usage — computed month by month at Nucli8's canonical rates, with no forward projections. Your net savings already has Nucli8's fee deducted, so it's what you would have kept. Read-only access: revoke anytime by deleting the CloudFormation stack in your account.