HOLOIN
Book a demo
Menu

live · EV charging depots

For the depot manager who finds out at six which van didn’t charge.

Ready by six. Under the limit.

Every charger, every session, every vehicle that needs to leave at six — in one twin, on your own server, with no fee per port.

See it on a depot like yours — 15 min →What you need
Marlowen Depot · 14 chargers · its twinlive
Load now
72.0kW · of 200
Sessions
12charging · energy from each charger’s register
Ready by departure
12of 14 · Van 12 22.7 kWh short, est.

RuleEvery session’s energy from the charger’s own register; readiness by the van’s departure as an estimate; a power limit completed only on the charger’s own reading.

  • Bay 7GroundFailure · the charger’s own error · work order #26
  • 01:39Board B lost power · 6 chargers silent behind its meter, held under one alarm
What the twin holds: load · supply tree · sessions · readiness · chargers · historydemo run
1The problems

What a depot manager actually hears.

Four sentences from the people who run depots. Each one is answered below, with the screen that answers it.

the depot manager, at six
“A van didn’t charge and we found out when the driver did.”
Answered by readiness by departure ↓
the site engineer, at the meter
“Plug everything in and we trip the supply.”
Answered by the limit as a rule ↓
the technician, at a dead bay
“The charger shows a code and nobody knows what it means.”
Answered by the fault in the standard’s own words ↓
the operations lead, after a trip
“One board trips and every charger behind it alarms.”
Answered by one alarm on the board’s meter ↓
2How HOLOIN answers each

Four problems, four screens.

Each answer below is something the product did in the demo run, shown on the screen where it did it.

Problem 1 · “A van didn’t charge.”

Every van, ready by its departure or not, as an estimate.

For each one with a departure time: energy so far, what it needs, the rate now — ready by its departure, or not ready, with the shortfall in kWh. Every projection says “est.” Vehicles without a departure time say so; the twin doesn’t guess.

Outcome The van that won’t make it is named before the shift, not after.
Depot · readiness
ready12 of 14 vansprojected ready by their departure, est.est.
shortVan 1222.7 kWh short at this rate, est.est.

From the demo run. 12 of 14 vans projected ready by their departure; Van 12 22.7 kWh short at this rate (est.).

Problem 2 · “We trip the supply.”

The limit is a rule, not a hope.

A rule the depot writes — load over its limit → share 90 % of it equally across the chargers charging now — sends each charger a charging profile. Each command completes only when that charger’s own reading shows it at or under its share while it draws. A charger that answers “accepted” and keeps drawing is a failed command, shown as one.

Outcome The limit is kept by a rule you write and can read.
Depot · load
load72.0 kWthe site meter’s import, of 200 kWnow

From the demo run. Marlowen Depot drawing 72.0 kW against its 200 kW limit. The demo writes no limit rule, so the frame shows the load and the limit only.

Problem 3 · “A code nobody understands.”

The fault in the standard’s own words, and a work order from your rule.

Faults by the names the protocol gives them — GroundFailure (a ground fault) — into a work order by a rule you write; a charger whose sessions fail at more than twice its siblings’ rate, before anyone complains.

Outcome The technician reads the fault, not a code.
Depot · chargers
faultBay 7 · GroundFailurethe charger’s own errorerror
work order#26opened by the depot’s ruleopened

From the demo run. Bay 7 reported GroundFailure: work order #26.

Problem 4 · “Every charger alarms.”

One alarm on the board’s meter.

A switchboard trip as one alarm naming the meter on that switchboard, not each charger offline — once the depot’s supply tree is set up.

Outcome One alarm names the board; the chargers behind it are listed under it.
Depot · supply tree
root causeBoard B · meter6 chargers silent behind it, held01:39

From the demo run. “6 devices silent — all behind Board B meter, down since 01:39”

And the rest of the day’s work

Tonight’s planA power limit per charger for the night, within 90 % of the depot’s limit, earliest departure first — a recommendation with its evidence. Confirming it sends the limits once, audited, each judged on the charger’s own reading.
The peak, with its timeThe month’s peak so far and when it happened; your demand charge per kW, if you enter it, turns it into a figure that says “est.”
AvailabilityTo the minute: the minutes each connector could charge, out of the minutes judged.
SessionsEvery session’s energy from the charger’s own register, start to stop — never added-up power.
A silent chargerJudged against its own rhythm.
Registered firstA charger is registered before it connects, with a key shown once.
Unknown chargersUnknown chargers knock and are refused; a person registers or accepts them; nothing is created on its own.
The depot’s daily figuresOn its page, day by day.
3The twin of a depot

The depot is the record. Everything attaches to it.

A depot is its supply limit, its chargers and their connectors, the site meter, the switchboards between them, and the vans that need to leave.

Load
Against the limit

The site meter’s import, against the depot’s supply limit.

Sessions
Each from the charger’s register

Energy from start to stop, never added-up power.

Readiness
Each van by its departure

Ready or short, every projection “est.”

Chargers
In OCPP’s words

Connectors, status and errors as the charger sends them.

Supply tree
Boards and their meters

Boards, their limits, and their meters where fitted.

Then
History

Every reading, session and work order against the depot.

4What the twin changes in the day’s work

No surprise at six. No trip at the meter.

Stated as changes, not as numbers: your numbers are yours to measure, and Why it pays gives you the arithmetic.

Before
  • A van that didn’t charge is found at six.
  • The supply limit is a hope.
  • A charger shows a code.
  • A board trip floods the alarm list.
  • The utility’s peak arrives with the bill.
With the twin
  • Each van ready by its departure, or named short, as an estimate.
  • The limit is a rule; each command completes on the charger’s own reading.
  • The fault in the standard’s words, as a work order.
  • One alarm on the board’s meter.
  • The month’s peak so far, with its time.
5OT and IT

OT and IT, in one twin.

Marlowen Depot · supply tree · Board B
Site meter · 200 kW limitok
feeds
Board B · meter · down since 01:39root cause
6 chargers behind it
Charger · silentheld
Charger · silentheld
Charger · silentheld
… and 3 more, held
6 devices silent — all behind Board B’s meter. One alarm, with the chargers it holds back. The supply tree you drew is mirrored into the twin’s wiring, so the switchboard is a device with dependants.

OT and IT, in one twin. Chargers over OCPP and the site meter are the OT; the switchboards and their meters, and the roof’s inverter found by a Field Agent, are the electrical IT between them. The depot’s supply tree is wiring the twin reasons over: a board down is one alarm, not one per charger.

OT · what is measured

Each charger’s connectors, status words and errors as OCPP gives them; every session’s energy from the charger’s own register; the site meter’s import; the roof’s inverter over SunSpec.

IT · what keeps it reporting

HOLOIN is the OCPP server, on your installation: a charger is registered before it connects, with a key shown once; the supply tree, with each board’s meter, mirrored into the twin’s connections.

6How it’s deployed

Buy the chargers. Everything else comes inside.

One install bundle carries what a depot needs. Your chargers connect out to your installation over TLS; the depot appears.

You supply
  • One Linux server with Dockeryours, or one we run for you in the country you choose
  • The chargersany that speaks OCPP 1.6J or 2.0.1
  • The ports your IT opensthe install guide lists them
Inside the install
  • The OCPP server, built inyour chargers connect to your installation, OCPP 1.6J and 2.0.1
  • The database, the backups, the web entryone compose file, one address
Kept running by the install itself
  • One scriptready in 2 min 42 s on the acceptance box (run 39194860273)
  • Nightly backup, monthly restore drilla failed one is an alarm in the product
  • Upgrade in placesame volumes, registrations and readings intact, proven on every release
  • No telemetrythe bundled servers’ phone-home is off; CI fails if any container reaches out

The servers this kind of asset uses, each shown only when its acceptance run passed; statuses from the facts file.

7Without HOLOIN

Five systems, or one.

The same depots, run the usual way. No names: the categories are what matters.

Bought separately
  • A charge-point operator’s cloud — a fee per port, your data on their servers.
  • A load-management box — its own rules, out of sight.
  • A fleet spreadsheet — which van leaves when.
  • An energy portal — the peak after the fact.
  • A ticket tool — faults retyped.
Five contracts, five logins, no path from one to the other. When a van isn’t ready at six, nobody can say why.
In HOLOIN
  • The OCPP server inside your install — your chargers, your server.
  • The limit as a rule you read — each command completed on the charger’s own reading.
  • Readiness by departure — per van, as an estimate.
  • The month’s peak so far — with its time.
  • Faults become work orders — in the standard’s words.
One installation, one database you own, one price counted in devices.
8What it costs

Counted in devices. Never in people.

One licence per installation, per year, by device tier. A charger is one device, whatever its connectors; a meter is a device; an operator’s login and a technician’s phone are not. Add operators and technicians without a change to the bill.

The whole grid, every tier and every pack, is on Pricing — published, with what counts as a device and what is included.

US$7,000a year
A depot like the demo’s: 14 chargers, the site meter and Board B’s meter — the 100-device tier, from the published grid.
  • The platformUS$2,500
  • The Fleet or Charging packUS$4,500
  • Operators and techniciansincluded
  • The OCPP server, the phone appincluded
9Secure, and kept running

Your server. Your depot’s data. Nothing phones home.

Not a policy page: each of these is a property of the software you can check on your own server.

One installation, yours

Installed from a bundle that carries everything it needs. Never a shared cloud: one installation per customer, or one your integrator runs for you, each client a company of its own.

PostgreSQL you own

Every reading, session and record in a database you administer. A nightly backup you can restore anywhere, drilled monthly.

Commands only from what you allow

HOLOIN never adds a charger on its own. It sends a charger only commands from a rule a person wrote, from a person or an API key allowed to send them, or from a plan someone confirmed. Every command is logged, and completes only on the charger’s own message — never on its “accepted”.

Nothing phones home

No telemetry in the product, none in the bundled servers. Proved with the network sealed on every release.

Your rules stay yours

Lines, rules and what the twin learned are text and arithmetic in your database; they leave with you.

An audit log that can’t be edited

Every change, by whom, from where — append-only in the database itself, for seven years, even for the database’s own administrator.

10The four questions

What you actually want to know.

Do I have to install anything?

No. We run HOLOIN for you on a dedicated server in the country you choose, never shared with another company, and you can take it with you. If you have your own servers, install it there instead; same product.

What do I need?

Chargers that speak OCPP 1.6J or 2.0.1, connecting out to your installation over TLS. The install guide lists the ports.

What does it cost?

Per installation, per year, by device tier: from US$7,000 a year for the platform and EV charging, up to 100 devices. The whole grid is on Pricing. No per-seat fees; every operator and technician is included.

Who do I call?

Hours, channel and response time: on request. Every installation can produce a support bundle on demand, a readable archive with no personal data or secrets, which your IT team can check before it goes to us.

11The way in

See it running on yours.

I’m responsible for the depots

Fifteen minutes on a depot like yours — no slides.

See it on a depot like yours — 15 min →Get demo access →

I install systems for clients

One installation per client, each a company of its own. The chargers connect to the installation; the ports in the install guide.

Start a partner conversation →