Daptin

Home / Product / Usage plans and metering

Admission and usage accounting.Usage plans and metering

Make finite product usage explainable.

Connect plan admission, reservations, measured cost, completion, and usage records in one request lifecycle.

See how it worksView the source ↗
Before workDecide whether the request belongs and fits.
During workKeep consumption tied to a product identity.
After workRecord actual usage and finish the reservation.
Why it matters

A limit is useful only when the whole lifecycle agrees.

A product that offers storage, provider calls, AI work, or another finite service needs more than a counter. It needs to know which plan applies, whether the person belongs to it, how much a request may cost, whether capacity should be reserved, and how actual use is recorded.

Carry the account, plan, reservation, measured cost, and completion record through one request. Expression-based costs can relate product inputs to usage while plan membership and quota state provide the customer context.

The intended result is an explainable product rule: why a request began or was declined, whose allowance it used, what it consumed, and what remains.

See the plan in motion

Follow each allowance from the plan to the customer’s activity.

These views show what a customer receives, what the product counts, and how the available amount changes as a feature runs.

Diagram showing a customer account connected to its subscription, plan, included allowance, activity history, and allowance balance.
How a plan becomes a customer allowanceA customer account receives a plan, an included allowance, an activity history, and a current balance.Open diagram for full-size view
Diagram showing customer activities flowing into plan allowances with renewal periods and limit behavior.
Choose what counts and when it renewsCount requests, files, AI use, connected-service updates, or business-specific units over a period you choose.Open diagram for full-size view
Diagram showing a plan check, an allowance hold, a requested feature, and the finished customer activity history.
Keep the balance accurate while a feature runsSet aside the expected amount, replace it with actual use, and return unused capacity when an activity stops or times out.Open diagram for full-size view
How metering fits

From promise to measured outcome.

Plan admission, reservations, measured cost, limits, completion, and usage records share one request lifecycle.

BelongPlan and membership

Relate an account or group to the product allowance intended for them.

AdmitQuota and expected cost

Decide whether finite work may begin before expensive execution starts.

MeasureUsage and dimensions

Record consumption in the terms the product understands.

CompleteReconcile the outcome

Close each usage reservation with measured cost and a recorded completion state.

Usage contract

Tie admission, reservation, measured cost, and completion to one plan.

Define plan membership, quota dimensions, cost expressions, reservation rules, completion behavior, and usage records on the backend. Each finite operation carries the account and plan that authorized it.

View the source ↗Explore AI workload routing →