Kion's FinOps+ v3.16 release: automation that acts, AI token spend that's finally visible. June 15, 2026 Kion v3.16 is a release built around a simple premise: knowing about a problem and doing something about it are two very different things. This release closes that gap. Kion is introducing Automation Policies, a dedicated framework for defining and enforcing cloud actions at scale. Kion is also adding a native Anthropic integration that brings AI token spend directly into Kion instead of relying on Kion's Custom Provider option. Lastly, Kion has expanded granularity in Spend Reports with SKU Meter support, giving teams the billing-level detail that actually shows up on your invoice. Automation Policies: A dedicated home for cloud action. What's new. Kion v3.16 introduces Automation Policies, a new capability that gives cloud operations and FinOps teams a dedicated place to define, manage, and apply automated actions across their cloud environments. High-Level overview. If you've used Kion's compliance features for a while, you may have noticed something awkward: a lot of what people actually want to automate has nothing to do with compliance. Tagging resources, scheduling compute shutdowns, cleaning up orphaned assets - these are operational hygiene tasks, not audit findings. Cramming them into a compliance workflow created confusion about what compliance scores meant and made it harder to find and manage these policies over time. Automation Policies fix that. They're cloud custodian policies with their own dedicated space in the platform, their own labeling, and their own application logic completely separate from compliance standards and scores. You create an Automation Policy, attach it to accounts or cloud rules in your hierarchy, and let it run. No compliance score noise. No hunting through your compliance feature to find a policy that was never really about compliance in the first place. Kion v3.16 ships with a set of out-of-the-box policies built around the most common, highest-value use cases: Auto-Tag Resources: Pre-configured policy to tag all supported resources using custom variables. Tags provide spend visibility in shared accounts and identify ownership for both humans and automation downstream. Scheduled Lights On/Lights Off: Schedule compute and database resources to power down during off-hours and back up when needed. For teams running non-production environments, this is often the single fastest path to real cost reduction. Define multiple policies for flexibility, and use the default to get started quickly. Orphaned Resource Deletion: Automatically remove resources that are older than a specified number of days and are unattached or unused. This covers things like Elastic IPs, abandoned load balancers, and idle compute instances. The resources that generate charges while doing nothing. No manual savings opportunity review required. It just happens. Why it matters. Automation Policies matter because enforcement is where FinOps and cloud governance actually intersect. Knowing you have orphaned resources is useful. Automatically deleting them is valuable. The gap between awareness and action has always been a friction point, and for a long time the answer was "write a script, set up a Lambda, hope it keeps running." Automation Policies give you a platform-native way to close that gap, governed by the same hierarchy and permissions structure you already have in Kion. And this is Phase 1. The foundation Kion is building here is the pre-requisite for the multi-tiered workflow capabilities Kion want to build next: notifications, approvals, and more complex policy logic tied to the events that actually matter to your organization. Direct Anthropic integration: native AI spend visibility. Kion now supports a native integration with Anthropic as a direct billing source. Connect your Anthropic premium license to Kion and pull AI token spend into the same financial management layer you use for AWS, Azure, GCP, and OCI today. Some context on where Kion is coming from: Anthropic token spend has been visible in Kion for a while already, for customers ingesting it through a FOCUS converter via their cloud provider bill. That path works, but it's indirect. The data arrives on whatever cadence your cloud provider exports it, it flows through a conversion layer, and by the time it lands in Kion it's often days old. This integration is different. You connect your Anthropic organization directly to Kion using an Admin API key, and spend flows in natively. That means more timely data, cleaner attribution, and no dependency on how your cloud provider handles AI marketplace billing. Once connected, it works the way everything else works in Kion. Spend Reports show Anthropic spend broken down by model and token type, making it easier to understand which teams, applications, and AI workloads are driving token costs. You can allocate AI spend to a Scope tied to a specific agent, team, or workload. And Anthropic token spend contributes to budgets and enforcements the same way any other cloud cost does. The conversation about AI spend governance has been building for a couple of years now, and most teams are still in "figure out what we're spending" mode rather than "actively manage and enforce" mode. A big part of why is the data problem: AI spend is real but it's scattered, it shows up late, and it doesn't map cleanly into existing cost structures. A direct integration closes most of that gap. When Anthropic spend lands in Kion natively and on time, you can actually govern it. Budget enforcements can include it. Scopes can allocate it. Spend Reports can break it down the same way you break down any other service. You stop treating AI as a separate problem and start treating it as part of the cloud financial picture it already is. SKU Meter in Spend Reports: more granularity where it counts. As a quick note on a FinOps reporting improvement also shipping in 3.16: SKU Meter is now available as a dimension in Spend Reports. SKU Meter surfaces the usage-type level billing detail you need to actually reconcile a Spend Report against your cloud bill. That means AWS Usage Type, Azure Meter Name, GCP SKU Description, and OCI SKU Name, all in a single multi-cloud, FOCUS-compliant dimension. For FinOps teams responsible for chargeback, showback, or invoice validation, SKU Meter makes it easier to trace costs back to the exact usage categories that generated them. See what's driving spend and connect it directly to your invoice, without leaving Kion. What v3.16 adds up to. Automation Policies, native Anthropic integration, and deeper billing granularity don't share a theme by accident. They're all answers to the same underlying question teams have been asking: how do Kion stop managing cloud spend reactively and start operating it proactively? Automation Policies let you define the actions and let the platform take them. The Anthropic integration brings a fast-growing category of AI spend into the governance layer you've already built, with better data and less lag than the converter path. SKU Meter gives you the granularity to hold your cloud bill accountable at the line-item level. Kion v3.16 helps teams move from visibility to action by automating routine governance tasks, bringing AI token spend into existing FinOps workflows, and providing the reporting detail needed for confident financial management. If you'd like to see how these capabilities fit into your environment, request a demo or reach out to your customer success team.

Kion introduces Scopes: A new model for financial ownership across Cloud and beyond. March 27, 2026 As organizations scale, financial ownership no longer fits neatly into cloud account structures. Teams span accounts, shared services blur boundaries, and spend increasingly extends beyond cloud into SaaS and GenAI. The result is a disconnect between how costs are incurred and how ownership is understood. This makes it difficult to answer: * Who is responsible for this spend? * How is ownership best represented across services? * Where should accountability live? With Kion v3.15, Scopes introduces a new way to model financial ownership, aligned to how organizations actually operate across cloud and beyond. What are Scopes? Scopes define logical ownership boundaries using metadata and rules, independent of accounts, providers, or spend type. They create a flexible layer of visibility across: * Cloud infrastructure * SaaS applications * GenAI and usage-based services With Scopes, teams can utilize detailed criteria and granular metadata to: * Understand total technology spend in context * Easily organize costs by team, application, or business unit * Apply financial guardrails aligned to true ownership Scopes can separate or combine spend types, allowing teams to isolate 3rd party costs (ex: GenAI usage) or unify all spend into a single ownership view. With Scopes, any resource, type of spend, or metadata can be used to create detailed financial ownership. Extending Kion's org chart into financial ownership. Kion has long provided visibility through OUs and Projects. Scopes extend this by adding an ownership layer that is not constrained by accounts. This enables organizations to: * Better represent ownership across accounts, clouds, and services * Align budgets and reporting to teams and applications with shared infrastructure * Create financial guardrails at a resource level * Connect structure with true cost ownership across all types of technology spend From cloud cost to total technology spend. FinOps is expanding beyond cloud into total technology spend, including SaaS, GenAI, and shared services. Most organizations still manage these separately. Scopes unify them. By defining ownership once and applying it across spend types, teams can: * Create a complete view of what a team owns * Maintain consistency across cost models * Adapt as new spend categories emerge For example, with Scopes, organizations can group their GenAI spend by model type and/or token type to get better insight into the drivers of their AI spend. A practical take on FinOps Scopes. The FinOps Foundation introduced Scopes to define ownership beyond traditional cloud boundaries. Kion operationalizes this approach by aligning ownership to business context, keeping it consistent across environments and flexible over time. Why this matters for FinOps. Account-based ownership breaks down in modern environments with multi-cloud, shared services, and SaaS/GenAI spend. Scopes shift to context-based ownership across all technology spend, enabling teams to: * Align accountability to real ownership * Unify visibility across spend types * Apply controls where they matter Key advantages. * Ownership modeled independently of account structure * Visibility across cloud, SaaS, GenAI, and shared services * Ability to combine or isolate spend types * Alignment between org structure and cost ownership * Flexible, metadata-driven definitions Model ownership the way your organization actually works. Scopes represent an evolution in financial ownership. By moving beyond rigid structures, teams can align total technology spend, across cloud, SaaS, and GenAI, with real accountability. This creates a more scalable foundation for modern FinOps.To learn more about Scopes and how they support modern FinOps practices, explore the full Kion v3.15 release. Frequently Asked Questions About Scopes

Extending FinOps beyond public cloud with FOCUS converters. March 25, 2026 As organizations increasingly expand workloads across public cloud, SaaS platforms, AI services, and on-prem infrastructure, financial governance is becoming more complex. FinOps teams need consistent visibility into spending across these environments, but cost data is often reported in different formats depending on the platforrm. The FOCUS specification (FinOps Open Cost and Usage Specification), developed by the FinOps Foundation, provides an open standard for normalizing cost and usage data across providers. By standardizing billing datasets, FOCUS helps organizations analyze and compare spending across cloud and technology services more effectively. Kion was an early adopter and integrator of the FOCUS specification, helping organizations normalize billing data across major cloud providers including AWS, Azure, GCP, and OCI. However, modern infrastructure extends well beyond traditional cloud services. To support this shift, Kion developed automated FOCUS converters that transform cost datasets from AI platforms, SaaS services, and on-prem environments into the FOCUS format. By automating this transformation, organizations can quickly ingest new cost sources into their Kion FinOps+ workflows and gain faster visibility into spending across the technology estate. The challenge: FinOps visibility beyond public cloud. Public cloud providers already produce relatively structured billing and usage data. However, AI platforms, SaaS tools, and on-prem environments often expose cost data in very different formats. This creates several challenges for organizations trying to implement FinOps practices: * Cost data from SaaS platforms may not align with cloud billing schemas * AI platforms may report usage in non-standard units that don't align with traditional cloud billing models. * On-prem environments often lack standardized cost reporting entirely * Historical spend data may require manual transformation before analysis Even with the FOCUS specification providing a common data standard, organizations still face a major hurdle: Transforming diverse datasets into FOCUS-compliant data quickly enough to provide immediate value. This is where automation becomes critical. Bridging the gap: automated FOCUS converters. While FOCUS standardizes cost data, it does not solve the challenge of transforming raw datasets into that format. To address this, Kion developed custom FOCUS converters that transform cost data from SaaS platforms, AI services, and on-prem environments into the FOCUS format. These converters automate what would otherwise be a manual data transformation process, enabling organizations to bring additional environments into their FinOps workflows faster. Examples of platforms supported today include: AI Platforms * OpenAI * Anthropic SaaS Platforms * Databricks * MongoDB Atlas On-Prem Infrastructure * VMware environments Kubernetes * OpenCost Partners (MSP, ISV, Resellers) * Azure Partner Center By automatically converting these datasets into FOCUS-compatible data, organizations can quickly ingest spend data into Kion and begin analyzing it immediately. Accelerating time to value for FinOps teams. The key benefit of automated converters is speed of implementation. Without automation, organizations may need to: * Export raw cost data from multiple services * Manually map fields to a standardized format * Normalize historical data * Load the transformed data into a FinOps platform This process can take weeks or months. Automated FOCUS converters streamline this workflow by handling the data transformation automatically during onboarding, allowing organizations to start analyzing cost data much sooner. This accelerated time to value is especially important as organizations experiment with AI workloads, where cost visibility is often the first step toward responsible governance. Supporting FinOps for AI and emerging infrastructure. As AI adoption increases, organizations are looking for ways to track and manage the financial impact of AI services. Many AI platforms expose usage data differently than traditional cloud services, often in units like: * Tokens * API calls * Model usage * Credits FinOps tools must therefore evolve to support both infrastructure costs and AI consumption models. Organizations across regulated industries, including healthcare, energy, biotechnology, and the public sector, are already using Kion to gain visibility into AI-related spending as part of their broader financial governance strategies. By standardizing and transforming these datasets into a consistent format, organizations can begin to apply FinOps principles to AI workloads just as they would with cloud infrastructure. Looking ahead, deeper AI usage reporting, such as token-level visibility, may further expand how organizations manage and optimize AI costs. As infrastructure continues to evolve, combining open standards like FOCUS with automated data transformation will be essential for gaining complete financial visibility across cloud, SaaS, AI, and on-prem environments. Frequently Asked Questions (FAQ)