← Units360.ai
Units360 · Co-working Space
ACT 1 OF 5
Define Units & Conversion Rules
1 billing unit · 3 service units · conversion table
WORKNEST CO-WORKING · FLOOR PLAN WorkNest Acme Design 100 cr CHECK-IN Check-in Desk A Desk B Desk C Conference Room Printer
How it Works
🏢 WorkNest IDLE 🖥️ Booking Sys READY ⚡ Units360 API READY 🪙 Credit Ledger 100 cr 🔄 Conversion RULES 🧾 Invoice PENDING
Credits Used
0
of 100 total
Balance
100
credits remaining
Desk Hours
0
hrs used
Room Hours
0
hrs used
Print Pages
0
pages printed
Define Customer Uses Month Summary Rate Change Invoice
WorkNest · Units360 Terminal
SETUP
🪙 Unit Definitions (4 units)
credit
hot_desk_hour
conference_room_hour
print_page
🔄 Conversion Rules
1 credit =
1 credit =
1 credit =
effective
🪙 credit · hot_desk_hour · conference_room_hour · print_page1 billing unit · 3 service units · acme-design
🔄 1cr=1desk·hr · 1cr=30min·room · 1cr=10pagesMay 2024
💡 WorkNest uses Credit as a Billing Unit. They define 3 service units — hot_desk_hour, conference_room_hour, and print_page. A Conversion Table maps each service unit to credits. Change a rate once; all invoices apply it automatically.
🐢 Speed:1× 🐇
Space · ← → · R · ? Guide
Platform Guide · Co-working Edition
Units360? WorkNest Credits Service Units Accounts Transactions Conversions Configuration Processing
Platform Overview
🚀What is Units360?

Units360.ai is a low-code usage metering platform. Define any measurable unit — tokens, credits, kWh, API calls, hours — and the platform auto-provisions the ledger, billing APIs, and invoicing logic instantly.

In this demo, Credit is the Billing Unit. WorkNest defines 3 service units — hot_desk_hour, conference_room_hour, and print_page. A Conversion Table maps each service unit to credits. When WorkNest changes a rate, all future invoices pick it up automatically.

1. Define
Config
→
2. Deploy
Engine
→
3. Stream
Events
→
4. Invoice
Auto
No DevOpsCredit ledgerRate versioningAuto-invoice
Use Case
🏢WorkNest — Co-working Space

WorkNest sells monthly credit packages to businesses. Acme Design buys 100 credits/month. Credits are the Billing Unit — a Conversion Table maps them to service units: 1 hot_desk_hour = 1 credit, 1 conference_room_hour = 2 credits, 1 print_page = 0.1 credits.

As demand grows, WorkNest can change conversion rates (e.g. conference rooms become more expensive) without rebuilding any billing infrastructure.

Company
WorkNest — co-working space operator
Customer
Acme Design — 100 credits/month plan
Billing unit
credit — internal currency
Services
hot_desk_hour, conference_room_hour, print_page — mapped to credits via Conversion Table
Core Concept
🪙Credit — The Billing Unit

A credit is an abstract billing unit. Customers pre-purchase credits; services debit them. This decouples the customer's billing experience from the underlying service pricing.

WorkNest can change service rates (credits required per service unit) without re-negotiating customer contracts. The credit price stays the same; the conversion rate changes.

"unit_id": "credit",
"type": "BILLING_CURRENCY",
"account": "acme-design",
"balance": 100, // monthly plan
Pre-purchasedConvertibleRate-versioned
Service Units
🔄Service Units — What Credits Buy

Each service at WorkNest is also a Units360 unit. When a customer uses a desk or books a room, the booking system records the usage. Units360 converts the service usage to credits and debits the account.

hot_desk_hour
1 credit per hour at any desk
conference_room_hour
2 credits per hour (May rate; updated to 4 cr/hr in June)
print_page
0.1 credits per page (10 pages = 1 credit)
Rate versioning: when WorkNest changes conference_room_hour to 4 credits/hour in June, all June invoices apply the new rate. May invoices are already locked at the old rate. No manual recalculation.
Core Concept
🏦Account

An Account is a billing entity — a customer, team, or cost centre. Each account has a balance per unit. For WorkNest, Acme Design's account tracks their credit balance and sub-balances per service.

account_id
acme-design
credit_balance
starts at 100, decrements on usage
plan
100 credits / month, renews monthly
Core Concept
⚡Transaction

Every service usage event creates an immutable Transaction in the ledger. Each transaction records the unit, quantity, credits debited, and the conversion rate at the time of the event — ensuring accurate historical invoicing.

{
"unit": "hot_desk_hour",
"qty": 1,
"credits_debited": 1,
"rate_applied": "2024-05-01",
"account": "acme-design"
}
Platform Feature
🔄Conversion Rules

Conversion Rules define how service units translate to credits. They are versioned by effective date — a rate change creates a new rule version without invalidating historical records.

"conversions": [
{ "service": "conference_room_hour", "credits": 2,
"effective": "2024-05-01" },
{ "service": "conference_room_hour", "credits": 4,
"effective": "2024-06-01" } // new
]

Units360 applies the correct version for each billing period automatically. No retroactive changes. No manual overrides needed.

Platform Component
📋Configuration

The configuration defines your entire metering model: units, accounts, conversion rules, alert thresholds, and billing periods. Submit once; Units360 handles everything else.

Declarative YAML/JSONVersion-controlledZero-DevOps deploy
Platform Component
⚙️Real-Time Processing

Units360 processes every usage event in real time: validates the event, applies the correct conversion rule version, debits the account, and updates all ledger balances atomically — all under 50ms.

Rate changes take effect immediately. When WorkNest updates the conference room rate, Units360 picks up the new rule for all events timestamped on or after the effective date. Historical transactions are never modified.