Cross-provider cost allocation, plus broader provider coverage

In the multi-cloud milestone post, cross-provider cost allocation was the natural next step. A week later, it's here.

Cost allocation across every provider

Knowing what each provider costs isn't much use if you can't split that cost across teams or projects. That's why the new Cost Allocation view doesn't just show cost by tag — it also surfaces a coverage KPI and a breakdown of what's untagged, because before splitting anything up you need to know where the visibility gaps are, and those gaps don't stay inside a single provider's border.

Two new providers

• Hetzner — Cloud instances and cost estimates, plus Robot dedicated servers.
• Better Stack — monitors, heartbeats, and status pages.

Broader coverage in existing providers

We also went deeper on two providers that were already connected:

• AWS IAM — roles and policies, with findings and a dedicated audit view.
• Kubernetes — opt-in inventory of secrets, service accounts, and namespaces, plus security stats on the cluster overview.

What's next

We're still broadening provider coverage (Google Cloud, Azure, Vultr, and Linode remain the clearest candidates), and alerts, notifications, and configurable budgets are on the radar.