# TagoIO Build | We Deliver the IoT System | TagoIO > TagoIO Build is a service: we take the scope and deliver the IoT system your operation needs at a fixed price. You run the site. TagoIO Build You need a working system, not an IoT development project Building it yourself means staffing an IoT team you don't need. Solving an operational problem shouldn't become an engineering department. ## We deliver the IoT system your operation needs You bring the site problem. We take the scope and deliver the software that reads the sensors, applies your rules, and puts the result where your team needs it. **Fixed price.** Nothing for you to assemble. You keep running the site. ## A written scope. A closed price. The quote names in writing what the system will do. You do not pick modules; we write the scope after we understand the job. A website or app for your users goes in as its own line when you need one. ### Data Every reading arrives, gets stored, and stays queryable: named devices, named variables, and a current value your team can act on. A unit that goes quiet shows up here too. ### Process Your rules run against that data, on a schedule or on every reading: thresholds, calculations, reports, and the checks your operation does by hand today. The job's own logic lives here. ### Action or screen The output your team actually touches, whether that is a dashboard they open, a scheduled export, or a trigger that notifies whoever is on call. One system can carry all three. ### Website for your users (Scoped separately) A site your own customers or crews log into, built from scratch and carrying your name rather than ours. It goes into the quote as its own line. ### Mobile app for your users (Scoped separately) A native app for the people already on site, so a reading or an alert does not wait for someone to get back to a desk. It goes into the quote as its own line. ## TagoIO inside is our call How much TagoIO goes into the system is an engineering decision we make per project, not a menu you configure. Products go in when they make delivery faster and stay out when they do not. The price is fixed either way. Screens / API / Services / Storage ### On the TagoIO platform When the platform already covers the job, we deliver on it. The fastest path, with less custom code to maintain. ### Custom build, TagoIO inside Software built for your operation, with proven TagoIO services doing the heavy work behind an API built for your needs: parsing, analysis, AI, and actions. ### Custom from scratch When the job calls for it, nothing from TagoIO goes in. A new API, new storage, new screens, built only for you. ## It runs on the host you name The finished system can live on TagoDeploy, on your cloud, or on servers you already run. The target is written into the scope. ### TagoDeploy A dedicated TagoIO instance we operate. Single-tenant, in the region you name, no shared infrastructure. ### Your cloud AWS, Azure, Google Cloud, or another provider. We install in the account you name and hand the system over. ### On-premise Your datacenter or plant. We deliver the system on hardware you control. ## The finished system, not a product to learn You are buying years of sensor work, applied to this job. ### TagoIO when it is faster We use TagoIO when it is the faster path. We build custom when it is not. That can mean a system with no TagoIO pieces at all. ### Small jobs count A parser and a rule is enough. A dashboard and analysis is enough. ### Keep what already works If you already have a working TagoIO tenant, we do not rewrite it. The project is the new gap. ## The plant stays yours. The software stays ours. The annual contract covers the software. Everything that happens on site stays with your team. ### Annual support A separate contract, paid in full or monthly. It covers software uptime, bugs, and updates. Automation and alerts may ship inside the system if the spec names them. ### Your team You run alerts, field response, and compliance. Your team knows the plant better than we do, so the calls that need that knowledge stay with the people making them today. What changes is that none of it needs an IoT team behind it. ### Who carries what - Software uptime: Ours - Bugs and fixes: Ours - Updates: Ours - Alert response: Yours - Field work: Yours - Compliance: Yours ## You shouldn't have to build an IoT stack to run your operation A physical problem becomes a software project the moment you assemble the stack on your own payroll. ### That work lands on someone else's calendar. Sensors, networks, dashboards, and the ticket into the tools you already run now sit with whoever drew the short straw. That was never their job. ### A number on a screen is not the system. The map, the rule, and the dispatch your team already uses: that is the product. Homegrown builds stop at the demo. ### Saturday, you are the help desk. When a unit goes quiet, the person who wired it is the only one who knows why. Your operation is still live. A folder of scripts is not a vendor. ### With TagoIO Build ### The work lands on our calendar. Scope, build, and delivery are our job, done by people who do sensor work all day. Your team keeps the jobs they were hired for. ### The product is the working system. The map, the rule, and the dispatch your team uses ship finished. The demo stage is ours to get through, not yours. ### Saturday, you call a vendor. A unit going quiet is a support ticket with a contract behind it, not a hunt for whoever wired it. ## Frequently Asked Questions ### What is TagoIO Build? TagoIO Build is a service, not a platform. You bring the site problem; we take the scope, build the system, and hand it over working. You buy the working system for this job, not a seat to learn. ### What does a fixed-price quote cover? The quote is a closed price against a written scope: the data the system reads, the process it runs, and the action or screen your team uses. A website or mobile app for your users is priced as its own line. ### Do I pick components or assemble anything? No. You describe the job and we deliver the working system. Whether it runs on the TagoIO platform, uses TagoIO parts inside a custom build, or ships fully from scratch is our engineering call. The price is fixed either way. ### What does support cover? A separate annual contract, paid in full or monthly. Software uptime, bugs, and updates. ### I already have a working TagoIO tenant. What then? We do not rewrite it. The project is the new gap. ### Where does the system run? On TagoDeploy, on your cloud (AWS, Azure, Google Cloud, or another provider), or on-premise. The target is part of the written scope. ## Get a fixed-price quote Tell us what is failing on site. We come back with a written scope and a closed price. [llms.txt](https://tago.io/llms.txt)