What's New — UoI block billing
Released on July 20, 2026
ToothFairyAI now bills organization plans by UoI blocks sized from actual consumption, rather than a fixed user (seat) count. The headline change: your billed capacity is no longer tied to maxUsers — it is derived from the Units of Intelligence your workspace actually consumes.
💡 UoI block billing
Consumption-sized billing
For Serverless and Enterprise plans, the number of blocks you are billed for is computed each billing cycle from your real usage:
Billed blocks = max(minimum blocks, min(round-up(consumed UoI ÷ UoI per block), maximum blocks))
- Floored at your plan minimum — every plan has a minimum number of blocks (Serverless: 5, Enterprise: 10).
- Capped at your plan maximum — consumption beyond the cap never inflates your invoice beyond the plan ceiling.
- No per-seat fees — unlimited users continue to work under the same block allocation; adding people never adds headcount fees.
Per-plan UoI per block:
| Subscription | UoI per block | Minimum blocks | Maximum blocks | Starting budget |
|---|---|---|---|---|
| Serverless | 5,000 | 5 | 100 | 25,000 UoI |
| Enterprise | 7,500 | 10 | Custom | 75,000 UoI |
Serverless (100 blocks / 500,000 UoI) has a fixed plan ceiling; Enterprise is custom and is arranged with your account team above the 10-block / 75,000 UoI minimum.
What changed in the product
- Billing now reads your family's aggregated
totalUoI(root + child workspaces) to size the billed blocks — the family rollup is the source of truth, with the root's own consumption as a fallback. - The in-app pricing step still lets you raise your allocation above the plan minimum. You still cannot reduce below the UoI you have already consumed in the current billing period.
- Enterprise customers retain custom UoI budgets and can increase above the minimum commitment by contacting support.
- Reserved-compute workspaces continue to be managed by contacting support, not in-app.
📖 Documentation: Units of Intelligence
Reliability
Usage pushes are now idempotent per billing period — the monthly cycle will not re-bill a workspace that was already billed this period, and lastBillingDate is only stamped after a successful Stripe usage push (so a failed push is retried on the next run).
Tales for the curious 🧚
You pay for intelligence consumed, not headcount — so a quiet month costs less and a busy month scales smoothly, all within your plan's floor and ceiling.