April 2025 Summaries

The text discusses outcome-based pricing, a pricing model that aligns payment with results. Unlike usage-based pricing, where customers pay for work done regardless of outcome, outcome-based pricing charges only when the desired result is achieved. This approach builds trust and ties revenue directly to customer success. However, defining what counts as a successful outcome can be challenging, especially in cases where the outcome's context is ambiguous or uncertain. The model also introduces complexities such as delayed billing events, attribution challenges, and revenue collection and recognition issues, which require careful consideration from finance teams.

The OpenMeter Collector now supports event buffering, allowing it to retain events on a persistent volume during network failures and re-deliver them once network connectivity is recovered. The collector can be installed in infrastructure and points the OpenMeter SDKs to enhance resilience and meter various usage data sources. With event buffering enabled, the collector provides visibility into buffer and processing states through Prometheus metrics, ensuring each event is processed once and exactly once. To get started with event buffering, install the OpenMeter Collector and point your SDKs to it, following a simple two-step process. This feature helps prevent revenue leakage caused by network issues and ensures that never an event is lost.

The OpenMeter collector is a standalone application that can be installed in a Kubernetes cluster to meter resource usage, such as Pod runtime CPU, memory, and storage allocation. This release supports metering of Pod, CPU, Memory, and Persistent Volume allocation seconds for Kubernetes workloads, allowing users to monetize customer workloads running on Kubernetes. The collector also supports converting Prometheus metrics to metered usage and importing usage from various databases. OpenMeter collects detailed resource usage from Kubernetes workloads, including Pod Allocation Time, CPU Core Allocation Time, Memory Gigabyte Allocation Time, GPU Allocation Time, and Persistent Volume Allocation Time. This data can be used for cost visibility, chargebacks, and metered billing. The system also provides a no-code catalog to price each resource, generates invoices automatically after usage, and supports enterprise contracts with tiered pricing or commitments.