Meteroid Helps You Design Billable Metrics That Reflect Your Business Model

Usage-based billing only works if you can meter usage accurately—and that’s where Meteroid’s metering engine shines. Whether you're tracking API calls, storage consumption, seats provisioned, or custom events, Meteroid helps you define metrics once and use them across pricing, invoicing, and reporting.

What Is Metering?

Metering is the process of collecting, measuring, and recording how customers use your product over time. In Meteroid, billable metrics form the foundation for usage-based pricing.

Think of a metric as a stream of usage events—like “GB stored,” “messages sent,” or “support tickets resolved.”

How Billable Metrics Work in Meteroid

You send your product's usage data to Meteroid via API. Then, Meteroid aggregates this raw usage into billable metrics using logic you configure:

• What to count

• Over what period

• With what aggregation rule

Once defined, billable metrics become reusable building blocks across your Plans.

Aggregation Types Meteroid Supports

Each billable metric in Meteroid can be aggregated using the method that fits your business model:

Sum

Add up all usage events over the billing period.

Perfect for: API calls, emails sent, credits used.

Count

Count the number of events that occurred.

Perfect for: Support tickets, logins, app launches.

Max

Take the highest value recorded during the period.

Perfect for: Peak bandwidth, max storage used.

Min

Track the lowest recorded value.

Useful for SLAs or thresholds.

Last

Use the most recent value sent before invoicing.

Great for entitlements like "number of seats provisioned."

Unique Count

Count distinct users, sessions, or custom identifiers.

For true account-level or per-user pricing.

Need More Flexibility? Use Meteroid's Metric Segmentation Feature

For advanced use cases, Meteroid lets you segment metrics to apply different prices based on different attributes.

Types of Segmentation Meteroid supports:

• Single Dimension: Vary pricing by one attribute (e.g., Cloud Provider → AWS, Azure, GCP).

• Two Dimensions – Independent: Set prices for each combination of two indepedant attributes (e.g., Cloud Provider × Region).

• Two Dimensions – Dependent: Limit pricing to valid combinations (e.g., AWS only available in Europe and North America).

Try Meteroid’s Metering Engine

Whether you're just getting started or scaling usage-based pricing across segments, Meteroid makes it simple to meter, price, and monetize usage accurately.

👉 Start for free and define your first metric in minutes. Or explore the Metrics documentation to learn more.