Most building owners never decide to get locked in. They buy a building management system because they need controls that work, they sign whatever the integrator puts in front of them, and the system runs. The lock-in is not a clause anyone reads out loud. It is the slow accumulation of dependencies that, three years later, means one vendor controls what your building can and cannot do.
We call it the hidden tax because it behaves like one. You do not see it as a line item. You feel it in the price of every small change, in the data you own but cannot reach, and in the quotes you cannot benchmark because only one company speaks your building's language. The hardware was the cheap part. The dependency is what you pay for, year after year, for as long as you hold the asset.
Where the tax actually comes from
Lock-in is rarely a single bad decision. It is built from a handful of ordinary ones that each made sense at the time.
- Proprietary protocols. The controllers talk in a closed dialect. The data exists, but reading it requires the vendor's gateway, the vendor's license and the vendor's blessing.
- The integrator monopoly. Only firms certified by the vendor can touch the system. You cannot get a second quote that means anything, because no one else can do the work.
- Undocumented commissioning. The point list, the logic, the wiring map live in one engineer's head. When they leave, your building's manual leaves with them.
- Licensed reporting. Energy and compliance reports come from the vendor's cloud, on the vendor's terms, and stop the day the contract does.
None of these is dramatic on its own. Together they form a wall. By the time an owner notices, the cost of leaving looks higher than the cost of staying, which is exactly the position the wall was built to create.
The hardware was the cheap part. The dependency is what you pay for, year after year, for as long as you hold the asset.
The numbers owners do not see
The sticker price of a BMS is a fraction of what you spend over its life. The expensive years are the quiet ones. A change that should take an afternoon becomes a multi-week change order because only one firm can scope it. A retrofit gets shelved because integrating a new chiller into the closed system costs more than the chiller. Surplus energy goes unsold because the data needed to optimise it sits behind a license you would have to renew to read.
We have seen this first-hand. A hotel in Hammamet generates its own power through a turbine and could sell the surplus back to the grid, but its HVAC, access and energy systems are fragmented and locked to a single vendor. The opportunity is sitting in the building. The lock-in is what stands between the owner and it. That is the tax made visible: not a fee, but a value you are quietly prevented from capturing.
Vendor-neutral is an engineering choice, not a slogan
The opposite of lock-in is not a different vendor. It is an architecture that does not let any single vendor become load-bearing. That is the principle puniq designs around, and it is a deliberate engineering discipline, not a marketing promise.
Through our Data Auditor we go into an existing, fragmented building and unify every system into one readable layer that lives on-premises. We translate the closed dialects into open protocols, so the controllers you already own start speaking a language anyone can read. Where there is no system to start from, the Infrastructure Blueprint builds the open automation layer from scratch, designed from day one to never trap the owner.
The data stays yours. It sits in your building, not in a vendor cloud you rent access to. Any qualified integrator can work on top of an open layer, which means you can finally get a second quote that means something. The building performs without the building being held hostage.
