You can now add budgets directly to reports in the Ternary Reporting Engine. Budgets appear as overlay lines on charts and as variance columns in tables, giving you an at-a-glance view of how actual cloud spend compares to plan.

What’s new

Budget overlay lines on charts. When a budget is added to a report, a reference line appears on bar, line, and area charts showing the budgeted amount for each period. If the budget changes month to month, the reference line adjusts accordingly. Budget details are also included in chart tooltips and legends for additional context. Reports can be saved with budgets applied, and overlays update automatically as underlying data refreshes.

Variance columns in tables. In table view, the budget amount and variance columns are automatically included. For standard budgets, totals and variance are displayed at the summary level. For hierarchical budgets, amounts and variance appear inline, aligned to the appropriate dimension. When the Show Totals toggle is enabled, the footer includes budget and variance values alongside cost totals.

Dashboard widget support. Reports with budget overlays render seamlessly when pinned to dashboards, ensuring budget tracking is visible alongside your other key metrics.

How to get started:

Open a budget in Ternary and select “View in Report Builder.” The budget overlay will appear on supported chart types and in table view.

Note: Budgets are currently supported at monthly granularity.

Why it matters

This enhancement brings planning and performance tracking into the same reporting workflow. Teams can monitor budget adherence, identify variance earlier, and take action without switching between tools.

We’ve added vendor icons to the report configuration sidebar in the Ternary Reporting Engine.

What’s new

• Vendor icons in the sidebar. Each measure and grouping now displays a vendor icon alongside the field name, making it easier to identify the data source at a glance.

Why it matters

• Many vendors use similar tag names across platforms. By surfacing vendor icons directly in the report builder, this update reduces confusion and helps ensure you’re selecting the correct fields when building multi-vendor reports.
  
  

  
  

With the full transition to FOCUS Billing, all Ternary data and reporting now come from this modern, unified pipeline. As a result, we are deprecating the legacy billing data source and the reports built on it.

Key dates

• March 2, 2026: Ternary will stop importing data from the legacy billing pipeline. Reports using 'Billing' as the data source will no longer update, but will remain visible in your tenant.
• July 31, 2026: All legacy billing reports will be permanently removed from the Ternary platform.

What you need to know

To continue tracking your cloud spend, we recommend migrating any reports still using the legacy 'Billing' source to the new FOCUS Billing data source.

We’ve enhanced the report configuration experience in Ternary to provide better guidance when building reports.

When opening the dropdown selectors for measures or groupings, you will now see helpful tooltips that include:

• Descriptions to explain the data behind each field
• Links to FOCUS or cloud service provider (CSP) documentation for deeper technical context

Why it matters

This update makes it easier to understand what each measure or grouping represents, reducing guesswork and helping you build more accurate, trusted reports. Whether you're new to Ternary or working across cloud providers, these tooltips give you immediate access to the information you need.

We’ve updated the alert rule side panel in Anomaly Detection to deliver a clearer, more intuitive configuration experience.

Why it matters

This refreshed layout improves the way you define, review, and manage anomaly rules, making it easier to focus on the conditions and thresholds that matter most.

View the image below to see a side-by-side comparison of the previous and updated UI.

Ternary Reports now support custom number formatting, giving users greater control over how numbers are displayed in both the UI and exported files.

What’s new

• User-level number formatting. Choose how numeric values appear in reports, including support for regional formats such as decimal signs, thousands separators, and abbreviations (for example, 1.000.000, 1M, or 1MM). To configure, open the Settings menu from your profile dropdown and navigate to the Number Formatting tab.

• Custom export formatting. By default, exports use raw numeric values. To customize the export format, uncheck the raw numbers option during export. This opens a formatting menu where you can apply your preferred numeric style to that report.
  
  

Why it matters

This enhancement ensures that reports and exports are easier to read, share, and interpret across different regions and stakeholders. Whether you're working with EU-style formatting or need shortened metrics for executive summaries, Ternary gives you control over how numeric data is presented.

Ternary now supports multi-channel Slack notifications, allowing you to send the same anomaly alert to multiple public Slack channels without duplicating configurations.

Why it matters

This enhancement improves visibility and reduces the overhead of managing separate alerts for different teams. By routing alerts to the right Slack channels, teams such as FinOps, Engineering, and Operations can stay informed and take action faster.

How to get started

First, configure the Slack integration from the Admin page. Once connected, go to the Anomaly Detection page to select which public Slack channels should receive alerts. You can assign multiple channels to a single alert to ensure that all relevant teams are notified.

Ternary now supports direct integration with Databricks, making it easy to ingest your Databricks usage and cost data into the Ternary Reporting Engine for unified reporting and analysis.

You can now view Databricks costs alongside your existing multi-cloud infrastructure and technology vendor spend, giving you a more complete view of your organization's usage and cost drivers.

Why it matters

This integration helps FinOps and engineering teams track Databricks consumption in the same place as cloud and SaaS data, reducing silos and improving visibility across environments.

How to get started

Visit our Databricks integration documentation for setup instructions and configuration guidance.

Ternary now supports both legacy and Multiprice Committed Use Discount (CUD) models for Google Cloud.

Google’s new Multiprice CUD billing model introduces a shift from credit-based savings to a net pricing consumption model, along with updates to BigQuery export schemas, SKU identifiers, and Marketplace Procurement API flows.

Key dates

• July 15, 2025: All new Google Cloud billing accounts default to the Multiprice CUD model. Existing accounts without active CUDs can opt in at any time.
• January 21, 2026: Google will automatically migrate all remaining accounts to the Multiprice model.

Why it matters

With this support, Ternary ensures continuity in reporting and optimization workflows as Google transitions to its new CUD model. Customers can continue tracking commitment utilization and cost efficiency without disruption, regardless of which model their billing account is using.

We’ve introduced several enhancements to improve how you interact with data in Ternary Reports. These updates make it easier to explore, filter, and display report results based on your workflow and preferences.

What’s new

• Interactive table filters. You can now filter reports by clicking directly on table cells. Selecting a grouping value updates the chart and right-hand configuration panel, with support for multiple selections and clear visual feedback. This behavior also applies to dimension labels, chart segments, and legend items.
• Comfortable and compact display modes. Switch between Comfortable (default) and Compact modes in data tables. Compact mode reduces row height and padding, allowing more rows to be visible on screen. The selected view persists across reports until changed.
• Auto-run option for reports. Reports no longer auto-run by default when variable inputs change. You can now manually run a report using the Run button or enable auto-run in the UI for a more exploratory experience. Your preference is saved per report.

Why it matters

These updates give users more control over how they interact with report data. Whether you're digging into specific values, scanning large datasets, or fine-tuning report inputs, the experience is now more responsive, customizable, and aligned with the way different teams work.