They start from different operational problems
Kong OpenMeter and Verdix can both support usage-based commercial models, but their starting points differ:
- Kong OpenMeter starts with API, AI and product usage.
- Verdix starts with the signed customer or partner agreement.
OpenMeter is designed to meter activity, manage pricing and entitlements, and support usage-based billing. Verdix translates bespoke agreements and existing operational data into approved billing or reconciliation workflows.
What is Kong OpenMeter?
OpenMeter began as an open-source metering and billing platform. Kong acquired it in September 2025 and integrated its capabilities into Kong Konnect for monetising APIs, AI models and data streams. The open-source project and OpenMeter Cloud have continued alongside the Kong offering.
Kong's Metering & Billing product supports:
- real-time usage metering;
- usage-based and tiered pricing;
- subscriptions and commitments;
- prepaid credits;
- custom enterprise deals;
- usage limits and notifications;
- customer entitlements;
- invoicing and payment-gateway integrations.
Its strongest use cases are products built around APIs, AI tokens, infrastructure consumption and other high-frequency digital activity.
What does Verdix do?
Verdix starts with the final signed agreement.
For customer billing, Verdix:
- interprets the contract;
- identifies rates, thresholds, commitments and billing dates;
- connects those terms to customer-defined operational endpoints;
- retrieves the required usage;
- creates the billing schedule;
- routes it for approval;
- sends approved instructions to the chosen billing system.
For partner reconciliation, Verdix compares the partner agreement, operational activity and incoming invoice to calculate the expected amount and identify discrepancies.
Verdix is not intended to become the company's real-time product-usage ledger or entitlement engine.
Key differences
The architectural difference
Kong OpenMeter's typical workflow starts with the product sending events into the platform. OpenMeter aggregates them and uses configured plans, features and rate cards to calculate usage, control entitlements and produce invoices. Its metered entitlements can track balances and support real-time access checks — making it powerful when usage must influence the product experience immediately.
Verdix reads the signed agreement, identifies which operational data is needed and retrieves it from an existing customer-defined endpoint. Rather than continuously receiving raw events, it fetches what a particular billing cycle requires from a source that already holds the trusted data.
The practical distinction is audience. OpenMeter is designed for engineering and platform teams instrumenting product usage pipelines. Verdix is designed for Finance, RevOps and Billing Operations teams who need to operationalise commercial agreements without replacing existing financial infrastructure.
When Kong OpenMeter may be the better choice
Kong OpenMeter is likely to be stronger when:
- API or AI traffic must be measured continuously;
- usage limits must be monitored in real time;
- customers need live balances or usage visibility;
- prepaid credits must be managed;
- feature access depends on the customer's plan;
- metering is closely connected to the API gateway;
- one product catalogue should support self-service and enterprise pricing.
Kong describes the platform as capable of turning API traffic, events, logs and metrics into billable usage while supporting plans, credits, commitments and invoicing.
When Verdix may be the better choice
Verdix may be more suitable when:
- the signed agreement is the commercial source of truth;
- customer terms are spread across order forms and amendments;
- billing runs monthly or periodically;
- the required usage already exists behind an API;
- Finance manually translates agreements into billing schedules;
- the existing billing, ERP and payment systems work;
- incoming partner invoices also need contractual validation.
The strongest Verdix buyer is not primarily asking: “How do we meter every API request in real time?”
They are asking: “How do we turn each bespoke agreement and our existing operational data into the correct billing or payment instruction?”
Is Kong OpenMeter a competitor or a complement?
It can be both.
They compete when a company is choosing between introducing a new metering, pricing and invoicing platform or keeping its existing infrastructure and adding agreement-led automation. The overlap is growing because Kong OpenMeter now supports custom enterprise deals, subscriptions, commitments and invoicing — not only technical metering.
They complement each other when a business needs OpenMeter's real-time metering but also has complex signed agreements or partner invoices to manage. A combined workflow could be:
- Verdix structures the customer-specific obligations from the signed agreement;
- OpenMeter supplies metered usage and entitlement data;
- Verdix creates the approved billing schedule;
- the billing platform or ERP issues the invoice;
- Verdix uses the same agreement model to reconcile incoming cloud, AI, API or infrastructure-partner invoices.
An important product distinction
OpenMeter is designed to answer: how much was consumed, which plan applies and does the customer still have access?
Verdix is designed to answer: based on the signed agreement and operational evidence, what should this customer be billed or this partner be paid?
A company with real-time AI or API monetisation may need OpenMeter. A company with periodic bespoke billing may need Verdix. A company with both requirements may use the two together.
The takeaway
Choose Kong OpenMeter when real-time usage metering, product packaging, credits and entitlements are central to the product architecture.
Choose Verdix when the primary challenge is operationalising signed customer and partner agreements while retaining the existing finance stack.
OpenMeter measures and controls digital consumption. Verdix turns bespoke commercial agreements into approved financial workflows.