New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

How to choose an IoT platform

A 13-point checklist: the questions to ask any IoT platform before you commit, why each matters, and where Hermetry stands.

Choosing an IoT platform is a decision you will live with for years. This checklist gives you the questions to ask any platform before you commit, why each one matters, and where Hermetry stands, so you can compare like with like.

The checklist at a glance

  1. Can it connect the devices you already have?
  2. Does it work at sites with poor or no internet?
  3. How does each device prove who it is?
  4. Is it one platform, or several tools glued together?
  5. Can your own team build the screens?
  6. Will the right person hear about an alarm?
  7. Can you update firmware safely?
  8. Can you keep plants, departments or clients apart?
  9. Can you see who did what?
  10. Where will your data live?
  11. Can you leave with your data?
  12. Will it carry your growth?
  13. Can your other systems talk to it?

1. Can it connect the devices you already have?

Replacing working sensors and meters to fit a platform is the most expensive way to start. List the protocols your devices speak today, including equipment that cannot send anything by itself and has to be asked.

Ask:

  • Which protocols are supported out of the box, and which need custom work?
  • Can it reach equipment that cannot send by itself, such as SNMP devices and cameras?
  • Does it run its own LoRaWAN network server, or do you need a separate one?

Hermetry: Devices send over MQTT or HTTPS, LoRaWAN sensors join through Hermetry’s own network server with a library of 344 codecs, field devices report through a gateway, and SNMP equipment is polled by the platform. Devices and connectivity

2. Does it work at sites with poor or no internet?

Plants, pump stations and remote sites rarely have a fixed IP address or an open port, and often lose their connection. A platform that needs inbound access to every site will cost you a VPN project.

Ask:

  • Do devices connect outbound only, or does the site need open ports?
  • What happens to readings while the connection is down?
  • Can field equipment without a public address still be reached?

Hermetry: Devices and gateways connect outbound, so sites need no VPN or fixed IP. With Hermetry Edge on the site network, the platform reaches local equipment over Edge’s encrypted connection. Hermetry Edge

3. How does each device prove who it is?

A shared password across a fleet means one leaked device exposes all of them. Each device should have its own credential that you can rotate or revoke on its own.

Ask:

  • Does every device get its own credential?
  • Are certificates supported, and who issues them?
  • Can you limit a device type to known networks and message rates?

Hermetry: Each device has its own access token, MQTT password or X.509 certificate from the platform’s own authority. Secrets are shown once and stored only as hashes, and a profile can limit devices to up to 64 networks. Device security

4. Is it one platform, or several tools glued together?

When dashboards, SCADA screens, rules and alarms each keep their own copy of the data, the numbers drift apart and every change has to be made several times.

Ask:

  • Does a value from a sensor appear the same everywhere: dashboard, screen, rule?
  • Is there one sign-in and one permission model across all parts?

Hermetry: Connectivity, dashboards, SCADA, rules, alarms and firmware updates share one data model and one sign-in. Why Hermetry

5. Can your own team build the screens?

If every new dashboard or process screen needs the vendor, your operators will wait weeks for small changes.

Ask:

  • Can engineers build dashboards and process screens without code?
  • Is there a library of industrial symbols, and do they show live states?

Hermetry: Dashboards and SCADA screens are built in the browser, with a symbol library in 13 industry packs, every symbol in 2D and 3D. SCADA library

6. Will the right person hear about an alarm?

An alarm nobody acknowledges is just a log entry. Check how alarms escalate, and through which channels people are reached.

Ask:

  • How many severities are there, and can alarms be acknowledged and resolved?
  • Does it keep reminding until someone acknowledges?
  • Which channels reach people: app, e-mail, SMS, chat?

Hermetry: Alarms have five severities, are acknowledged and resolved, and remind until someone acknowledges, in the app, by browser push, in chat, by e-mail or by SMS. Alarms and alerts

7. Can you update firmware safely?

A bad firmware image sent to the whole fleet at once can take every device offline. Updates should be signed and rolled out in stages.

Ask:

  • Is firmware signed, and who holds the signing key?
  • Can a rollout go out in waves and stop by itself if too many devices fail?

Hermetry: Firmware is signed in your own release pipeline; Hermetry keeps only the public keys. Rollouts go out in waves, and a wave that fails its gate pauses the rollout. Firmware updates

8. Can you keep plants, departments or clients apart?

If you run several sites or serve your own customers, each one needs its own users, devices and branding, without seeing the others.

Ask:

  • Is separation enforced in the database, or only in the application?
  • Can each organisation have its own roles, sign-in rules and branding?

Hermetry: Every organisation is kept apart by row-level security in the database, with its own members, roles, sign-in rules and branding. Organisations and white label

9. Can you see who did what?

Auditors, insurers and your own security team will ask who changed a setpoint, a rule or a permission, and when.

Ask:

  • Are sensitive actions written to an audit log that cannot be edited?
  • Does it support two-factor sign-in, passkeys and single sign-on with your identity provider?

Hermetry: Sensitive actions go to an append-only audit log per organisation, including support access. Sign-in supports two factors, passkeys, and SAML 2.0 or OpenID Connect. Security

10. Where will your data live?

Many contracts and laws say where data may be stored. Ask where the servers are, what leaves that region, and whether you can run it on your own servers.

Ask:

  • In which regions can you host, and can you check it yourself?
  • What is processed outside your region, and why?
  • Is there an on-premises option for sites that cannot use a cloud?

Hermetry: Hermetry runs in separate regions, with a residency page that shows your region’s facts, and can run on your own servers on the Enterprise plan. Data residency

11. Can you leave with your data?

The day you sign is the day to ask how you leave. Check what you can export, in which format, and for how long after the contract ends.

Ask:

  • Can you export your data in machine-readable formats at any time?
  • How long is data kept after the contract ends, and is deletion confirmed?

Hermetry: You can export through the app and the API during your subscription, and for 30 days after the agreement ends. Deletion is confirmed in writing on request. Export and leave

12. Will it carry your growth?

A platform that works with 50 devices may not work with 50,000. Ask for load test results with real numbers, not just a claim.

Ask:

  • Are load test results published, with server sizes and message rates?
  • Are limits and quotas documented before you buy?

Hermetry: Load tests run by an independent party are published: up to 500,000 devices, and up to 11,111 messages a second, on one 16-core server. Limits and quotas are in the docs. Performance

13. Can your other systems talk to it?

Your ERP, MES, ticket system or data team will want the data. Without an open API, every integration becomes a project.

Ask:

  • Is there a documented REST API with keys limited to chosen permissions?
  • Can it call your systems when something happens, with signed webhooks?

Hermetry: The REST API uses keys that hold only the permissions you choose, signed webhooks call your systems on events, and MCP servers let AI assistants read your data. Developers

Then test it with your own devices

Answers on paper only go so far. Before you decide, run a short trial:

  1. Connect two or three of your real devices, including the hardest one.
  2. Build one dashboard and one alarm your operators would actually use.
  3. Trigger the alarm and check that the right person is reached.
  4. Export the data and check that you can read it.
  5. Ask your security team to review the answers above.

Questions about choosing an IoT platform

What matters most when choosing an IoT platform?

Start with what you cannot change easily: whether it connects your existing devices, where your data lives, and whether you can leave with your data. Dashboards and features are easier to judge in a trial.

Should we build our own IoT platform or buy one?

Building means you also own device security, firmware updates, multi-site separation, audit and scaling for as long as you run it. Use this checklist to see how much of it a platform already covers before you decide.

How long should a platform trial take?

Long enough to connect your real devices, build one dashboard and one alarm, and export the data. If those steps take weeks, that tells you something too.

Do we need on-premises hosting?

Only if a site cannot send data to a cloud, or a contract requires it. Otherwise a hosted region in your legal area is usually simpler. Hermetry offers both, and they can be combined.

Try Hermetry against this list

Start a free trial in your region, or let us walk you through each point with your own devices in mind. Words you are unsure of? See the IoT glossary.