OpenMeter

OpenMeter Cloud is now Konnect Metering & Billing. The separate OpenMeter open-source project remains available. Choose the deployment deliberately: the project is software you operate, while Konnect provides an account-based hosted product.

OpenMeter measures incoming events and associates them with a customer's usage. Plans attach prices and allowances to features, and subscriptions assign those terms to customers. Versioned plans can change without automatically changing existing subscriptions.

Feature allowances can represent a measured balance, a simple on-or-off permission, or a customer-specific configuration. A token allowance, for example, needs both a recorded consumption figure and an application check that prevents further use when the balance is exhausted. Your application remains responsible for enforcing the access decision.

For local evaluation, the repository supplies a Docker Compose stack with a sample request meter. A developer can send an event and query its measured value through the local programming interface (API), without a vendor registration. The project does not bundle an operator interface, payment processor or general accounting system.

Moving from usage to a bill in Konnect

The hosted setup requires a Konnect account and appropriate Metering & Billing permissions. An ingestion token authenticates usage submissions. After configuring the meter, go to Metering & Billing > Product Catalog > Create Feature and connect that feature to the relevant meter and filters.

Create a plan, add a rate card with the feature and its price, then publish it. Under Billing, create the customer and map the customer identifier to the usage source. Assign a subscription to the plan. Metering traffic alone does not establish these commercial terms.

The open-source edition has no software license fee, but hosting and connected providers cost separately. Hosted pricing and allowances should be confirmed through Kong's current offer.

OpenMeter's releases are marked beta and may introduce breaking changes. Plan upgrades carefully. The project is most useful when measured consumption and access rules are central to the product, rather than incidental invoice fields.