v1.10 Adds 15-Provider Coverage Without 15 Different Tools
This release solved a practical multi-cloud problem: teams were seeing AWS waste in one place, Alibaba or regional cloud waste in another, and doing the last mile in spreadsheets.
Coverage
15 providers in one workflow
The aim was to remove provider fragmentation from weekly review, not just add more logos.
Depth
Provider-aware waste detection
The release also expanded the detection set so findings would reflect real provider billing models.
Trust
Local-first stayed intact
Provider breadth did not change how credentials were handled or where scans were executed.
This release started from a blunt support ticket: AWS waste is visible, Alibaba waste is not, and the finance handoff still happens in spreadsheets.
That is what v1.10 fixed. Global teams do not suffer from a lack of raw data. They suffer from fragmented review loops. One business unit runs AWS, another uses Alibaba Cloud, and smaller groups keep workloads on DigitalOcean, Oracle, or regional providers that the main tooling ignores.
What changed in v1.10
The scan layer was rebuilt around a more consistent output model so teams could triage findings without changing mental context every time the provider changed.
- AWS
- Azure
- Google Cloud
- Alibaba Cloud
- Huawei Cloud
- Tencent Cloud
- Oracle Cloud
- DigitalOcean
- Linode
- Vultr
- IBM Cloud
- Cloudflare
- Volcengine
- Baidu AI Cloud
- Tianyi Cloud
The point was not completeness for its own sake. It was operational continuity: one scan, one shared backlog, one review meeting.
Detection got deeper too
This release line did more than expand provider names. It added provider-aware checks for idle databases, oversized instances, orphaned load balancers, and other billing patterns that only appear when you understand how each provider turns usage into spend.
That matters because shallow cross-cloud visibility often becomes a lowest-common-denominator report. v1.10 aimed for broader coverage without flattening the useful differences out of the findings.
Why local-first still mattered
Security teams often reject broad SaaS collection models before procurement even begins. That did not change here. The product still kept credentials on the device and executed scanning from the customer boundary. More providers did not mean a broader trust footprint.
Your API keys stay on your device. Scanning happens from your IP address. No infrastructure inventory is shipped to a hosted cloud inventory plane.
For the origin context, start with v1 Launch. For strategy and governance framing, continue with Engineering Trust, Customer Value, ESG.
Run the multi-cloud workflow in your own environment
Save your first $1,000 before the next billing cycle.