Fleet, money and maintenance under control
Beyond the storefront, the platform is an operations tool. The admin console and a set of background workers keep utilisation high, revenue collected and every action auditable.
Track every physical unit through its life
Catalogue models are what customers see; fleet units are the physical assets. The two are linked so availability, allocation and maintenance stay consistent.
Unit inventory
- Per-unit records linked to a model
- Status & availability control
- Location / city assignment
- Association to the current rental
Allocation
- Assign a unit when a booking is approved
- Concurrency-guarded reservation holds
- Automatic hold expiry (worker)
- Release on cancellation
Maintenance
- Maintenance tickets per unit
- Damaged units kept out of allocation
- Repair requests from the portal
- Service state tracked over time
Revenue collected, deposits kept honest
The platform distinguishes earned rental revenue from refundable customer deposits, and automates recurring billing so the operator does not chase periods manually.
Recurring billing
A billing worker advances rental periods and issues charges on schedule.
Invoices
Invoice generation with server-rendered PDFs, downloadable from the portal.
Deposits
Refundable deposits recorded as a liability, reconciled at return — never counted as revenue.
Expenses & metrics
Expense tracking plus revenue, custody and accessory metrics for the operator.
Background workers do the repetitive work
Four scheduled workers keep the operation moving without manual intervention. They are revenue-critical and operational, and run independently of the customer-facing surface.
| Worker | Cadence | Responsibility |
|---|---|---|
| Rental billing | Daily | Advances rental periods and raises recurring charges (revenue-critical). |
| Return reminders | Twice daily | Notifies customers of upcoming returns (operator-toggleable). |
| Hold expiry | Hourly | Releases expired reservation holds back to available inventory. |
| Email outbox | Per minute | Reliable, retried delivery of transactional & operational email. |
Auditable, rate-limited and access-controlled
Audit logging
Sensitive operations are recorded to an audit log for traceability and accountability.
Access control
Admin access is JWT-authenticated; the admin token is attached server-side and never exposed to the browser.
Rate limiting
Sensitive public endpoints (booking, waitlist, payments, portal actions) carry a strict rate-limit policy.
See the operations console live
Book a private demo to walk the fleet, billing and maintenance surfaces on the running system.