TRUST
What we claim, and how to check it.
The evidence behind every status on this site, the guide your IT team would follow, and how you leave with everything.
How we verifyThe CI runs behind the statuses on this site: the install tested with the network sealed, the check counts, the run numbers.Install guideThe guide your IT team would follow to install and run HOLOIN on its own servers: sizing, network, installing, backups, upgrades.Technical packThe OpenAPI document, the software bill of materials, the read-only statement, a sample webhook receiver and the install guide, by email.
Installed, not subscribed. If a licence lapses: Updates and support stop. After 14 days’ grace the installation turns read-only: monitoring, alarms and ingestion keep running on your server; changes — new vehicles, rules, users — wait for a valid licence.
NO LOCK-IN
Leave with everything, in formats you already use.
- A PostgreSQL database you own. It runs in your installation, on your disk; your team can open it with
psqlat any time. - Backups are standard PostgreSQL dumps. The nightly backup is a dump of the whole database, plus your uploaded files as a plain archive — restorable with PostgreSQL's own tools, without HOLOIN.
- Open formats in and out: 3D building models are the glTF files you upload; field and zone outlines are GeoJSON; jobs and buildings import from CSV and every report exports to CSV; the whole API is described in OpenAPI.