The output
Registers & the dashboard builder
The heaviest single piece of engineering on the platform this year, and the least visible: a reporting layer that lets a customer build their own view without asking us for a release.
The usual arrangement is that every new report is a request, a specification, a queue position and a release. Six weeks for a column. It is the single most reliable source of frustration in enterprise software, and the reason so many operations teams run the real business in a spreadsheet exported at 6 a.m.
The platform inverts it. Registers are configuration over columnar storage rather than hand-written queries, and above them sits a builder where a customer assembles their own dashboard. When the person who needs the number can build the view, the six-week queue disappears.
The register engine
Configuration, not queries
Registers are defined as configuration rather than written as queries, so a new register is a config entry and behaves consistently with every other one.
Columnar storage underneath
Registers run over a columnar store rather than against the transactional database. Heavy operational reporting stops competing with the system people are trying to work in.
A library of operational registers
Trip, shipment, partner, exception, LTL and FTL daily registers ship with the platform as the operational backbone most customers start from.
Consistent export
Every register exports the same way. The spreadsheet a finance team wants is a download rather than a favour.
The dashboard builder
The builder works over the register layer, so a measure that is not in a register is not yet available to build with. Extending the register set is a configuration change on our side rather than a release, but it is still a step.
The rest of the Control Tower
See it running on your operation
A working session over your own fleet, lanes, partners and SLAs — not a slide deck.