Skip to Main Content
Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace Cloudability
Created by Guest
Created on Apr 16, 2026

Direct query access to native cloud billing fields

Cloudability currently abstracts and normalizes all billing data from providers such as AWS, Azure, and GCP. While this enables unified cost visibility, it limits users' ability to validate and interpret data in "like-for-like" terms with the original cloud provider. Also, some fields currently appear hidden and are not able to be used within the tool. A new capability allowing direct query access to native field values would GREATLY enhance transparency, simplify migration, and improve data alignment. Cloudability has our data - let us access all of it.

Requested Enhancement
Add an optional "Native Field Query Mode" within Cloudability's data explorer and/or API. This mode would allow users to run queries using the raw provider field names (e.g., UsageType, ProductCode, ResourceId in AWS, or service.name in GCP). Users could toggle between Normalized Mode and Native Mode to view or export data as-is from each provider's Cost and Usage Reports or equivalent billing sources.

 

Benefits
For Customers:

  • Improves accuracy and trust in Cloudability's reporting by allowing one-to-one data validation against cloud provider data.
  • Simplifies report migration from in-house or third-party tools by leveraging familiar field names and schema.
  • Enables deeper analytics and debugging when reconciling anomalies between normalized and provider-native data.

For IBM Cloudability:

  • Enhances credibility and adoption among advanced FinOps teams who require transparency.
  • Reduces support case volume related to data mismatches or unclear normalization logic.
  • Attracts enterprise customers migrating from native cloud billing pipelines who value schema-level continuity.
  • Mitigates competitive risk from tooling providers who have this native functionality (CloudHealth, Harness.io, and many others).

 

How It Should Work

- Introduce a "Query Mode" toggle in both UI and API endpoints.
- In Native Mode:

  • Query syntax matches provider-native fields and metadata.
  • Data returned maps 1:1 with source billing file structure.
  • Option to download results in provider-native format (CSV/Parquet).

- In Normalized Mode (default):

  • Queries use Cloudability's unified field taxonomy.
  • Existing dashboards, reports, and dimensions remain unaffected.

- Implement field documentation and mapping reference per provider for clear usage guidance.

Idea priority Urgent
  • Admin
    AJ Peter
    Jul 6, 2026
    Thanks for the request. Direct access to native billing fields is a meaningful transparency and reconciliation use case. I am moving this to future consideration so it stays captured for roadmap prioritization.