Skip to content

Knull Network

Where mobility becomes infrastructure.

The network is the topology of Knull: where docks sit, how units circulate between them, and how a destination becomes covered. The platform is how that network is operated.

01The progression

One unit is useful. A network is infrastructure.

  1. 01

    One connected unit

    A trolley that knows its identity, condition and whether it is in a session. Useful — but on its own, a product.

  2. 02

    Fleet

    Many units released, returned and maintained as one pool. A fleet is a service: it has availability, not just inventory.

  3. 03

    Dock cluster

    Docks anchor the fleet to a place. Custody, charging and access become fixed infrastructure in a zone.

  4. 04

    Destination network

    Clusters across entrances, levels and car parks act as one system. Availability follows how people actually move.

  5. 05

    Multi-destination infrastructure

    The same standard repeats across an estate, so owners compare, plan and operate destinations consistently.

02A destination, through a trading day

Explore an illustrative destination network.

Switch level, layer and time of day to see how dock occupancy, demand, charging and service shift through a day. The destination and every figure are hypothetical.

Illustrative deployment modelHypothetical destination · not live data
Level
Layer
Time of day
N-013/8E-012/8C-016/10

13:00 · Ground

Midday peak. Entrance clusters draw down; atrium and food-court docks fill with returns.

Units docked, all levels
40 / 72
Docks on this level
3
  • N-01 · North entrance3/8
  • E-01 · East entrance2/8
  • C-01 · Central atrium6/10

03Topology principles

How a network is shaped.

  • Start where journeys start

    Clusters sit at entrances, car-park lobbies and transit links — the points where visitors arrive with free hands.

  • Follow vertical movement

    Lift lobbies and level transitions are where carrying becomes hardest, so they carry docks.

  • Return where journeys end

    Return capacity follows exits and parking, so units come back to where they will next be needed.

  • Balance, don't overbuild

    A network is sized to peaks it can rebalance between, not to the worst hour at every dock.

  • Isolate faults

    A zone that loses connectivity is isolated; the rest of the network keeps operating.

  • Repeat across an estate

    A consistent dock standard lets the same playbook run in every destination.

Network is topology. Platform is operation. Together they are the system.

Next step

Map a network against your destination.

Tell us about your levels, entrances and footfall; get an indicative view of dock distribution and fleet size.