HOLOIN
Book a demo
Menu

The device tells you first

Every asset, live. Yours.

For teams that run vehicles, fields, buildings, remote sites, solar plants and EV depots: one list of what needs a person. On servers you own.

See it on your kind of asset — 15 min →Get demo access →
Room 002 · Meeting · its twinlive
CO₂ · reported by the room’s sensor
1,620ppm
against the line you set: critical · from 09:28:14
critical

RuleCO₂ high in Room 002 · Meeting — shipped on for every company with a building; the line, the minutes and the actions are yours.

  • 09:28:14Alarm raised, critical · Siravelle Tower › Room 002
  • 09:28:15Work order #24 opened and assigned · urgent, on the technician’s phone
  • 09:28:29Work order closed by the technician
  • 09:28:45Alarm cleared · by the reading, not by a person
What the twin holds: readings · your lines · alarms · jobs · historydemo run · the company’s own time

What you run

One product, whatever you run.

live
Fleet
For the dispatcher who hears about a skipped stop from the customer.
The tracker confirms each arrival; a stop left open is caught as the truck drives off.
live
Agriculture
For the grower whose schedule waters whether it rained or not.
A zone is watered until the soil says enough, and a run is refused when it has rained.
live
Buildings
For the facilities team that learns a room is bad from a complaint.
CO₂ rising becomes a work order on the technician’s phone, and the alarm clears only when the air does.
live
Remote sites
For the operator who learns a site lost power when it goes silent.
When the grid fails, the battery’s time left counts down, and a generator start counts only when its controller reports it running.
live
Energy plants
For the owner who can’t tell a cloudy hour from a broken string.
Production is judged against the plant’s own expected figure, with a passing cloud told apart from a fault.
live
EV charging depots
For the depot manager who finds out at six which van didn’t charge.
Each van shows whether it will be ready by its departure, as an estimate, with every session checked against the charger’s own meter.
live
Smart factory
For the plant manager who reads machine states off a clipboard.
State, stops and OEE read from each machine’s own protocol — nothing is ever written to it.
live
Cold Chain
For the cold-store manager who learns why it got warm at the audit.
Every stretch outside the band is recorded with the door, the defrost and a signed reason; the inspector’s record is one download.
Everything inside, by layer →
The twin, the rules, the commands, the integrations — one page, no form.

How it works, in one demo run

A reading became a job at 09:28:14.

Every asset has a live twin: its readings, judged against lines you set, and a job done only when the device confirms it. Here, Room 002 in the demo run, in the order it happened.

Room 002 · Meeting
CO₂
1,620ppm
above the line
1 · A reading arrives. The sensor in the meeting room reports CO₂ rising to 1,620 ppm.
Rule · CO₂ high in Room 002

When a reading arrives for Room 002 · Meeting, if CO₂ is above the room’s comfort band, then raise a Critical alarm and open a work order titled from the alarm.

2 · Judged against your line. The rule that fired, as the builder shows it. It ships switched on for every company with a building; the line and the actions are yours.
Alarms
criticalRoom 002 · CO₂09:28:14
Siravelle Tower › Room 002 · Meeting
3 · The alarm, with its place. Critical at 09:28:14, and where it is.
Work order #24
Statusassigned
Assigned09:28:15
WhereRoom 002
4 · A job, on a phone. At 09:28:15, the technician had the job on their phone, with the room on the plan.

Times are the demo company’s. The values are the run’s own, from the recorded demo-runs file.

The same twin, for IT and OT

A room went quiet. One alarm says why.

A server room in the demo run: a UPS, a PDU, a switch and three servers, each a device in HOLOIN, with the wiring between them recorded. When the power path breaks, the twin names the cause and holds the alarms beneath it.

Room 003 · Server room · Rack A1
UPS-1 · on batterywarning
powers
PDU-A · outlet 1 offroot cause
outlet 1 → switch
SW-CORE-1 · silentheld
ports 1–3
SRV-APP-01held
SRV-DB-01held
SRV-FILE-01held
Upstream cause: PDU-A. 4 devices silent behind it; their alarms held under this one.
  • 09:48:18UPS-1 reports on battery · the shipped UPS rule raises a critical alarm and opens a work order
  • 09:48:22PDU-A outlet 1 switches off · load shedding; the switch and three servers go silent
  • 09:48:51One alarm, not four · PDU-A named as the cause; 4 alarms held under it
  • 09:49:57Power back; the held alarms never fired
1
alarm a person sees, instead of 5
4
devices in the blast radius, named before anyone goes to the room

The UPS, PDU and switch are read over SNMP, the servers push their own readings, and the wiring between them came from the IT team’s own asset database, confirmed by the switches’ neighbour tables. Nothing in the room was changed to be watched. Values from the Server room demo run; times are the demo company’s.

What’s inside

One platform. This much of it, today.

Everything in the product, by layer. The whole list, and for each item what proved it, is on its own page.

How readings arrive

every protocol lands on one pipeline

  • LoRaWAN live
  • CoAP live
  • HTTP live
  • Monitoring-tool alerts live
  • LwM2M live
  • MQTT live
  • OCPP 1.6 · 2.0.1 live
  • Sparkplug B live
In full →

The twin

each device belongs to one place

  • Vehicles
  • Farms, fields, zones
  • Buildings, floors, rooms, racks
  • Remote sites · plants · depots
  • Dependencies: declared, discovered, learned
In full →

Rules and actions

yours to read, change, switch off

  • Thresholds, schedules, events, time windows
  • Alarms with escalation, quiet hours
  • Work orders, on a phone
  • Commands completed only on evidence
In full →

What it learns

arithmetic you can read, no model

  • Usual for this hour of the week live
  • Trends, and when a line is reached live
  • Dependencies it noticed, for you to confirm live
  • “What if this fails” scenarios live
In full →

Sovereign by construction

Your server. Your database. 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, rule and record in a database you administer. A nightly backup you can restore anywhere, drilled monthly.

Nothing phones home

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

Your rules stay yours

Lines, rules, schedules and what the twin learned are text and arithmetic in your database. They leave with you; nothing learned from you leaves otherwise.

A real exit

Licensed by the year for one installation. Leave with your database, your backups and open formats: glTF, GeoJSON, CSV, the whole API described.

Why it’s different

Five things you can check.

01

One twin for every asset

A truck, a zone, a room and a rack are the same twin with different parts; the next kind of asset comes through the same contract.

02

Everything after the radio, in one install

The tracker server, the LoRaWAN network server and the Field Agent ship inside; a device is registered in HOLOIN, never in their consoles.

03

Commands complete on evidence

A valve is open when it reports open. An arrival is the tracker’s. An alarm clears when the reading does.

04

Verification you can read

Every live integration cites its test run; every sentence is recorded against its source; each release is tested with the network sealed.

05

Installed, not subscribed

Licensed by the year for one installation; PostgreSQL you own, backups you can restore anywhere, a real exit.

How this differs

What it does that they don’t.

Dashboards

A dashboard shows a value. HOLOIN judges it against your line and opens the job.

Tracker portals

A portal shows where the truck is. HOLOIN confirms the stop, and catches the one left open.

Building management systems

A building system runs the plant. HOLOIN turns a bad room into a work order on a phone, and clears it only when the air does.

IT monitoring

A monitor pages you for every server that went quiet. HOLOIN names the PDU that took them down, and holds the rest.

Custom builds

A custom build is one project. HOLOIN is one product for every kind of asset, upgraded in place.

Subscriptions to someone else’s cloud

A subscription keeps your data on their servers. HOLOIN runs on yours: nothing phones home, and the database is one you own.

A scenario

One organisation, four kinds of asset.

A water utility runs pumping stations, a fleet of service vans, its offices and a solar plant. On one installation they share one list of what needs a person, one set of rules and one technician’s phone — each asset with its own twin.

Findings · one list
criticalVarnholt Ridge Tower · grid down, generator not startedRemote sites09:03:25
criticalRoom 002 · CO₂ above the lineBuildings09:28:14
clearedInverter 2 · string 3 backEnergy plants09:36:50

Proof

Checked before it ships, in the open.

70 checks

Installed from scratch on every release with its internet cut: a backup restored, a dropped table recovered, readiness proved. The run →

5,753 checks

End-to-end checks through the web entry. How we verify →

Public, no form

The install guide and the API reference. The install guide →

HOLOIN is in pilot. The first installations’ own measurements will appear here when they exist.

The way in

See it running on yours.

I’m responsible for the assets

Fifteen minutes on your kind of asset — no slides.

See it on your kind of asset — 15 min →Get demo access →

I install systems for clients

One installation per client, each a company of its own.

  • The tracker and LoRaWAN servers inside; a Field Agent for the OT network
  • Pricing per installation, published; partner terms on request
  • The install guide and the API are public — read them before we talk
Start a partner conversation →