Steora sells Solos. This is the one gap software can close before hardware exists.
Canopei Fleet is the named platform a buyer logs into: nine metrics per bench, a defined telemetry frame over the EN/ABEL mesh, offline buffering, and three tiers with the public uptime page free forever. The dashboard below is built and demonstrable now. It is running on a simulated estate, labelled as such on every panel, and the working scale prototype feeds the identical schema with measured values.
9
Metrics per bench, defined
Verified44 B
Telemetry frame, no personal data
Verified30 days
Offline buffering in local flash
CommittedThe dashboard, finished before the first bench ships.
Everything below is the real interface running against a simulated eight-bench estate, so an operator can see exactly what they will get. Nothing here is a picture of a dashboard; it is the dashboard.
Simulated estate · 30-day window
98.4%
Mean uptime
293.0
kWh harvested, 30 days
96%
Of modelled yield
1900
Charge sessions delivered
70.1
kWh delivered to devices
47
Charging shed events
| Site | Uptime | kWh in | vs model | Sessions | kWh out | SoC | Shed | Status |
|---|---|---|---|---|---|---|---|---|
| Ancoats, Cutting Room SquareOpen square, sky-view factor 0.94 | 99.7% | 41.2 | 98% | 318 | 11.4 | 78% | 2 | Nominal |
| Levenshulme, high street paradeHighest session count in the estate | 99.2% | 33.8 | 95% | 402 | 14.9 | 64% | 6 | Nominal |
| Salford Quays, waterfront walkAbove model, low overshadowing | 99.9% | 44.6 | 103% | 265 | 9.8 | 86% | 0 | Nominal |
| Stockport, Underbanks76 percent of model, soiling or new shading, inspection raised | 97.4% | 24.1 | 76% | 188 | 7.2 | 41% | 14 | Watch |
| Bolton, Victoria SquareCanopy lighting extending trading evenings | 99.5% | 36.9 | 99% | 291 | 10.6 | 72% | 3 | Nominal |
| Wigan, Believe SquareNominal across all subsystems | 99.6% | 35.2 | 98% | 233 | 8.7 | 75% | 1 | Nominal |
| Oldham, Union StreetUSB-C face 2 reporting ingress fault, part dispatched, seat still in use | 92.1% | 29.4 | 84% | 141 | 5.1 | 33% | 21 | Fault |
| Marsden Moor trailheadBeacon reserve never breached, charging shed zero times | 100.0% | 47.8 | 106% | 62 | 2.4 | 94% | 0 | Nominal |
Swipe the estate table sideways to see every metric
The public tier is free forever, and that is the point.
Anyone can check whether a bench is working without asking us. A supplier who publishes their own uptime has to keep it up.
Public uptime page
Anyone, no login
Free, permanently- ·Per-site uptime for the last 90 days
- ·Whether charging is currently available at that bench
- ·Open incident log with time to restore
Host view
The pub, the park, the campus that hosts the bench
Included with every bench, no subscription- ·kWh harvested and charges delivered, daily and monthly
- ·Battery state of charge and any load shedding overnight
- ·Fault alerts by email, with the repair instructions for that build number
- ·Downloadable social value and carbon report for their own reporting
Operator fleet view
A borough, an estate manager or a hire operator running many benches
18 GBP per bench per year- ·Whole-estate map with per-bench status and last report time
- ·League table of yield against modelled yield, to catch shading and soiling
- ·Spares and service scheduling against the maintenance model
- ·Mesh node health across the EN/ABEL layer
- ·API and CSV export for asset management systems
Nine metrics, each with a unit and a source.
- Unit
- percent of the day the charge service was available
- Interval
- 1 minute heartbeat
- Source
- Controller watchdog
- Unit
- Wh
- Interval
- 5 minutes
- Source
- MPPT input counter
- Unit
- Wh
- Interval
- Per charge session
- Source
- USB-C port metering
- Unit
- count and mean duration
- Interval
- Per session
- Source
- USB-C negotiation log
- Unit
- percent
- Interval
- 5 minutes
- Source
- Battery management system
- Unit
- count, with which load was shed
- Interval
- Per event
- Source
- Priority controller
- Unit
- coded fault with severity
- Interval
- Per event
- Source
- Controller and BMS
- Unit
- neighbours seen, packets relayed
- Interval
- 15 minutes
- Source
- EN/ABEL node
- Unit
- percent of modelled yield
- Interval
- Daily
- Source
- Computed on the yield model
Defined before the hardware, so the hardware has to meet it.
Message shape
A fixed 44-byte binary frame: build number, epoch minute, Wh harvested, Wh delivered, state of charge, flags for shed and fault, and a rolling sequence number. No free text, no personal data, no device identifiers of any kind.
Interval and budget
One frame every five minutes, 288 frames a day, roughly 12.7 kB per bench per day. That fits inside the 1.2 kbps control-plane budget in the mesh link specification with room for relayed traffic.
Offline buffering
The controller holds 30 days of frames in local flash. When a node loses its uplink it keeps recording, and back-fills in sequence-number order when the mesh returns. Gaps are shown as gaps, never interpolated.
Retry and back-off
Three immediate retries, then exponential back-off to a fifteen-minute ceiling. A bench that cannot reach the mesh still charges phones: telemetry loss never degrades the service.
Privacy by construction
The bench cannot identify a user. It counts sessions and watt-hours. There is no MAC capture, no camera, no footfall sensor, and nothing that could later be repurposed into surveillance.
- Priority
- 1
- Shed rule
- Never shed. Reserve held at 20 percent state of charge.
- Priority
- 2
- Shed rule
- Dimmed before it is shed, and only below 14 percent.
- Priority
- 3
- Shed rule
- First to shed, below 22 percent, restored automatically at 30 percent.
Where this sits
Canopei Fleet closes the fleet platform row on the differentiation roadmap, runs over the EN/ABEL mesh, and takes its first measured telemetry from the working scale prototype.