Transportation
Tolling, transit and fleet systems produce trip events at scale and must share them with authorities under strict terms. UltraFabric keeps each party's rows in its own key range and checks every plan against it.
Workload shape
| Writes | Event streams from the road |
|---|---|
| Reads | Settlement, reporting, lookups |
| Tenancy | Operators, authorities, partners |
| Retention | Years, for disputes |
How the data lands
Design fit, not a customer claim: which parts of UltraFabric carry which parts of this workload.
- Trip, toll and telematics events as columnar collections
- Vehicles, contracts and accounts as rows; retried batches are idempotent
- Operators and authorities as tenants on one cluster
What it looks like
An authority's token reads the authority's tenant; an operator's reads the operator's. Neither can address the other's key range.
CREATE TABLE trips (id bigint PRIMARY KEY, plaza text NOT NULL,
at timestamp, class int, fee numeric(8,2)) WITH (storage = columnar);
SELECT plaza, class, count(*), sum(fee)
FROM trips WHERE at >= '2026-10-22' GROUP BY plaza, class;Built today, coming next
Everything in the first column is in the repository and tested; the second column is the roadmap in order.
Built today
- Row and columnar engines with answers equal to DuckDB's
- Primary keys unique per tenant; key lookups seek to one row
- Idempotent writes keyed by the client
Next
- Parallel reads at a snapshot
- Group commit for collection inserts
- The managed service after replication
Other use cases
Airports & Aviation
An airport runs many organisations on one estate: the operator, airlines, ground handlers, security and government agencies.
Smart Cities
A city platform collects from traffic, lighting, water, waste and safety systems, each owned by a different department, often with different vendors.
Power & Utilities
Grid operators keep two kinds of data that rarely live well together: dense measurement streams and slow-changing asset records.
Public Sector
Government platforms host many departments on shared infrastructure, each with statutory limits on who may see what.
Tell us about yours.
Early access starts with a conversation about the workload you would move first.