Kong expands into usage billing

This shows Kong is turning billing into a stand alone product line, not just an add on for API gateways. The important shift is that Kong can now sell to any company that charges by usage, whether the unit is tokens, minutes, seats, storage, or events. That widens the market from API teams to any software company that needs to meter consumption, apply credits and plans, and turn raw product activity into invoices or internal chargebacks.

• The product came from Kong's September 3, 2025 acquisition of OpenMeter. OpenMeter was built as a general usage metering and billing system, with support for plans, credits, invoicing, and Stripe integration, so it naturally fits non API workloads as well as API traffic.
  1 prnewswire 4 openmeter 5 openmeter
• In practice, non API customers are still solving the same problem. They stream product events like model tokens, video minutes, compute time, or workflow runs into a meter, aggregate them into billable units, then apply pricing rules, prepaid balances, and overages before sending charges to a payment system.
  2 sacra 4 openmeter 6 sacra
• The competitive set is broader than API infrastructure. Kong is now entering the same buying motion as Orb, Metronome, Lago, and Stripe, where the winner is the system that can handle messy real world pricing, like tiered rates, hybrid seat plus usage plans, credits, and finance system sync, not just count API calls.
  2 sacra 3 sacra 6 sacra 7 stripe

The next step is clear, Kong will keep moving up from traffic control into revenue control. As it adds credits, auto refill, more payment connectors, and deeper entitlement logic, billing becomes a wedge into product and finance teams first, then a path to pull those customers into Kong's API and AI gateway stack later.