Bifrost (Maxim AI)
Open-source, performance-focused gateway unifying LLM, MCP, and agent traffic.
The tools that let an enterprise see, control and prove the economics of the AI it uses, from the model call to the board pack. Organised by the problem each one solves, with every entry checked against its own sources.
Vendor-neutral and unsponsored. The map describes vendors from public sources and does not rate, score or rank them. IBM-owned products are marked IBM-owned. See how the map is built. Tokenomics Foundation membership comes from the Foundation's members page and signals engagement with the discipline, not quality. I'm Ed Epstein, an enterprise account executive at IBM in the Apptio portfolio (Apptio, Cloudability, Turbonomic), and I write and edit AI Economics Hub. IBM sells products in several areas this site covers, including FinOps, technology business management and AI value measurement, and is a member of industry bodies the site discusses, including the Tokenomics Foundation. This is an independent personal publication. The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. No IBM, client or partner confidential information is used. IBM-owned products are marked wherever they appear, and the vendor map describes products without rating them.
Start with your problem
Most buying mistakes in this market come from choosing a category before naming the problem. Pick the statement closest to yours to see the vendors that address it.
Directory
Showing 99 of 99
Layer A: Build and run
Problem it solves: Multi-provider access, routing policy, failover, budget enforcement at the point of consumption.
The gateway is where AI cost policy becomes enforceable rather than reportable. This is the layer FinOps teams most often discover they are missing.
Maps to Usage Transparency in the Five-Layer model; most relevant at maturity levels 1 to 3.
Open-source, performance-focused gateway unifying LLM, MCP, and agent traffic.
Edge-network gateway with caching, rate limiting, analytics, and unified billing for third-party model usage.
AI routing built on Kong's established API management platform.
AI gateway with agent tracing and cost monitoring, compatible with LangChain, Google ADK, OpenAI and other frameworks.
Open-source LLM proxy and gateway with broad provider coverage, budgets, and key-level spend controls.
Model router that predicts the best model for each request, now focused on coding agents.
Managed single endpoint across hundreds of models with aggregated billing.
Full-stack AI gateway combining routing with observability, guardrails, governance, and prompt management.
OpenAI-compatible router across 600+ models, with routing, caching, failover, observability and EU data residency.
Enterprise AI gateway and MCP gateway with rate limiting, observability and compliance controls, plus model deployment.
Managed routing tied to the Vercel platform, with pass-through provider pricing and automatic fallbacks.
Also plays a role here:
Layer A: Build and run
Problem it solves: Trace-level cost, quality, and workflow context.
This is where cost data meets quality data. Without it, optimisation degrades into cheapest-token chasing.
Maps to Usage Transparency and Output Quality in the Five-Layer model; most relevant at maturity levels 2 to 3.
Two products: Phoenix, a free self-hosted tracing and evaluation project, and Arize AX, the commercial platform with online evaluation, drift monitoring and enterprise support.
Evaluation-first platform with logging, prompt management, and a gateway designed to feed its eval workflows.
Extension of Datadog's observability platform into LLM tracing, quality, and cost monitoring.
AI observability and evaluation platform that turns offline evaluations into production guardrails.
Part of Mintlify
Open-source LLM observability and cost monitoring with an AI gateway for routing, failover and caching.
Part of ClickHouse
Open-source LLM observability with tracing, evaluation, and cost visibility.
Part of LangChain
Tracing, evaluation, and monitoring platform tightly paired with the LangChain ecosystem.
Open-source AI observability and evaluation platform from Comet for testing and improving agent systems.
LLM reliability platform and maintainer of OpenLLMetry, the OpenTelemetry-based instrumentation for LLM apps; joining ServiceNow.
Part of CoreWeave
LLM tracing and evaluation inside the established W&B ML platform.
Part of OpenAI (acquisition announced)
Open-source test harness that compares prompts and models on output quality, estimated cost and latency, with red teaming for security.
Part of Snowflake
Open-source evaluation and tracing library for LLM apps and agents, built to find the quality and cost frontier between versions.
Open-source evaluation framework with metrics for retrieval-augmented generation, agents and tool use. Its role is quality evidence, not financial management.
Layer A: Build and run
Problem it solves: GPU efficiency, container and workload optimisation, commitment management.
Infrastructure optimisers focus on GPU utilisation, Kubernetes efficiency, and cloud commitment management.
GPU cloud providers such as CoreWeave, Lambda, Together, Fireworks, Baseten, and Modal are supply-side infrastructure, not governance tools, and are therefore not profiled as directory entries. They are referenced here as context for where AI workloads run, but the vendor map focuses on buyer-side control and visibility platforms.
Maps to Usage Transparency in the Five-Layer model; most relevant at maturity levels 2 to 3.
Kubernetes optimisation platform with automation-led scaling and strong relevance for GPU-heavy AI infrastructure.
Kubernetes-native cost allocation platform with strong GPU and workload-level visibility for AI infrastructure.
Application resource management platform that uses automation to improve utilisation and performance across cloud and container environments.
Shift-left FinOps: shows the cost impact of infrastructure-as-code changes and applies policies before deployment.
Automated AWS cost optimisation, centred on hourly commitment management, with pay-for-results pricing.
Cloud Efficiency Posture Management platform with engineering-centric waste detection, automated remediation, and AI-adjacent efficiency controls.
Automation-led FinOps platform focused on commitment optimisation, workload scheduling, and showback metrics.
Cloud infrastructure optimisation (Spot Eco, Spot Ocean, Elastigroup) and CloudCheckr, now part of Flexera.
Cloud governance as code built on the open-source Cloud Custodian project, with an AI agent (Jun0) for FinOps tasks.
FinOps platform built around spot instance optimisation (SpotIQ), Kubernetes node selection (ClusterIQ) and AI token optimisation (TokenIQ).
Layer B: Financial governance
Problem it solves: Allocation, showback, anomaly detection, and governance across cloud plus AI spend.
FinOps platforms extend cloud cost governance into AI workloads, providing allocation, budgets, and optimisation workflows.
Maps to Usage Transparency and Delivery Alignment in the Five-Layer model; most relevant at maturity levels 2 to 4.
Cost governance across cloud, AI platforms, code and runtime, with automated pull requests to fix waste.
FinOps-oriented platform positioning AI agents around forecasting, anomaly detection, and predictive spend governance.
Mature FinOps suite extending broad cloud cost governance into AI, containers, and unit economics.
FinOps platform with cloud and AI cost attribution and automated workflows to act on waste.
Cost intelligence platform that ties cloud and AI spend to teams, products, features, and unit economics.
Cloud cost data joined with Datadog performance and observability data, including AI and LLM spend.
FinOps platform (Cloud Intelligence) combined with hands-on engineering support, covering anomalies, Kubernetes and workflows.
Enterprise FinOps platform with dedicated AI cost management, virtual tagging, and shared-cost allocation.
Hybrid ITAM and FinOps suite with cloud cost optimisation and visibility across broader technology estates.
Engineering-facing cloud cost platform with allocation, showback and chargeback, and AI-assisted optimisation.
Cloud governance and FinOps platform (Kion FinOps+) that has added Anthropic token spend management.
AI and hybrid cloud cost management covering GPU, cloud and AI infrastructure, with forecasting and allocation.
FinOps platform covering cloud, AI and data spend, with automated savings.
AI FinOps and data observability for cloud data platforms and LLMs, using an AI agent called RADEN.
Multi-cloud FinOps platform extending forecasting, anomaly detection, and allocation into AI workloads.
Cloud financial management platform that uses AI to detect waste, track savings and forecast costs, aimed at enterprises and managed service providers.
Multi-cloud cost management platform with AI provider integrations, savings automation, and GPU-efficiency reporting.
Layer B: Financial governance
Problem it solves: AI cost inside enterprise service, planning, and portfolio structures.
TBM and ITFM platforms translate AI cost into business service models, cost pools, and portfolio planning structures.
Maps to Delivery Alignment and Portfolio Strategy in the Five-Layer model; most relevant at maturity levels 3 to 5.
TBM and ITFM platform for cost transparency, allocation, planning, and application of TBM structures to AI spend.
Technology financial management platform recognised in analyst conversations for cost transparency, service insight, and business reporting.
ITFM platform for cost transparency, forecasting, and scenario modelling with explicit visibility into AI and cloud costs.
ServiceNow platform capabilities that expose IT cost, asset, and service data inside broader enterprise workflow and AI contexts.
Platform that combines AI economics, TBM and FinOps for visibility across cloud, SaaS, infrastructure and AI spend.
Layer B: Financial governance
Problem it solves: We can see the AI bill but not what each customer, agent, workflow or product feature costs, so we cannot price, budget or protect margin.
A young category that sits between the gateway and the finance team. These tools meter AI usage at transaction level and attribute it to a customer, agent, feature or workflow, so cost can be compared with revenue or value. They matter most to companies that sell AI-powered products and need cost per customer or cost per outcome. Expect overlap with FinOps platforms adding token cost, and with gateways adding metering.
Usage-based billing platforms such as Stripe Billing (which completed its Metronome acquisition on 14 January 2026), Orb and Amberflo are seller-side tools for charging your customers. They are out of scope here, but often appear in the same evaluation.
Maps to Usage Transparency and Portfolio Strategy in the Five-Layer model; most relevant at maturity levels 2 to 4.
Cost and margin visibility for AI agents, down to each action, agent and customer.
Metering and attribution for AI usage at transaction level, across tokens, APIs and agent workflows, with real-time spend controls.
Layer C: Consumption and workforce
Problem it solves: Copilot, ChatGPT Enterprise, Claude, and embedded AI SKUs are bought as software subscriptions outside the FinOps remit. Shadow AI usage is invisible to all of it.
For most enterprises, seat-based workforce AI is already a larger controllable line than API tokens, and almost no FinOps practice owns it.
Maps to Usage Transparency and Productivity Value in the Five-Layer model; most relevant at maturity levels 1 to 3.
Measurement layer for enterprise AI: what AI costs, what teams produce with it and which workflows to automate next.
GenAI visibility platform spanning shadow AI discovery, licence intelligence, and a 2026 AI value realisation module.
Cost, usage and licence intelligence across the Microsoft estate and multicloud, with a module for Microsoft 365 Copilot readiness, adoption and licence optimisation.
SaaS management platform with shadow IT and shadow AI discovery plus licence optimisation.
Workplace analytics that shows how work and AI adoption happen across the organisation, from collaboration and tool data.
SaaS management platform with AI application discovery, licence utilisation, and renewal governance.
Part of Microsoft
Native Microsoft 365 measurement of Copilot and agent adoption, credit consumption and business impact, delivered through Viva Insights and the admin centre.
Also plays a role here:
Layer C: Consumption and workforce
Problem it solves: Per-seat and usage-hybrid AI coding spend with weak FinOps visibility.
AI coding tools represent one of the largest current enterprise AI spend categories, but cost governance maturity varies widely across vendors.
Maps to Usage Transparency and Productivity Value in the Five-Layer model; most relevant at maturity levels 1 to 3.
AWS-native AI coding and development assistant with per-seat pricing, AWS-integrated billing, and enterprise governance through IAM and AWS Organizations.
Agentic coding tool spanning terminal, IDE, and enterprise deployments, with usage-based and seat options.
AI-first code editor with deep model integration, growing enterprise adoption, and tiered pricing including a Business plan with centralised billing.
Agentic code editor from Cognition, rebranded from Windsurf in June 2026, centred on managing local and cloud coding agents.
Per-seat AI coding assistance with Google Cloud billing integration.
AI coding assistant from Microsoft with Business and Enterprise tiers, offering seat-level billing, admin controls, and a Billing API for usage reporting.
AI coding assistance integrated into JetBrains IDEs (IntelliJ, PyCharm, WebStorm, etc.) with per-seat licensing through JetBrains Toolbox for Business.
Part of OpenAI
OpenAI's coding agent across CLI, IDE, cloud and code review, billed through ChatGPT workspace credits or the API depending on plan.
Part of IBM
IBM's agentic software development platform, with built-in consumption analytics (Bobalytics) and modernisation workflows for IBM Z, IBM i and Java.
Layer C: Consumption and workforce
Problem it solves: Proving whether AI coding spend changes engineering output, the bridge from cost to value for the largest current enterprise AI use case.
DORA-metric relabelling is not AI measurement. The credible platforms compare AI-assisted and unassisted work and connect it to delivery outcomes.
Maps to Productivity Value in the Five-Layer model; most relevant at maturity levels 3 to 4.
Developer experience and productivity platform with dedicated AI impact measurement across coding assistants.
Engineering intelligence platform measuring AI coding tool adoption, velocity, and quality effects.
Engineering management platform with AI adoption and impact analytics tied to delivery and investment views.
Software delivery analytics with AI impact reporting and workflow automation.
Cost and outcome analytics for coding agents (Claude Code, Codex, Cursor), linking session costs to engineering work.
Engineering intelligence platform covering delivery metrics, developer experience and AI tool impact.
Also plays a role here:
Layer D: Value and strategy
Problem it solves: Connecting AI usage, cost, quality, and productivity to portfolio decisions, the full five-layer problem.
The thinnest category in the directory, but thin coverage here is not proof that capable products do not exist. Portfolio platforms such as Planview, AI governance layers from ServiceNow and SAP, and new value modules from IBM Apptio are all moving into this space, mostly with capabilities announced in 2026 and not yet proven at scale. Check each one's value evidence: few record realised financial benefit rather than adoption or estimated savings.
Maps to Usage Transparency and Output Quality and Productivity Value and Delivery Alignment and Portfolio Strategy in the Five-Layer model; most relevant at maturity levels 4 to 5.
Measures, adjusts and improves the value of enterprise AI, with products called Atlas, Forge and Convoy.
AI work platform with built-in outcome and ROI measurement framing.
Part of IBM
Links each AI initiative to business outcomes and customer-selected proof metrics, tracking baseline, target, actual and realised results against modelled AI cost.
AI ROI measurement platform connecting adoption data, productivity signals, and business outcomes across tools.
Governance and visibility layer for AI agents, models, and workflows across the ServiceNow platform.
Strategic portfolio management platform adding agent resource management, AI scenario planning and investment-to-outcome tracking.
Part of SAP
Discovery and governance of AI agents, models and MCP servers across vendors, linked to enterprise architecture in SAP LeanIX.
Layer D: Value and strategy
Problem it solves: Showing, from operational data, whether AI changed how work actually runs: cycle times, exceptions, rework and cost per completed case.
These are outcome evidence layers, not AI cost tools. They supply the before-and-after process data that a benefits case needs, and they are most useful when joined to cost data from layers A and B.
Maps to Productivity Value and Delivery Alignment in the Five-Layer model; most relevant at maturity levels 3 to 5.
Process intelligence platform that reconstructs how processes actually run, providing the operational evidence to test whether AI changed business performance.
Part of UiPath
Orchestration of AI agents, robots and people in one process, with process mining and automation-level analytics.
Layer E: Native provider controls
Problem it solves: Native AI billing, tagging, and optimisation controls from cloud platforms.
Hyperscaler native controls are improving but remain incomplete. They are designed to keep workloads within the platform ecosystem.
Maps to Usage Transparency and Delivery Alignment in the Five-Layer model; most relevant at maturity levels 1 to 3.
Native AI billing combines model-level Bedrock pricing with AWS tagging, Cost Explorer, and compute optimisation tooling.
Google Cloud combines Vertex AI pricing with labels and tags, billing export, and recommender-style cloud optimisation controls.
Azure exposes Azure OpenAI and Azure AI Foundry pricing plus native Cost Management, tags, and Advisor recommendations across AI workloads.
OCI provides generative AI cost models plus native Cost Analysis for service-, SKU-, compartment-, and tag-level views.
Layer E: Native provider controls
Problem it solves: Direct model API billing, usage reporting, and spend controls.
Model providers offer varying levels of cost visibility and control. Enterprise governance depth differs significantly across vendors.
Maps to Usage Transparency in the Five-Layer model; most relevant at maturity levels 1 to 2.
Claude API with token-based pricing, caching tiers, batch discounts, and admin APIs for granular usage and cost reporting.
Model API with token-, search-, and embedding-based billing plus billed token reporting and production and trial key separation.
Gemini Developer API with paid and free tiers, token-based pricing, context caching, and project-level quota tiers.
Open-weight model family where economics depend largely on the hosting path rather than a single public billing surface.
API and workspace platform with transparent pricing, usage tiers, and organisation-level rate and token limits.
Model provider covering both the API and the workforce products: token-based API billing with project budgets, and ChatGPT credit analytics and spend controls for enterprise workspaces.
Analysis
Six patterns drawn from the entries and dated events on this page. Each ends with what we would do about it.
We logged 13 acquisitions, renames or exits among vendors on or near this map since March 2025, and 10 current entries carry an ownership or name change. Products bought eighteen months ago may now sit inside a different company with a different roadmap.
What to do: Ask for change-of-control terms, data export in an open format and a dated roadmap commitment.
Portkey now ships as part of Palo Alto Networks Prisma AIRS. Kong AI Gateway and Cloudflare AI Gateway come from API and network security, and TrueFoundry leads with an MCP gateway for agent tool access. Cost control is becoming one feature of a security purchase.
What to do: Decide who owns the gateway, platform engineering or security, and check that budgets and attribution survive the change.
ClickHouse acquired Langfuse, CoreWeave owns Weights & Biases Weave, Mintlify acquired Helicone and Traceloop is joining ServiceNow. Trace data, the raw material for cost per outcome, is moving into larger estates.
What to do: Prefer OpenTelemetry-based instrumentation and open-source cores so traces stay portable if the vendor changes hands.
On 6 October 2026 the homepage titles read “The AI ROI Company” (CloudZero), “FinOps Platform for the Agentic Era” (Finout) and “the complete token engineering platform” (Faros AI). Kion added Anthropic token spend management in a point release. Messaging has moved faster than most products.
What to do: Ask each vendor to load a month of your own model provider billing data and show allocation by team and use case.
SpaceX completed its acquisition of Cursor in August 2026, Windsurf became Devin Desktop, and new tools such as Quesma and Not Diamond exist only to explain or reduce coding-agent spend. Seat prices are giving way to usage-based charges.
What to do: Track cost per merged pull request or per completed task, not cost per seat.
This directory lists 7 entries in AI value management, 2 in process outcomes and 2 in AI unit economics, against 17 FinOps platforms. A short list is not proof of an empty market: Planview and IBM Apptio AI Value & ROI both announced value capabilities in 2026. But only 2 assessed entries are designed to record realised financial benefit rather than adoption or estimated savings.
What to do: Ask each vendor which kind of value evidence it records, and expect to build part of the value model yourself; see the AI Value Gap and AI ROI pages.
Timeline
Acquisitions, renames and exits that change what you are buying. Each links to its source. Removed from the map in this edition: Productiv (ceased operations) and Zluri (now an identity governance product).
14 August 2026
The most widely used AI code editor becomes part of a company that trains its own models. Cursor blog
6 August 2026
A SaaS management vendor exits, a reminder to check vendor viability before multi-year contracts. Productiv
16 July 2026
Palo Alto Networks makes its Portkey-based AI gateway generally available, about six weeks after closing the acquisition. Palo Alto Networks blog
2 June 2026
Cascade agent retired on 1 July 2026, replaced by Devin Local. Devin Desktop
9 March 2026
The open-source evaluation and red-teaming tool is to be folded into OpenAI Frontier; OpenAI says the open-source project will continue. OpenAI announcement
3 March 2026
An open-source LLM observability tool joins a documentation platform. Helicone blog
March 2026
OpenTelemetry-based LLM instrumentation moves towards ServiceNow AI governance. Traceloop blog
14 January 2026
Usage-based billing consolidates into payment platforms. Seller-side billing is outside this map but often in the same evaluation. Stripe newsroom
2026, date not stated
Langfuse says it stays open source and self-hostable. Langfuse blog
2026, date not stated
Follows an $18 million Series A led by Dell Technologies Capital; moves from cost tracking towards AI value measurement. Ascerta
14 July 2025
The Windsurf product and team move to Cognition, maker of Devin. SiliconANGLE
5 May 2025
Weave, the W&B LLM observability product, now sits inside a GPU cloud provider. CoreWeave press release
3 March 2025
Spot Eco, Ocean, Elastigroup and CloudCheckr move into the Flexera portfolio. Thoma Bravo press release
Market structure
No single platform covers the whole chain. Most organisations combine one tool from layer A or E for live control, one from layer B for financial allocation, and build or buy the value view in layer D.
Layer A
Engineering infrastructure for AI demand: model routing, spend enforcement, trace-level observability, and GPU efficiency.
34 vendors
Layer B
Cost allocation, showback, and financial governance from cloud workloads to enterprise portfolio views.
24 vendors
Layer C
Workforce AI tools, seat spend, shadow AI discovery, and measuring productivity impact across engineering.
22 vendors
Layer D
Connecting AI cost, usage, quality, and productivity to portfolio decisions and business outcomes.
9 vendors
Layer E
Baseline billing, tagging, and optimisation controls from hyperscalers and model providers.
10 vendors
Categories also map to the Five-Layer AI Value Intelligence model and the AI Economics Maturity Model; open “How to read this category” in the directory for each mapping.
Supporting notes
These parts of the AI stack move unit costs, sometimes more than model price does, but none is a buyer-side governance product. They are described here rather than listed in the directory. An entry is added only where a product gives the buyer a distinct economic control.
| Technology | Economic effect | Why it is not listed |
|---|---|---|
| Semantic cachingRedis LangCache | Returns a stored answer when a new prompt means the same as an earlier one, so output tokens are not paid for again. Savings scale with the cache hit rate. | A component inside an application or gateway, not a governance product. Several listed gateways include caching. |
| Inference serving and prefix cachingvLLM | Reuses computation for prompts that share a prefix, such as a long system prompt, which cuts prefill cost and latency on self-hosted models. | Supply-side infrastructure. Its effect shows up in the GPU and infrastructure costs that layer A and B tools measure. |
| Agent frameworksLangGraph, CrewAI, OpenAI Agents SDK | Decide how many model and tool calls one task makes. Loop limits, retries and planning steps often matter more to cost per task than model price. | Build tools with no buyer-side cost control of their own. Their cost appears in observability and gateway tools. |
| Vector databases and embeddingspgvector, Pinecone, Weaviate | Retrieval quality sets how much context each prompt carries. Poor retrieval inflates input tokens; storage and re-embedding are recurring costs. | Data infrastructure. Their spend belongs in cloud and FinOps cost allocation. |
| MCP servers and toolsModel Context Protocol servers | Each tool an agent can call adds context, calls and sometimes per-call fees, and widens the surface to govern. | Governed through gateways and agent inventories, such as TrueFoundry and SAP AI Agent Hub, rather than as products in their own right. |
Method
The map organises vendors by the problem each one addresses. It describes what each product does, from public documentation; it does not rate, score or rank vendors, and listing is not a recommendation. Two descriptions help separate products that sound alike:
Both are taken from public documentation for entries added or revised on 8 October 2026; other entries have not yet been described this way. Confirm capabilities and pricing with the vendor. Read how the map is built.
Gaps
Gaps in what we could verify from public documentation, not proof that no product addresses them. Several vendors announced capabilities in these areas during 2026 that have not yet been assessed in use.
Scope
Tools an enterprise uses to govern AI it consumes. Seller-side billing platforms such as Metronome (now Stripe, completed 14 January 2026), Orb, Lago and Amberflo are out of scope.
CoreWeave, Lambda, Together, Fireworks, Baseten, Modal and similar are supply, not governance. They appear in notes where relevant.
A scope decision, not a judgement. Its AI-specific cost capability was not assessed for this edition; existing customers should check current documentation.
Each product appears once, under its primary buyer problem. Secondary roles show as capability tags and cross-references, and product entries name their parent company. Bedrock and Azure OpenAI sit inside the AWS and Azure entries.
One evidence role in the AI value lifecycle sits outside this map: AI risk and model-governance platforms. They supply approval evidence rather than AI cost and value control, so they are not profiled here.
Missing a vendor, or found an error? Corrections are logged publicly on the corrections page. Changes to this map are listed in the changelog.
By Ed Epstein, who works at IBM. The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. About and disclosure · Methodology