In this release, we’re excited to roll out new features that take cloud cost visibility and efficiency to the next level. From AI cost tracking into container workloads to a seamless Google Sheets integration for unit metrics, these updates are designed to give users greater clarity, flexibility, and control over their cloud spending.

Here’s a closer look at what’s new.

We’re excited to introduce a new feature in Octo, AI cost – designed to provide comprehensive visibility into the costs and usages associated with your AI workloads across products and services. This initial release supports AWS services only, with support for Google Cloud (GCP) and Microsoft Azure planned for future updates.

Highlights:

To get started with AI cost:

2. Select AI cost.

3. Fill out the required details.

Once the cost group is successfully created, you can view detailed AI cost insights by selecting the newly created group and navigating to the Insights tab. There, you’ll find comprehensive breakdowns, usage metrics, and cost trends to help you analyze and optimize your AI-related spending.

We’re excited to introduce Container Cost, a new feature that brings deep visibility into your containerized workload spending on AWS. This feature helps you accurately track, analyze, and optimize container resources costs and usage that are often hidden within broader infrastructure charges.

Built for teams running workloads on Amazon ECS and EKS, Container Cost uses AWS’s Split Cost Allocation Data (SCAD) to attribute infrastructure costs directly to containers - giving you granular insights into what’s driving your spend.

To get started with Container Cost:

1.Navigate to Cost Group Manager and click Create Cost Group.

2. Choose the new Container cost option.

3. Select supported services (ECS and/or EKS) to include in your cost group.

4. Fill out the basic details, then continue through the remaining setup steps.

5. Create the cost group to begin tracking container-level spend.

What You’ll See:

A new Insights tab specific to Container cost groups.

Cost and usage breakdowns grouped by cluster, service, task, EC2 Instance, and tagged for ECS Service.

Cost and usage breakdowns grouped by cluster, namespace, deployment, node, workload name, workload type, EC2 instance, pod, and tagged for EKS service.

⚠️ Note: AWS SCAD must be enabled in your billing settings. Currently supports AWS ECS and EKS. For more information about SCAD, see Enabling split cost allocation data - AWS Data Exports in the AWS Blog.

We’ve expanded the flexibility of Unit Metrics by introducing Google Sheets as a supported data source. Users can now connect a Google Sheet directly when creating unit metrics, making it easier to bring in business-relevant telemetry such as API calls, active users, transaction counts, and more—without the need for CSV uploads.

This enhancement is designed for teams who already use Google Sheets to track operational or business KPIs. It streamlines the workflow and reduces manual effort, allowing users to link a sheet, select a specific tab and range, and map columns for date and unit value in just a few steps.

Key Benefits:

This update supports our continued goal of making Unit Metrics easier to adopt across varied data sources, empowering users to drive deeper insights into their unit costs with minimal friction.

We have also made some minor bug fixes and improvements to other existing features.

Thank you for your continued support! Your feedback helps us improve. Stay tuned for more exciting updates coming your way soon!