The system
Not a trolley connected to an app.
Knull is a managed physical-digital infrastructure system. Connected units, docks, a destination-wide network, an operating platform and the people who run it — designed together, so each layer knows what the others are doing.
01The Knull Infrastructure Stack
Seven layers. One accountable system.
Select a layer to see what it does, what it consumes and produces, how it behaves when something fails, and what operators can see.
Layer 02
Mobility
The connected unit that carries purchases and belongings. The Knull Trolley is the first endpoint; the layer is designed so further endpoint types can join the same infrastructure in future.
Future endpoint types are an architectural allowance, not current products.
- Inputs
- Release command from the dock · Visitor handling
- Outputs
- Unit identity and condition · Session state
- Failure behaviour
- A unit reporting a fault is withdrawn from availability and flagged for service.
- Depends on
- Infrastructure · Operating
- Operator visibility
- Every unit, its location state, condition and service history.
- Explore
- Go to mobility →
02How value compounds
One unit is useful. A connected network is infrastructure.
The same architecture carries a single dock cluster or a destination-wide network. Nothing is rebuilt as the deployment grows — it is extended.
- 01
Connected unit
A trolley that knows its own identity, condition and session state.
- 02
Managed fleet
Units become a service once they are released, returned and maintained as one fleet.
- 03
Dock cluster
Docks anchor the fleet to a zone: custody, charging and access in one place.
- 04
Destination network
Clusters across levels and entrances become a single availability picture.
- 05
Multi-destination
The same platform runs several destinations with consistent standards.
03Design principles
Built the way infrastructure is built.
Local-first
Custody and core release logic sit at the dock, so the service does not depend on a round trip to the cloud for every action.
Known-safe failure
When a layer degrades, the system reports what it cannot see and withdraws affected units rather than guessing.
Modular by layer
Each layer has a defined interface, so docks, units and software can be serviced or upgraded independently.
Operated, not installed
The operating layer and service model are part of the system — availability is maintained, not assumed.
Aggregate by default
Reporting works on aggregate, non-personal session data. Analytics never sit in the release path.
Designed for integration
Interfaces are scoped per deployment, so Knull coexists with the systems a destination already runs.
Intelligence and integration layers describe architecture and intent. Forecasting, optimisation and specific third-party integrations are not presented as available until confirmed for a deployment.
Next step
Model the system against your destination.
Test fleet size, dock distribution and service capacity with your own assumptions — then plan a pilot.