When a project manager starts shopping for an IoT platform, the first search is almost always the same. Something like “best IoT platform 2026.” You get a listicle. Ten vendors, a table of green checkmarks, a paragraph each, and a “winner” at the top.
Those lists feel useful, and they tell you which vendors exist and roughly what category they sit in. But they do not answer the question you actually have. Your question is not “which platform is best in general.” Your question is “which platform fits my project, my budget, my timeline, and my team.” Those are different questions, and many of those lists are pay-to-play, so the ranking tells you who paid, not who fits.
So instead of another ranking, here is a framework. These are the questions I would ask any IoT platform vendor, including TagoIO, before signing anything. For each one I will tell you what a good answer sounds like and what should make you walk away.
Question 1: What is the real pricing model, and what is my 3-year total cost?
The sticker price on a pricing page is rarely the number you pay. Ask how pricing scales. Is it per device, per data record, per active user, per dashboard, or some mix? A platform that looks cheap at 50 devices can get expensive at 5,000 if you are billed per data transaction and your devices report every few seconds.
A good answer is a vendor who can model your specific case with you: your device count, your reporting frequency, your user count, over three years. You can see our model on the pricing page.
Red flags: “contact sales for all pricing,” no public numbers anywhere, and any model where a normal increase in data volume causes a non-linear jump in cost you did not see coming.
Question 2: How hard is it to leave, and can I export my data?
This is the lock-in question, and it is the one buyers skip most often. Before you commit, ask how you get out.
Can you export all of your raw data, in a standard format, on demand, without paying a penalty or filing a support ticket that takes two weeks? Can you export your device configurations and your dashboard definitions, or only the raw readings?
A good answer: documented export APIs, standard formats like JSON or CSV, and no contractual clause that holds your data hostage. Look at the TagoIO API docs to judge whether export is a first-class feature or an afterthought.
Red flags: proprietary export formats only, export gated behind a higher tier, or a vague “yes we can help you migrate” with no documented path.
Question 3: Who owns the data, and where does it live?
Ownership and residency are separate questions, and you need both answered in writing.
Ownership: the contract should say the data is yours, not the platform’s. Read the terms, not the marketing.
Residency: ask which region your data is stored in and whether you can choose. If you have European users, GDPR means you need to know where personal data sits and who can access it. Ask whether the vendor is a data processor under your control or a data controller in its own right.
A good answer names specific regions, names its compliance posture, and gives you a data processing agreement without a fight. TagoIO is GDPR-aligned and ISO 27001 certified, and for stricter residency needs there is TagoDeploy for a private cloud deployment in a region you choose.
Red flags: no DPA available, no clear answer on storage region, or terms that claim broad rights over your data.
Question 4: Does it support my connectivity out of the box?
This one is concrete and it kills projects late if you skip it. List your hardware and your network. LoRaWAN? Cellular? Wi-Fi? Modbus or other industrial protocols?
Ask whether the platform has native support or whether you are writing custom parsers and middleware. Ask specifically about your LoRaWAN network server and your cellular provider, by name.
A good answer: a documented integration for your exact stack, plus a parsing layer you can adjust without rebuilding. TagoIO supports LoRaWAN, cellular, and generic HTTP and MQTT ingestion, and for lightweight devices there is TagoTiP.
Red flags: “we can build a connector for that” as a paid professional services line item, or a network server they have never integrated with.
Question 5: How good is the API, really?
For a mid-market project, the API quality decides how much custom work your team does later. A clean, documented, consistent API saves you months. A patchy one costs you a developer for the life of the project.
Read the actual docs before you buy. Are endpoints consistent? Is auth sane? Are there SDKs for your language? Is there a sandbox?
A good answer is docs you can read in an afternoon and understand, like docs.tago.io. Red flag: docs that are out of date, missing examples, or that require a sales call to access.
Question 6: Do I need white-label, and can the platform do it?
If you are reselling the solution to your own customers under your own brand, you need white-label and multi-tenancy. This is not a small feature you bolt on later. It changes the whole architecture.
Ask whether each of your customers can have an isolated environment, their own branding, their own users, and billing separation. TagoRUN is built for this multi-tenant, white-label case.
Red flag: a vendor who says “you can change the logo” and calls that white-label. Real multi-tenancy means data isolation between tenants, not a cosmetic skin.
Question 7: How fast does support actually respond?
Marketing says “24/7 support.” Ask what that means in numbers. What is the response time on the tier you will actually buy, not the enterprise tier you will not?
Ask for the support SLA in writing. Ask whether you get a human or a chatbot. Ask whether there is a community forum and whether the vendor’s own engineers answer in it.
A good answer: a documented SLA tied to your plan, and a public community where you can see real questions getting real answers. Red flag: support quality that drops off a cliff below the top pricing tier.
Question 8: Will it scale to thousands of devices without re-architecting?
Your pilot will have 20 devices. Your rollout might have 5,000. Ask what happens between those numbers.
Does the platform scale by you upgrading a plan, or by you re-architecting? What is the largest documented deployment? What happens to dashboard performance and data query speed at scale?
A good answer points to real deployments at your target scale and explains how scaling works without a rebuild. Red flag: a platform that demos beautifully at 20 devices and has no story for 2,000.
Question 9: Does it meet my compliance requirements?
If you are in healthcare, utilities, or anything regulated, compliance is not optional and it is not something to discover after signing. Name your requirements up front: GDPR, ISO 27001, SOC 2, HIPAA, whatever applies.
Ask for the certifications and the audit reports. A good answer is a vendor who hands you the documentation. TagoIO holds ISO 27001 and aligns with GDPR.
Red flag: “we are working toward that” when you need it in production this year.
Question 10: Can I run a real proof of concept before I commit?
This is the most important question, and it is the cheapest insurance you can buy. Before any multi-year contract, build a small real PoC with your actual hardware, your actual data, and one real use case.
A good answer: a free tier or trial that lets you build the PoC yourself without a sales gate. You can start on TagoIO for free and test with real devices. Red flag: a vendor who will only let you see the product through a guided demo and will not give you hands-on access until you sign.
When TagoIO is the wrong choice
I run content for TagoIO, and I would rather you choose well than choose us and regret it. So here are two cases where TagoIO is not the right answer.
If you need full on-premises control with access to the source code, so your own engineers can modify the platform itself and run it entirely inside your walls with no dependency on a vendor’s cloud, then an open-source platform like ThingsBoard is a better fit. We have TagoCore for edge and on-prem scenarios, and it is open source, but if your core requirement is owning and modifying the entire stack, evaluate ThingsBoard honestly.
If your company is already deeply invested in AWS, you have cloud engineers on staff, and you want everything inside one AWS bill and IAM model, then AWS IoT Core may win. You will build more yourself and you will manage more infrastructure, but if you have the engineering team and the AWS commitment, that control can be worth it. TagoIO trades some of that control for speed to production, and that trade is not right for everyone.
How to use this framework
Take these questions into every vendor conversation, including ours. Score each vendor on the answers, not on where they ranked in a listicle. The platform that fits your project is the one that gives clear, documented, honest answers to the questions that matter for your budget, your timeline, and your risk.
When you are ready to test that on a real build, the cheapest way to learn is a small PoC. Start one, point it at your real hardware, and see how the answers hold up.
