Overview
OpenMeter Billing is currently in private preview - to request access.
Implementing and maintaining pricing and packaging is cumbersome and time-consuming. OpenMeter provides a flexible product catalog and billing system to define plans, provision custom deals, manage subscriptions, and handle invoicing so you don't have to hard code pricing in your application.
With OpenMeter, you can define a set of metered or non-metered features, add them to plans, define prices, access and usage limits, and assign them to customers. OpenMeter will automatically track usage, enforce limits, and generate invoices.
Plans are versioned and can be updated without affecting existing subscriptions.
Use Cases
OpenMeter billing can help to implement various pricing strategies:
| Use Case | Description |
|---|---|
| Recurring Billing | Monthly, weekly or annual subscriptions. |
| Usage-Based Pricing | Metered pay-as-you-go, tiered and volume-based pricing. |
| Custom deals | Custom pricing and discounts for specific customers. |
| Commitments | Pre-purchase commitments, minimum spends, etc. |
| Trials and ramp-ups | Time-based phases with different pricing and limits. |
| Discounts | Plan or customer-specific discounts. |
Core Entities
Billing is built around the following core entities:
| Entity | Description |
|---|---|
| Feature | A metered or non-metered feature like AI Tokens, SAML SSO, etc. |
| Plan | A plan is a versioned collection of rate cards like Pro plan. |
| Rate Card | A rate card is a feature and its pricing with optional limits. |
| Customer | A customer can subscribe to plans and have access to features. |
| Subscription | A subscription is a plan and rate cards assigned to a customer. |
| Invoice | An invoice is a bill for a customer based on their usage and plan. |