The way most system integrators sell IoT today
Most system integrators deliver IoT the same way they deliver everything else. A client asks for a solution. The SI scopes it, builds it, bills for the hours and the hardware, and moves on to the next client.
That model works. It pays the bills. And it has a ceiling.
A one-off project ends when the invoice is paid. The dashboard you built, the device integration you wrote, the alert logic you tuned, all of it lives inside one client account and does nothing for the next deal. Every new client restarts the same setup cost. New infrastructure to stand up. New support burden to carry. New devices to provision from zero.
But the harder problem is revenue shape. One-off project revenue does not compound. You are only as healthy as your next signed contract. When the pipeline slows, the income stops, because nothing you delivered last year is paying you this year.
White-label IoT changes that shape. It lets an SI put their own brand on a platform that already exists, manage many customers from one place, and turn delivery work into a recurring product line. This post explains what white-label IoT actually means, how TagoRUN provides it, the build versus resell decision, and where it is the wrong choice.
What white-label IoT actually means
White-label is a term borrowed from manufacturing. A company makes a product, removes its own branding, and lets another company sell it under their name. The buyer never sees the original maker.
In IoT, white-label means you run a full application platform under your own identity instead of building one. Concretely, that comes down to a few things.
Your own logo. The platform shows your brand, not the vendor’s. When a client logs in, they see your company.
Your own domain. Clients reach the platform at your URL, something like portal.yourcompany.com, not a generic vendor address.
Multi-tenant customer separation. You run one platform but each customer is isolated. Customer A cannot see Customer B’s devices, dashboards, or data. You, as the operator, see all of them and manage them from one console.
Your pricing on top. You decide what each customer pays. You buy capacity from the platform vendor at one rate and sell access to your clients at your own rate. The margin between those two numbers is your recurring revenue.
That last point is the business change. You stop selling hours and start selling access. A client who pays you monthly for a branded portal that monitors their equipment is a client who keeps paying as long as the equipment runs.
How TagoRUN provides it
TagoRUN is the white-label, multi-tenant product in the TagoIO family. It is built for system integrators and resellers who want to run an IoT platform under their own brand without building the platform itself.
With TagoRUN you create a branded environment. You set the logo, the colors, and the custom domain. Your customers sign up or get provisioned into that environment and only ever see your brand.
Each customer is a separate tenant. Their devices, dashboards, users, and data stay inside their own space. You operate above all of them, with visibility into every tenant and control over what each one can access. You can define the plans your customers buy and what each plan includes.
Underneath, you get the rest of TagoIO. Device connectivity, data storage, dashboards, analysis scripts, alerts, and user management. The same platform TagoIO runs is the platform your customers use, with your name on it.
You can see how the access tiers and limits work on the TagoIO pricing page, and the technical setup for devices, buckets, and dashboards is documented at docs.tago.io. For the multi-tenant and branding mechanics specifically, the TagoRUN sections of the documentation cover how tenants, profiles, and custom domains fit together.
Build versus resell
Every SI who looks at white-label IoT eventually asks the obvious question. Why not just build it ourselves on raw cloud? We know how to write code. We have AWS or Azure accounts. How hard can it be?
It is not hard to start. It is hard to finish, and harder to keep running.
A platform that holds up under real customers needs device ingestion that does not drop messages, storage that scales as data grows, a dashboard layer non-technical clients can actually use, user and permission management, alerting, and the multi-tenant isolation that keeps one client’s data away from another. Each of those is a real engineering effort. Together they are a product, not a feature.
Then there is the part nobody scopes correctly: running it. Uptime. Security patches. Scaling when a client adds ten thousand devices. On-call when something breaks at 2am. Every hour your engineers spend keeping your homegrown platform alive is an hour they are not spending on billable client work. The platform stops being an asset and becomes a second business you did not mean to start.
Reselling a managed platform moves that burden to the vendor. You pay for capacity and get connectivity, storage, uptime, and security as part of the deal. Your team spends its time on the layer that is actually yours: the client relationship, the domain knowledge, the specific solution. You trade some control for a lower operating cost and a faster path to a sellable product.
The honest tradeoff: building gives you total control and a cost structure you own, at the price of time and ongoing operations. Reselling gives you speed and offloaded operations, at the price of working within a vendor’s model and pricing. For most SIs whose core skill is delivering solutions rather than operating cloud infrastructure, reselling wins. But not for everyone.
When TagoRUN is the wrong choice
A house rule at TagoIO is that we name the cases where we are not the right answer. Two come up often.
First, device count economics. TagoRUN, like most of TagoIO, is priced around usage tiers, including how many devices and how much data you run. If your business model depends on deploying very large numbers of devices and you need predictable cost regardless of count, a usage-tier model can get expensive as you scale. Datacake uses a different pricing model that some integrators find fits high-device-count deployments better. If per-device cost is the number that decides your deals, compare it directly before you commit.
Second, full self-hosting and source control. Some integrators have a hard requirement to run everything on their own infrastructure, with access to the source, and no dependency on a vendor’s cloud. That is a legitimate need, especially in regulated or air-gapped environments. TagoRUN is a managed product, so it does not fit that requirement. Self-hosted ThingsBoard is open source, runs on your own servers, and gives you full control of the code. You take on all the operations and engineering yourself, which is the cost of that control, but if source ownership is non-negotiable, it is the honest fit.
If neither of those describes you, the resell path through a managed white-label platform is usually the faster route to recurring revenue.
Practical steps to start
You do not need to convert your whole business at once. A reasonable path looks like this.
Pick one repeatable solution. Look at the projects you have already delivered and find the one you have built more than once. Equipment monitoring, environmental sensing, asset tracking, whatever it is. That repeatable solution is your first product.
Stand up a branded environment. Set up TagoRUN with your logo, colors, and domain. Build the standard dashboards and device integrations for your chosen solution once, well.
Move one existing client onto it. Migrate or onboard a client you already trust into the branded environment as your first tenant. Use the relationship to find the rough edges before you sell it widely.
Set your pricing. Decide what a customer pays you monthly and confirm the margin against what the platform capacity costs you. The pricing page gives you the input side of that calculation.
Sell access, not hours. For the next client who needs that solution, quote a recurring subscription to your branded platform instead of a one-time build. The work you did once now serves every client after.
Each new tenant adds revenue without restarting your infrastructure cost. That is the compounding the one-off model never gave you.
The shift worth making
The one-off project model is not wrong. It is just limited. It ties your income to your next contract and throws away most of what you build.
White-label IoT keeps the work. It turns a solution you built once into a product many clients pay for monthly, under your brand, managed from one place. TagoRUN is built to make that switch without making you build the platform underneath it.
If your business depends on huge device counts at fixed cost, look hard at Datacake first. If you must own the source and self-host, ThingsBoard is the honest answer. For most system integrators who want recurring revenue from solutions they already know how to deliver, the resell path is the one that pays you next year for the work you do this year.
Start with one solution and one client. The model proves itself from there.
