The canonical vocabulary of the Bituser platform. Every capability is named once — as a Solution, Product, Feature, or Usage — and that name reads the same on the website, the rate card, and the usage statement.
Containment runs Solution ⊃ Product ⊃ Feature ⊃ Usage. A Solution is the one conceptual term — what a customer buys; the other three are system identifiers that name a Product, a Feature, and a Usage. Classification rides inside each term as a tag — Type on a Solution, IaaS / DaaS on the rest — never as a level.
A named group of ProductIDs delivering one customer outcome. It carries a Type that classifies its shape and sets the leading glyph and tag.
| type | classifier of the Solution's shape |
| contains | one or more ProductIDs |
| delivers | one customer outcome |
| named | source → destination |
The identifier for a Product — the buyer-selectable unit within a Solution. A Product contains one or more Features and emits metered Usage.
| identifies | a Product |
| class | IaaS / DaaS |
| contains | one or more Features |
| emits | metered Usage |
The identifier for a Feature — a reusable action a Product performs. One or more Features make up a Product, and a Feature is shared across Products wherever the same action recurs.
| identifies | a Feature |
| is | a reusable action |
| belongs to | one or more Products |
| example | 20081 · Action Page Visit |
The identifier for a Usage — the metered event and billing unit. Each Usage carries a Disposition (see §02) that, on a statement, sets its color.
| identifies | a Usage |
| class | IaaS / DaaS |
| carries | a Disposition |
| bills | on OK · SU or MA |
Disposition is a dimension on the Usage, held separately from the identifier so the event name stays stable and the outcome reads on its own. Every metered event resolves to one of four codes. OK = {SU, MA} is the billable grouping: only OK bills; NO and EX never do. A Solution carries a Type; a Usage carries a Disposition — the two never share a name.
One token, nested in context. Every tier is the same tag — icon plus name — told apart by color, not typeface. The Solution is the sellable outcome, carried on a rounded blue pill; its Products, Features, and Usages are rectangular metered building blocks nested inside it. Each Feature collapses to its billable line; expand it to see every Disposition. This is the reusable card that renders each Solution at /solutions/.
UAIID = User Agent Instance ID.
Each Feature collapses to its billable line — expand it to see every Disposition (SU · MA · NO · EX). Service and Disposition are independent dimensions.
Billing follows Disposition, not the identifier. A Usage bills only on a Success (SU) or Match (MA) disposition. NO and EX never bill.
This page defines how Usage bills. Rates, the billing floor, estimates, and the calculator live on /pricing — because the match rate is not one-to-one, unit prices can't be summed into a total here without misrepresenting cost.
Every tier is the same tag — an icon and a name — told apart by color, not typeface: Solution blue, Product purple, Feature amber, Usage green. The identical tag renders in the legend, the definitions, and the card.
A rounded pill is a sellable outcome — the Solution. Rectangular blocks are metered building blocks — Product, Feature, Usage. Shape tells apart what a customer buys from what the platform meters.
Type classifies a Solution; IaaS / DaaS classify Products and Usages; Disposition classifies a Usage. They ride inside a term as a tag — never as a level. Containment is Solution ⊃ Product ⊃ Feature ⊃ Usage.
A Feature is shared across Products wherever the same action recurs — the platform's cluster-for-reuse.
Disposition is independent of the pillar: SU and MA are green (both OK, both billable), NO is amber, EX is red. An IaaS Usage may carry MA and a DaaS Usage may carry SU; only the Disposition decides billing.
Each Solution, Product, Feature, and Usage is named once. The website, rate card, and statement all reference that name — and every reserved word owns an icon, reusable as a facet.
One term, three surfaces. The pill that labels a Product on the website is the same defined term that appears on the rate card and lines on the usage statement.
Labels each capability by Solution and its Type.
Lists each identifier by Type, Service, and Disposition.
UsageIDs render as lines, billed only on a Success or a Match.