Enable Cloudability to ingest and surface OpenAI Codex usage and associated costs, allowing customers to monitor, analyze, and manage their AI-related spend alongside their existing cloud costs.

As organizations increasingly adopt AI-assisted development tools such as OpenAI Codex, AI spend is becoming another category of technology expenditure that FinOps teams need to monitor.

The customers would like to use Cloudability as a centralized platform for understanding their AI-related spend. While the existing OpenAI integration addresses API Platform costs, the customer's requirement is specifically around Codex usage and the associated costs.

The proposed capability would allow customers to ingest Codex cost/usage data into Cloudability and make that information available through Cloudability's existing cost analysis, reporting, dashboards, and FinOps workflows.

Where the underlying source data supports it, the capability could ideally provide dimensions such as usage, service/product, model, account/organization, user, team, or other available attribution metadata. The exact level of granularity should depend on the data exposed by the relevant Codex billing/usage source.

Why is this useful?

Cloudability customers are increasingly managing a combination of traditional cloud infrastructure costs and AI-related costs. If AI spend sits outside Cloudability, customers have to use separate tools or manually combine data to understand their overall technology spend.

Supporting Codex costs would allow customers to:

• Centralize AI and cloud cost visibility within Cloudability.
• Monitor trends in Codex-related spending over time.
• Understand how much their organization is spending on AI-assisted development.
• Include AI costs in broader FinOps reporting and governance.
• Potentially attribute AI spend to teams, users, projects, or other business dimensions where the source data supports it.
• Give leadership a consolidated view of cloud and AI expenditure.
• Establish governance and accountability around the growing adoption of AI tools.

This would also help Cloudability remain relevant as customers expand their technology spend beyond traditional hyperscaler infrastructure into AI services and AI-powered developer tooling.

Who would benefit?

Primary beneficiaries:

• FinOps teams looking to manage AI expenditure alongside cloud expenditure.
• Cloud/IT financial management teams responsible for technology cost visibility.
• Engineering and development leadership adopting Codex across their teams.
• Finance and procurement teams that need visibility into AI-related technology spend.
• Technology leadership looking for a consolidated view of cloud and AI costs.

Customer benefit:

The customer would be able to use Cloudability as a central location for analyzing their cloud and AI spend instead of treating Codex costs as a separate expenditure that must be monitored independently.

How should it work?

Ideally, Cloudability should provide a supported integration or ingestion mechanism for Codex usage/cost data.

A potential workflow would be:

1. Customer connects or provides the appropriate Codex/OpenAI usage and billing source.
2. Cloudability retrieves the available Codex usage and cost information.
3. The data is normalized into Cloudability's cost model.
4. Codex appears as an identifiable AI cost/service within Cloudability.
5. Customers can analyze the data using existing Cloudability capabilities such as reports, dashboards, filtering, allocation/business mappings, and cost trends.
6. Where the source data provides sufficient metadata, customers can further attribute Codex spend to relevant users, teams, projects, models, or other dimensions.