What vendor-neutral actually means

Every IoT vendor says they are open. Open APIs, open standards, open ecosystem. Then the contract renews, the data lives in a format only their tools can read, and the cost of leaving is a rebuild. Open, it turns out, described the front door, not the exit.

Vendor-neutral is a stronger claim. It means that on the day our engagement ends, you can run the platform without us, move it to a different cloud without a migration project, and read every byte of your own data with tools you already own. If any of those three is false, the system is not neutral. It is a nicer cage.

The test we apply

Before we call an architecture neutral, it has to pass three questions:

• Can you leave the cloud? Infrastructure defined as code, no proprietary managed services on the critical path that a competing provider cannot match. Your platform should redeploy on a different account in an afternoon, not a quarter.
• Can you read the data? Storage in open formats with documented schemas. No blob that requires a license to decode. If a public organisation has to keep paying to read records it is legally obliged to retain, the procurement failed.
• Can you keep building? The codebase is yours, commented, in your repository, with the architecture written down. A new team should be able to ship a feature without calling us.

This is not theoretical. If the platform keeps readings in plain Postgres, auditing a meter is one query any analyst can run, with no licence and nobody to ask:

-- hourly average for one water meter, last 7 days
select
  device_id,
  time_bucket('1 hour', recorded_at) as hour,
  avg(value) as avg_litres
from sensor_readings
where device_id = 'wm-04417'
  and recorded_at >= now() - interval '7 days'
group by device_id, hour
order by hour;

If reading your own records needs a proprietary client and a current licence, you do not own the data. You are renting access to it.

Why the public sector specifically

A municipality runs on a decade horizon, not a funding round. Sensors deployed today should still report in 2036, through three procurement cycles and at least one vendor going out of business. Neutrality is not a preference here. It is risk management. The platform that cannot outlive its supplier is a liability the moment it goes into production.

What handover looks like

We hand back the code, the data, and the architecture. That is the whole product. The repository, the infrastructure definitions, the runbooks, and a diagram that an engineer who has never met us can follow. We are happy to keep operating it for you. We are just not the only people who can.

That is the difference. Open is a marketing word. Neutral is something you can test on the day you decide to walk away.