# TagoDeploy | Dedicated IoT Platform Instances | TagoIO

> Deploy dedicated TagoIO instances in 12+ AWS regions worldwide. Full control, custom domains, enterprise-grade isolation.

TagoDeploy

Deploy Your IoT Platform Globally. Your own Enterprise Version.

TagoDeploy gives you a dedicated, single-tenant instance of TagoIO in any of 12+ AWS regions worldwide, with full control over your resources and no shared infrastructure.

## One project, many services

A project starts by installing the TagoIO Platform app. Everything after it is another app from the same catalog, installed into the instance you own.

- **TagoIO Platform**: the app that creates the project, on infrastructure dedicated to you
- **Network middleware**: AWS IoT, Chirpstack, Everynet, Generic HTTPS, Loriot, MachineQ, Myriota, Senet, Sigfox, Tektelic, TTN
- **MQTT Broker**: managed, inside your instance
- **Monitoring**: alerts over email, SMS or webhook
- **Custom Docker**: your own container image, on its own subdomain

[Read the services docs](https://docs.tago.io/docs/tagodeploy/services/overview)

## Nothing ships until you review it

Changes collect in the project until you review and deploy them.

- **Review and Deploy**: every pending change listed by service before it runs
- **Previous version stays live**: until the new deployment finishes
- **History**: each deployment marked Success, In Progress or Error, with its logs
- **Versions**: move only on a manual Update or Rollback
- **Live settings**: MQTT clients, groups, rules, pipelines and collaborators apply without a deployment

[Read the deployments docs](https://docs.tago.io/docs/tagodeploy/project/deployments/history)

## Size every service yourself

Every service runs on settings you choose and change through a deployment.

- **Machine size**: vCPU and memory for the API, databases, MQTT and middlewares
- **Autoscaling**: minimum and maximum instances, a CPU threshold and cooldowns up and down
- **Replicas**: read replicas on the main and in-memory databases
- **Limits**: higher limits can need more capacity, so you adjust the API's scaling to fit
- **Analysis runtimes**: Node.js and Python, each with its own memory setting

[Read the limits docs](https://docs.tago.io/docs/tagodeploy/project/limits)

## Every service reports its own health

Every service charts its own load, and the Monitoring add-on alerts you when a metric crosses a threshold you set.

- **Charts**: each service charts its own metrics: CPU and memory for the API and apps, connections and IOPS for the Main Database
- **Monitoring add-on**: a separate app that turns thresholds on those metrics into alerts
- **Actions**: the add-on sends each alert by email, SMS or webhook
- **Logs**: the add-on records every check

[Read the monitoring docs](https://docs.tago.io/docs/tagodeploy/project/monitoring)

## You pay a flat license plus what you use

TagoDeploy is post-paid: a flat monthly platform license plus what each service uses.

- **Post-paid**: a flat monthly platform license plus actual resource use
- **By service**: charges split by each billed service
- **Month to date**: spend, daily average and last month's total
- **History**: cost over time, per service

[Read the bills docs](https://docs.tago.io/docs/tagodeploy/project/bills/billing)

## Pick a region for each project

Pick the region per project, near your devices or where your residency rules require.

- **Per project**: the region is chosen when the project is installed
- **Mixed**: projects under one account can sit in different regions
- **Coverage**: 12+ AWS regions across the Americas, Europe and Asia Pacific

- US East (N. Virginia)
- US East (Ohio)
- US West (N. California)
- US West (Oregon)
- Canada (Central)
- EU (Frankfurt)
- EU (Stockholm)
- EU (Ireland)
- EU (London)
- EU (Paris)
- Asia Pacific (Tokyo)
- Asia Pacific (Seoul)
- Asia Pacific (Osaka)
- Asia Pacific (Mumbai)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
- South America (São Paulo)

[Read the new project docs](https://docs.tago.io/docs/tagodeploy/new-project)

## You decide who can reach it

You set the domains, tokens, roles and backups for each project.

- **Default domains**: each service answers at {service}.{id}.tagoio.net
- **Custom domains**: your own hostname for TagoRUN or the API, added in a three-step wizard
- **Tokens**: full access, shown once, revoked for good, ten per project
- **Roles**: Admin for full access, Contractor for scoped access by outside contributors
- **Backups**: daily, kept for a retention period you set, restored into a new isolated instance

[ISO 27001 covers TagoIO as a company](https://tago.io/trust)

## Part of the TagoIO product family

TagoIO is a full-stack IoT cloud platform. Each product covers one part of building, running, and scaling an IoT solution.

## Frequently Asked Questions

### When do I need TagoDeploy?

Use TagoDeploy to launch your own admin portal in a dedicated instance in any location available worldwide. Whether you need to optimize the operational cost of your IoT solution based on a high number of devices, massive data storage, and high-frequency updates, TagoDeploy is your choice.

### What is the difference between the TagoIO Platform and TagoDeploy?

TagoIO is your IoT platform to manage sensors, data, users, analytics, and to provide insights through a customized portal using your brand. TagoIO Platform is available in a multi-tenant and a single-tenant version. TagoDeploy is used to configure, manage, and deploy your own TagoIO single-tenant version. This version can have high rate limits, lower costs for a high volume of data and devices, and many more options.

### How will I be charged?

TagoDeploy is post-paid: a flat monthly platform license plus the resources you actually use.

### Where is my data stored?

In the AWS region you pick when you create the project. TagoDeploy offers 12+ AWS regions: N. Virginia, Ohio, N. California, Oregon, Canada, Frankfurt, Stockholm, Ireland, London, Paris, Tokyo, Seoul, Osaka, Mumbai, Singapore, Sydney, São Paulo.

### Is an on-premises version available?

Currently, TagoDeploy projects are managed by TagoIO using AWS servers. Our team is working on an on-premise version.

### If I already have a TagoIO account, can I migrate it to TagoDeploy?

Currently, there is no process to automatically migrate all data from an account at TagoIO (admin.tago.io) to a specific deployment with TagoDeploy.

### Can I deploy my portal in different regions?

Yes, you can deploy each project under a TagoDeploy account in a different region. For example, you can deploy an instance in Japan and another in Ireland.

### Is TagoIO ISO 27001 certified?

Yes. TagoIO's information security management system is certified to ISO 27001, and the certificate is available on request.

### What happens while a deployment runs?

You cannot make further changes until it finishes, and the project keeps serving the previous version in the meantime.

### What does restoring a backup produce?

A new, independent project built from the snapshot. Your original project is never overwritten, and the new one is billed like any other project.

### Can collaborators manage billing?

No. Admins and Contractors can view and edit project resources, but neither can manage billing or delete the project.

## Run TagoIO on an instance that is yours

Tell us what you run and where. We size the instance with you, or you can price it yourself first.

- [Talk With an Expert](https://tago.io/request-demo)
- [Calculate My Cost](https://tago.io/cost-calculator-deploy)

[llms.txt](https://tago.io/llms.txt)