One visual grammar for the platform taxonomy — built so a token reads the same on the website, the rate card, the usage statement, and the Order Form.
Anchored to the blue Bituser already publishes (#5491E6, the site theme color). Blue carries the infrastructure-and-trust register that fits user data infrastructure, so it owns the one conceptual tier — Solution. The three system-identifier tiers stay neutral. One ramp, used with intent.
#5491E6 is too light to carry white text at pill sizes (≈3.3:1, below the 4.5:1 bar). The solid Solution token drops one stop to #2E63B4 (≈5.8:1, passes AA), while the exact published hex lives on as the bright accent on light backgrounds — so the brand color is preserved, just placed where it stays legible.
Containment runs Solution ⊃ Product ⊃ Feature ⊃ Usage. The spine is the typeface flip — sans for the one conceptual tier, monospace for the three metered system identifiers. Classification (Type on Solution, IaaS / DaaS on the rest) rides inside the token as a tag, never as a level.
The sellable unit, named source → destination. Carries a Type classifier (Pipeline today; others later) that sets both the leading glyph and the tag.
| typeface | Manrope · sans, Sora · display |
| size / weight | 16px / 500 |
| fill | #2E63B4 (brand-600) |
| text | #FFFFFF · arrow #A8C8F4 |
| radius | 999px (full pill) |
| classifier | Type tag (brand-200) + white divider |
The atomic ProductID, classified IaaS or DaaS. Monospace begins here. A Product is composed of one or more Features and emits its own match Usage.
| typeface | IBM Plex Mono · mono |
| size / weight | 13px / 500 |
| fill | #FFFFFF |
| text | #1B1B17 (ink) |
| border | 1px solid rgba(27,27,23,.13) |
| radius | 6px (chip) |
| classifier | IaaS / DaaS tag + divider rule |
The FeatureID — one action a Product performs. Documented and agreement-grade, but the quietest token: dashed, muted, hidden on customer surfaces initially. Shared across Products, which is the cluster-for-reuse — so no Blueprint tier is needed.
| typeface | IBM Plex Mono · mono |
| size / weight | 12.5px / 400 |
| fill | transparent |
| text | #6B6A62 (muted) |
| border | 1px dashed rgba(27,27,23,.24) |
| radius | 6px |
| visibility | internal-first · billing & agreements |
The metered UsageID — an IaaS product-match or a DaaS microtransaction. Smallest, recessed, telemetry register. The leading dot marks an event; in a statement it takes the outcome color.
| typeface | IBM Plex Mono · mono |
| size / weight | 12px / 400 |
| fill | #F3F2EB (panel) |
| text | #3A3A34 |
| radius | 6px |
| classifier | IaaS / DaaS tag + event dot |
| outcomes | match no_match error |
One Solution, two Products, their reusable Features, four UsageIDs. Each IaaS Product emits its own match event and the DaaS microtransaction it triggers — four billable lines.
Same format as the live pricing page — Type · Service · Product / Feature / Usage ID · Cost / Call — extended with counts and amounts for the client rollup. The tokens that label the platform become the line items.
| Type | Service | Product / Feature / Usage ID | Cost / Call | Amount |
|---|---|---|---|---|
| IaaS | User from Page · match | $0.0020 | $24.96 | |
| DaaS | Cookie to Hash Email | $0.0100 | $93.60 | |
| IaaS | User to Email · match | $0.0015 | $13.37 | |
| DaaS | Hash Email to Email | $0.0100 | $89.10 | |
| Website Visitor → Email | $221.03 | |||
Platform minimum $2,000/mo · then usage-based · all prices in USD · figures illustrative
Rates for IaaS and DaaS services are variable and may be updated at any time. A statement reflects current rates as of its issue date.
ProductIDs, FeatureIDs, and UsageIDs are the canonical identifiers referenced in the service agreement, and are subject to automated updates from the Bituser platform feed.
Sans = conceptual, customer-facing (Solution). Mono = a real metered identifier (Product, Feature, Usage). The flip is the strongest cue — preserve it above all else.
Solid → outline chip → dashed ghost → recessed panel. Prominence falls as you move from what is sold toward what is metered.
Pipeline is a value of Solution.Type; IaaS / DaaS classify the rest. Tags inside a token — never a level. Containment is Solution ⊃ Product ⊃ Feature ⊃ Usage.
Features are shared across Products — the platform's cluster-for-reuse. That removes any need for a Blueprint tier above Products.
One object, four surfaces. This spec is the source; each surface conforms to it. The pill that labels a Product on the website is the same defined term that prices on the rate card, lines on the usage statement, and is referenced in the Order Form.
Labels by Solution and its Type; Feature stays hidden initially.
Type · Service · Product / Feature / Usage ID · Cost / Call.
UsageIDs render as lines with counts and fees.
The canonical IDs are the defined contract terms.