# IoT Cloud Platform | TagoIO > The full-stack IoT platform to transform sensor data into smart solutions. Connect devices, build dashboards, and deploy at scale. Sensor to Decision. One Platform. Connect any device, store every reading, run your own code on it, and act automatically. Then hand your customer an app with your name on the door. ### Devices arrive decoded A connector reads the payload for you, so a reading lands with its name, its unit and its timestamp already on it. Not a hex string you have to parse. ### Readings are kept Every value stays with the device it came from, queryable for as long as you choose to keep it. No separate database to run beside this one. ### Your code runs on it An Analysis is your own script, running on a schedule or the moment a reading arrives. Nothing of yours has to stay up for it. ### Access is scoped Access Management decides which customer, team or script sees which part of it, before anybody opens anything at all. ## IoT Doesn't Need to be Complicated Follow these three simple steps: Build -> Customize -> Deploy! ### Build with templates Start building your solution using templates, connectors, and code snippets that will save time and inspire you. ### Customize to your liking Design dashboards, set up branding, configure alerts and workflows. Make it yours, no frontend code required. ### Deploy in 1-click Ship to production instantly. Scale from prototype to thousands of devices without re-architecting anything. ## Explore the platform, one part at a time Connect the hardware you already bought, run your own JavaScript or Python against what it sends, decide who sees which part of it, build the screens, and ship in one click. ### Bring the hardware you already bought. 654 connectors across 35 networks decode the payload for you. LoRaWAN, Sigfox, MQTT and plain HTTP all arrive the same way, so adding a sensor is a pick from a list. ### A board somebody will leave open all day. Widgets over your own photograph, glass cards, per-widget opacity and radius, the header off where it gets in the way. All of it is author settings, not a template you fight. ### Your own code, running where the data lands. An Analysis runs in Deno, Node.js or Python, on a schedule or the moment a reading arrives. Console output, environment secrets, the SDK you already read. Nothing to keep alive. ### One account, many customers, nothing leaking. An Access Policy grants or denies per resource, matched on a tag, a path or an id. That is how one deployment serves Northwind and Eastgate without either of them knowing the other exists. ### Shared, single-tenant, or on the box in the plant. Stay on the multi-tenant platform, take a dedicated TagoDeploy in the region your contract names, or run TagoCore at the edge where the link drops. Same platform in all three. - [TagoRUN](https://tago.io/run.md) - [TagoCore](https://tago.io/core.md) - [TagoDeploy](https://tago.io/deploy.md) - [TagoTiP](https://tago.io/tip.md) - [TagoIO Analytics](https://tago.io/analytics.md) - [Backend](https://tago.io/backend.md) - [Visualization](https://tago.io/visualization.md) ## The decoding is already written. Networks, gateways and devices the platform already speaks to, maintained by us. Point the hardware at TagoIO and the readings land named, timed and with their units attached. - [Browse devices](https://tago.io/devices.md) ## What companies build on TagoIO Five of the 18 published case studies: cattle on alpine pasture, a water utility, feed silos, a shopping mall and city waste. Different hardware, different networks, the same platform underneath. - [Read the case studies](https://tago.io/use-cases.md) ## Industries - [Agriculture](https://tago.io/agriculture.md) - [Buildings](https://tago.io/buildings.md) - [Energy](https://tago.io/energy.md) - [Industrial](https://tago.io/industrial.md) - [Logistics](https://tago.io/logistics.md) ## What it costs, and who answers when you ask. Everything above is on the price list, and the account you start on is the account that grows. No quote to sit through first. ### Published, and you can plan against it The price list and the calculator are both on this site. Size the project before you talk to anybody: the plan prices are published, and the calculator gives you an approximate estimate of the usage on top. ### Shared today, single-tenant later Start on a shared account. Move to TagoDeploy when the project earns infrastructure of its own. Same Devices, same Analyses, same dashboards, nothing rebuilt on the way across. ### Open protocols, and your data stays reachable MQTT and HTTP going in, the API coming out. Anything the platform holds, your own code can read, so leaving would be a decision rather than a rescue operation. ### Real people on support, not a bot Every paid plan gets email support from people who work the problem with you instead of handing back a queue position and a link to a help article, plus a 1-to-1 onboarding call. On Scale and TagoDeploy you also get a dedicated Customer Success Manager: a named person who learns the project and stays with it, the same person next quarter, in the same channel, who already knows what you built and why. Architecture reviews and the awkward questions about scale are part of that conversation rather than a ticket. - [See what it costs](https://tago.io/pricing.md) ## Ship the portal under your own name. TagoRUN is what your customers log in to. Your logo, your colours, your domain. The dashboards underneath are the same ones you built. - [Explore TagoRUN](https://tago.io/run.md) ## The same account, out on site. Your projects, your devices and your alerts open on the phone against the data the browser is showing. Nothing to rebuild, nothing to keep in sync. ## Ask the people who already shipped. Integrators, OEMs and hardware makers who put the platform under their own product. Nine of them, in their own words. ## Resources - [Pricing](https://tago.io/pricing.md) - [Blog](https://tago.io/blog.md) - [Integrated Devices](https://tago.io/devices.md) - [Partners](https://tago.io/partners.md) [llms.txt](https://tago.io/llms.txt)