Blog

OpenMeter is joining Kong to accelerate AI and API monetization and billing. OpenMeter Cloud continues to operate as usual for existing and new customers.

OpenMeter separates usage owners (subjects) from billing entities (customers). That design stays, but the subject API is deprecated in favor of customers.

OpenMeter explains its new pricing strategy: pay only for what you use, with automatic volume discounts that support growth instead of punishing it.

Add-ons let customers extend a base plan through self-service, whether bundled or cross-sold. OpenMeter's no-code product catalog now supports them.

Outcome-based pricing ties payment to results instead of work done. Compare it with usage-based pricing and see when each model fits your product.

OpenMeter Collector with event buffering and automatic recovery from network failures with persistent storage support. Never lose an event.

OpenMeter's collector now meters Kubernetes Pod, CPU, memory, and storage allocation seconds, so you can bill customer workloads accurately.

Open source remade infrastructure like operating systems, containers, and observability. Billing, still closed and proprietary, is next in line.

OpenMeter's collector now supports Run:ai, so you can meter GPU, CPU, and memory allocation for Kubernetes AI workloads and bill for it accurately.

OpenMeter Billing is built for flexibility and easy pricing changes. Combining with Stripe Payments, you can automate revenue collection.

OpenMeter Invoicing provides detailed breakdowns for multiple line items, accurate totals, and up-to-date invoice previews throughout the billing period.

OpenMeter's subscription management supports self-service signups and custom enterprise deals on one billing platform, without separate systems for each.

OpenMeter's no-code product catalog lets non-engineers launch products, change pricing, and package features instantly, without waiting on developers.

Launching OpenMeter Billing and the No-Code Product Catalog to allow pricing changes without developer involvement and making billing easy for developers.

AI companies have tried pay-as-you-go, credits, and commitments to find the right model. How AI pricing evolved and the tradeoffs each approach carries.

Why OpenMeter adopted TypeSpec, a Microsoft project for describing APIs, to generate OpenAPI schemas, clients, and docs across OpenMeter OSS and Cloud.

OpenMeter has successfully completed the SOC 2 Type II audit, signifying our commitment to rigorous security standards.

Use Dagger to achieve isolation and reproducibility with Helm, including running linters, tests, and pushing to a registry.

How to balance accuracy, auditability, real-time processing, and cost when building a metering system for usage-based billing, and pitfalls to avoid.

We accelerated our CI pipeline from 25 to 5 minutes and reduced costs by 50% using Dagger's caching mechanisms and Depot's custom runners.

OpenMeter Notifications alert customers when usage or entitlement balances cross thresholds like 75% and 100%, helping prevent overage surprises.

OpenMeter's first product designer on joining a startup pre-product-market fit, shaping design from day one, and staying in love with the craft.

OpenMeter's OpenTelemetry Log Collector extracts usage information from your logs and forwards it to OpenMeter for billing and cost management.

OpenMeter's Free Forever Plan is live: meter up to 1M events, use entitlements and Stripe billing, with no credit card required to get started.

OpenMeter's Edge Access, now in private beta, enforces usage limits and entitlement balances with low latency across a globally distributed data plane.

Usage grants support expiration, priorities, recurrence, and rollovers, enabling scenarios like granting customers 10M monthly token usage.

OpenMeter's new entitlements feature allows you to manage customer feature access, balances, and usage limits.

When your infrastructure can't effectively follow pricing changes, you lose the ability to iterate on pricing quickly and give up a competitive edge.

OCI tools like Helm store credentials on the filesystem in plaintext. It poses a security risk that is easy to overlook.

Credit-based pricing is increasingly popular among AI products. It helps mitigate high upfront costs and manage vendor and customer expenses.

Pricing AI products is hard given high cost of goods and heavy automation. See how AI companies use usage-based pricing, credits, and prepaid billing.

The top five challenges companies face adopting usage-based pricing, from entitlements and customer communication to sales strategy and cost management.

From LLM tokens to API calls, a look at the most common usage metering use cases OpenMeter customers implemented in 2024, and how they set them up.

OpenMeter raised a $3M seed round from Y Combinator, Haystack, and Sunflower Capital to standardize usage metering and enable AI monetization.

Whether you need a metering system depends on two things: your usage volume and the use cases you build on top of aggregated usage data.

Feature announcement of subject display names, webhook usage sync filters, and new collectors for Postgres and ClickHouse

OpenMeter's Consumer Portal and React SDK let you build a real-time usage dashboard so customers can track consumption and control spending.

OpenMeter's FinOps unit economics solution enables companies to attribute shared costs to customers and internal teams.

OpenMeter's Kubernetes Usage Collector meters container CPU time and pod execution time for per-second billing of workloads on Kubernetes.

OpenMeter's native Stripe integration syncs usage-based billing for AI, API, and infrastructure consumption like logs, Kubernetes, S3, and databases.

Unit economics and rate cards can ensure that engineering efforts align with strategic business objectives and drive sustainable growth.

How OpenMeter's open-source Redpanda Connect plugins ingest usage data from databases, logs, Kubernetes, and any cloud vendor for accurate billing and FinOps.

OpenMeter's production-ready Kubernetes Helm Chart deploys metering infrastructure with a bring-your-own-databases option for Kafka and ClickHouse.

Differences between tiered pricing model, volume-based pricing model and tiered pricing strategy and how they work.

FinOps Unit Economics and Rate Cards help to attribute shared costs and create a contract among teams providing services to each other.

Key API Monetiztion strategies, covering models like Subscription, Usage Based Pricing, and Pay-Per-Transaction.

Essential components of a great customer usage dashboard and exploring what leading companies are doing in this domain.

OpenMeter launched on Product Hunt and placed 1st Developer Tool of the week and 2nd Product of the day. Read the backstory behind the launch.

Businesses with tiered or usage-based pricing, especially in the AI and DevOps sectors, need to shield their profit margins from undue overuse.

Our journey from Kafka Connect to building a robust and scalable Kafka to ClickHouse sink by implementing a Kafka Consumer worker in Go.

How OpenMeter uses Redpanda Connect to generate realistic sample usage data, formatted as CloudEvents, to test stream processing at scale.

Cost Per Transaction and Rate Cards helps Finance and Engineering to speak the same language and leads to higher cloud savings, and better outcomes.

How to meter LLM token usage with OpenAI's streaming API and the Vercel AI SDK in Next.js, since streamed responses don't return token counts.

Explore how OpenMeter utilizes ClickHouse and Kafka Connect for robust usage metering to power accurate analytics and billing.

OpenMeter Cloud beta is live: a fully managed, highly available metering service with real-time data, a UI for meters, and secure Google or GitHub login.

Implementing robust Stripe usage reporting that can withstand rate limits and errors for accurate usage-based billing.

Usage-based pricing can grow Net Revenue Retention through organic account expansion and reduced churn. Here's how NRR works and how to calculate it.

Turning application logs into usage with Vector for usage-based billing. Useful in serverless environments like AWS lambda where integrating SDKs is challenging

Guide to avoid overcharging customers with usage-based billing by double counting your usage data. By implementing an idempotent stream processing with Kafka.

A deep dive into metering OpenAI API and ChatGPT token usage, so you can accurately chargeback customers and power usage-based billing for AI features.

Comparing lifecycle event and heartbeat driven metering to measure CPU Hours of containers, pods, and serverless on second granularity.

What makes usage data auditable versus operational, and why choosing between event-driven metering and time-series metrics matters for billing and FinOps.