live · Partners · integrators and service providers

For the integrator who runs five clients on five portals.

One installation. Every client a company of its own.

Fleets, farms, buildings, sites, plants and depots on one product your team learns once — with the tracker server, the LoRaWAN network server and the Field Agent inside it. You run nothing else, and each client owns its data.

Start a partner conversation →Get demo access →

Your installation · the clients inside itlive

A logistics client · its own users, roles and dataFleet

A property client · its own users, roles and dataBuildingsEV charging

A telecoms client · its own users, roles and dataRemote sitesEnergy

A farm client · its own users, roles and dataAgriculture

One licence, yoursper installation, per year; verticals licensed one by one; devices counted across it

Their data, theirsa client’s company exports or erases its own records; its name and logo on its screens

Your access, by consentoff until the client’s administrator grants it, for a set time

Every action, loggedagainst both identities — yours and the client’s — in an audit log nobody can edit

Inside the install: tracker server · LoRaWAN network server · OCPP · HTTP · MQTT · the Field Agentthe product as shipped

1The problems

What an integrator actually says.

Four sentences from the people who install and run systems for clients. Each one is answered below, with the screen that answers it.

the service manager, counting logins

“Every vendor portal is another login for my technicians.”

Answered by one wizard for any device ↓

the account manager, in the client’s boardroom

“The client asks who owns the data, and I don’t have a good answer.”

Answered by a company of their own ↓

the owner, pricing a tender

“A building client and a fleet client are two products and two skill sets.”

Answered by one twin on every vertical ↓

the support lead, at the client’s audit

“Supporting a client means I need their admin password.”

Answered by access by consent, logged twice ↓

2How HOLOIN answers each

Four problems, four screens.

Each answer below is a part of the product your team would use on day one, shown on the screen where it lives.

Problem 1 · “Another login for my technicians.”

One wizard registers any device. The servers it needs are inside.

A technician picks the device’s model, types its identifier and places it — a vehicle, a room, a zone, a site. HOLOIN registers a cellular tracker in the bundled tracker server and a LoRaWAN sensor in the bundled network server itself; a controller is read by the Field Agent on the client’s OT network. Nobody opens another system, and the keys stay encrypted on the installation.

Outcome One login, one wizard, one set of steps a technician learns once — whatever the device.

Manage · Add device

1 · PRODUCT

Pick the modelfrom the catalog: trackers, sensors, controllers, chargers; measurements and thresholds preloaded

2 · IDENTITY

Type the identifieran IMEI, a DevEUI with its keys, a controller’s address — HOLOIN registers it in the server inside

3 · HOME

Place ita vehicle, a room on its plan, a zone on the map, a site, a plant, a depot

4 · VERIFY

Watch it arrivethe first reading on screen; packets sent before registration replayed

The same four steps for a cellular tracker, a LoRaWAN probe, a BACnet controller, a Modbus meter, an OPC UA server, an SNMP switch or an OCPP charger.

From the product. The Add Device wizard as a technician sees it: the model, the identifier, the place, the first reading.

Problem 2 · “Who owns the data?”

Each client is a company of its own, inside your installation.

A company has its own users and roles, its own devices and twins, its own rules and work orders, its own name and logo on every screen. Its administrator can export a driver’s record or erase it; the database is PostgreSQL and the backup restores anywhere. When a client leaves, you hand them their data — and you can write that into your contract before they ask.

Outcome “Who owns the data?” has an answer you pass through: they do, and here is how they take it.

Installation · companies

companyA logistics clientits own admins, dispatchers, drivers · Fleetapart

companyA property clientits own facilities team and technicians · Buildings, EV chargingapart

companyA farm clientits own growers · Agricultureapart

theirsDisplay name and logo on their screens · export and erase on request · PostgreSQL you administer, a backup they can takeby design

From the product. One installation, one licence; every client company with its own users, data and branding; nothing shared between them.

Problem 3 · “Two products, two skill sets.”

The same twin, rules and work orders on every kind of asset.

A vehicle, a room, a field zone, a site, a plant and a depot are the same kind of thing to HOLOIN: a place with devices, readings judged against lines, alarms, work orders and history. The rule builder, the alarm list, the technician’s phone and the reports are one product. A technician who set up a building client can set up a fleet client the next week.

Outcome One team, one training, every tender you can see from your office.

Twins · the same panel

vehiclePosition · driver · stops · proofsreadings · lines · alarms · work orders · historyFleet

roomComfort band · occupancy · doors · setpointsreadings · lines · alarms · work orders · historyBuildings

zoneMoisture by depth · valve · flow · runsreadings · lines · alarms · work orders · historyAgriculture

siteGrid · generator · fuel · doorreadings · lines · alarms · work orders · historyRemote sites

From the product. Every home kind carries the same five things; the module adds what its asset needs and nothing else changes.

Problem 4 · “I need their admin password.”

Access by consent, for a set time, logged against both identities.

Your support engineer never signs in as the client. They request a support session with a written reason and a duration; the client’s administrator approves it — or has given a standing consent in advance — and the session opens at the level granted, read-only or full. Every request in it is written to the audit log with both names. The client can end it at any moment; it ends itself when the time is up.

Outcome The client’s auditor reads your support history in their own log, and finds nothing to ask.

Support access · a session

requestedYour engineer, with a written reasona duration and a level: read-only or fullpending

approvedBy the client’s administratoror by a standing consent they set, with its own expiryopens

every requestLogged against both identitiesin the client’s audit log and in yours · users, roles, keys and privacy pages never reachableappend-only

endsWhen the time is up, or when either side ends itthe client is told; the notice itself is loggedat once

From the product. A support session’s life: requested with a reason, approved by the client, logged twice, ended by the clock or by either side.

And the rest of a partner’s week

Roles your wayA role is a named set of permissions; make a “Site technician” or a “Client viewer” once and give it to every client.

Single sign-onA client’s identity provider signs its people in; groups map to roles; no accounts for you to manage.

The technician’s phoneWork orders, parts, photos and notes, offline-safe — the same app for every client.

Reports and eventsCSV reports per module; signed events to the client’s own systems; an API with keys scoped as you choose.

Device limits, softUp to 110 % of the limit, a new device is allowed and recorded as overage; past that, new placements are refused. Devices already placed, and their readings, never stop.

Custom hardwareYour own device definitions, company-owned, exportable as a file the catalog tool accepts.

One upgrade pathUpgrade in place, same volumes; registrations and readings intact, proven on every release.

A support bundleOne archive with no personal data or secrets, which the client’s IT can read before it goes to you — or to us.

3The partner model

You licence the installation. Your clients own their companies.

Two shapes, both true: one installation per client on their own server, or one installation of yours with every client a company inside it. Either way the licence is annual, per installation, by the verticals used and a device tier; devices are counted across the installation, people never are.

You buy at a partner discount and the client is yours: your contract, your invoice, your support. Partner terms — the discount, minimums, support tiers — are stated on request, not on this page.

Yours

The installation and its licence

The server, the bundle, the upgrades, the licence file; the verticals you switch on.

Theirs

The company and its data

Users, roles, devices, twins, rules, work orders, history; their name and logo on it.

Theirs

The way out

Export, erase, a PostgreSQL backup that restores anywhere — on the day they leave, by their administrator.

Yours

Support, by consent

A session they approve, for a set time, logged against both identities; standing consent if they choose.

Ours

The product and the vendor

Releases proven on every tag, the install guide and API reference public, a technical pack on request.

Ours

Access to you — never to your clients

On an installation you run, we have no access at all: you or your client send us a support bundle.

4What it changes in your business

Fewer portals. Fewer awkward questions.

Stated as changes, not as numbers: your margins are yours to work out, and Why it pays gives your clients the arithmetic.

Before

Five vendor portals; a login per technician per portal.
“Who owns the data?” answered with a shrug or a vendor’s terms.
A building client and a fleet client need two products and two trainings.
Supporting a client means holding their admin password.
A new vertical means a new vendor evaluation.
The client’s data lives on a vendor’s cloud, priced per device per month.

With one installation

One login; the servers a device needs are inside.
“They do — here is how they take it”: export, erase, a backup that restores anywhere.
One product; the next client is a company, not a project.
A consented session, for a set time, logged against both names.
A new vertical is a line on the licence; the team already knows the product.
The data lives on the server you or the client run, under one annual licence counted in devices.

5OT and IT, for your engineers

What an engineer learns once.

The install is one Linux server with Docker; the Field Agent is one small program on the client’s OT network, outbound only. Everything an engineer needs to know is in the install guide, and it is public.

On the client’s OT network

The Field Agent, outbound only.

Reads BACnet, Modbus and OPC UA; KNX in beta
Writes only the points the site’s own configuration allows, and only on evidence
Binds nothing but what its drivers declare; the client’s firewall stays “deny incoming”
Discovers what you point it at — never a sweep

On the server

One bundle, one compose file.

The tracker and LoRaWAN servers as install options; OCPP, HTTP and MQTT in the app
TLS at the web entry with the client’s certificate, or a self-signed one for a pilot
Backups nightly, a restore drill monthly, both alarms in the product if they fail
Upgrade in place from a new directory; the old one stays until you remove it

Protocol statuses come from the product’s own facts file; a protocol is named here only once its acceptance run passed, beta where it says beta.

Install guide · what IT opens

in443 to the web entrythe apps, the API, the chargers’ and devices’ pushTLS

inThe tracker protocols’ portsone per protocol, opened only where a client has trackerslisted

in1700 UDP from the client’s LoRaWAN gatewaysto the network server insidelisted

outNothingno telemetry from any container; proved with the network sealed on every releasenone

From the install guide. Every port the guide lists, and the one line about what leaves: nothing.

6How it’s deployed

Buy the devices. Everything else comes inside.

One install bundle carries every server a client’s devices need. Your engineer runs one script; your technician registers the devices; the client’s company appears.

You supply

One Linux server with Dockeryours per client, one of yours for many, or one we run for you in the country you choose
The devicesany model listed, or your own with a published map
A small box for the Field Agenton the client’s OT network, where there are controllers to read
The ports IT opensthe install guide lists them

Inside the install

The tracker serveran install option; trackers registered once by IMEI, never opened by hand
The LoRaWAN network serveran install option; sensors registered once by DevEUI, through the client’s gateway
The Field Agentits image and a standalone package, in the bundle
The web app, the phone app, the database, the backupsone 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 a client’s devices use, each shown only when its acceptance run passed; statuses from the facts file.

7Without HOLOIN

Five vendors to resell, or one product to run.

The same client base, served the usual way. No names: the categories are what matters.

Resold separately

A tracker platform — per device per month, on the vendor’s cloud, the client’s positions in it.
A BMS front-end — the controller maker’s, with its own integrator certification.
A farm or site monitoring portal — per vendor of probe or controller.
A ticket tool — with an account per client and a bridge nobody maintains.
A support arrangement per vendor — each with its own access to the client’s data.

Five contracts, five margins, five trainings; the client’s data in five places, none of them theirs.

In HOLOIN

The tracker and radio servers inside — positions on the installation you run.
The building’s controllers read by the Field Agent — the BMS stays; its points are in the twin.
Farms, sites, plants and depots on the same product — one twin, one rule builder, one phone app.
Work orders in the product — from the alarm, on the technician’s phone, offline-safe.
Support by consent — one mechanism, logged against both identities, for you and for us.

One installation per client or one of yours with companies inside, one database the client owns, one price counted in devices.

8How partners buy

Per installation, per vertical, per device tier, per year.

The grid your clients see is published: the platform plus one vertical from US$4,000 a year for up to 100 devices, each further vertical by its pack, larger installations by tier. A device is a tracker, a sensor, a controller, a charger; a login or a technician’s phone is not.

Partners buy at a discount and own the client. The discount, minimums and support tiers: on request. Up to 110 % of the limit, a new device is allowed and recorded as overage; past that, new placements are refused. Devices already placed, and their readings, never stop.

US$7,000a year, list

A client with a fleet of 70 vehicles, one tracker each — the 100-device tier, from the published grid. Your price: less the partner discount, on request.

The platformUS$2,500
The Fleet packUS$4,500
Dispatchers, drivers, techniciansincluded
The tracker server, the radio server, the phone appincluded
Partner discounton request

9Secure, and kept running

Your installation. Their data. Nothing phones home.

Not a policy page: each of these is a property of the software your client’s IT can check on the server.

One installation, yours

Installed from a bundle that carries everything it needs. Never a shared cloud: one installation per client, or one of yours with each client a company of its own.

PostgreSQL the client can take

Every reading, alarm and record in a database you administer and they can export. A nightly backup that restores anywhere, drilled monthly.

Commands only on evidence

Read-only by default; a command goes out only where a person switched writes on, and completes only when the device reports it. Every outcome logged.

Nothing phones home

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

Your access, by consent

Yours to a client’s company is off until its administrator grants it — for a set time, logged against both identities.

An audit log that can’t be edited

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

10A partner’s four questions

What you actually want to know.

How do I evaluate it without a call?

The install guide and the API reference are public. Ask for the technical pack — the OpenAPI document, the software bill of materials, the read-only statement, a sample webhook receiver — and for demo access to a live installation, read-only, for seven days.

What does my team have to learn?

One product: the Add Device wizard, the twin, the rule builder, work orders and the phone app are the same on every vertical. An engineer learns the install and the Field Agent once; a technician learns the wizard once.

How do I bill my clients?

Your contract, your invoice. The licence is yours per installation, counted in devices at renewal from a usage report you can read; what you charge a client for an installation, a company or a device is your business.

Who supports whom?

You support your clients; we support you. Hours, channel and response time: on request. Every installation can produce a support bundle with no personal data or secrets, which the client’s IT reads before it leaves.

What we don’t do, said plainly: no dashcams, no ELD, no route optimisation, no AI scoring. HOLOIN wins the client who wants ownership, breadth across asset types and honesty — and we’d rather you knew that before the first call.