ThingsBoard Cloud vs private instance

Timo WevelsiepTimo Wevelsiep

ThingsBoard can be consumed as a cloud service or operated as a private instance. The right model depends on data residency, customization, integration depth and operational ownership.

Table of Contents

Short answer

Choose cloud when standard deployment and fast start matter most. Choose a private instance when data location, network isolation, custom integrations or customer-specific operations become deciding factors.

If you already know that you need a dedicated environment, see Managed ThingsBoard hosting.

Deployment tradeoffs

Criterion ThingsBoard Cloud Private ThingsBoard instance
Start speed Fastest path for standard evaluation and early dashboards. Requires setup, sizing, security and operations planning.
Data residency Bound to the provider's cloud model and available regions. Can run in an EU region, dedicated cloud, customer tenant or on-premise environment.
Network access Usually internet-facing with platform-defined boundaries. Can be placed behind VPN, private networks or customer firewalls.
Customization Works well inside standard platform options. Better for custom integrations, branding, extensions and database access patterns.
Operations Platform operation is abstracted by the cloud provider. You or a managed provider own backups, updates, monitoring and scaling.
Commercial fit Good when usage fits published plans and common patterns. Good when costs and architecture should match a specific rollout model.

When a private instance wins

A private instance helps when customers ask where data lives, who can access it and how the environment is isolated.

It also helps when ERP, ticketing, GIS, billing, custom mobile apps or own databases need deeper integration than a standard cloud setup allows.

If your product promise includes uptime and support, the ThingsBoard environment needs the same operational discipline as the product itself.

How merkaio operates ThingsBoard

We focus on dedicated ThingsBoard environments for teams that need control without building an internal platform team:

  • deployment architecture for CE or PE environments
  • database, MQTT, reverse proxy, TLS and backup setup
  • monitoring for availability, storage, queues and integrations
  • rule chain, dashboard and device-model implementation
  • integration with ChirpStack, Grafana, APIs and custom applications

ThingsBoard is a trademark of its respective owner. merkaio is an independent infrastructure and operations provider.

Frequently asked questions

Is a private ThingsBoard instance always better?▼
No. Cloud is often the better starting point for simple evaluation. A private instance matters when control, integration depth or operating requirements justify it.
Can merkaio operate ThingsBoard PE?▼
Yes, if licensing and access are provided by the customer. We can handle infrastructure, deployment, monitoring, updates and integrations.
Can a private instance run on-premise?▼
Yes. We can design cloud, dedicated server, hybrid or on-premise environments depending on network, compliance and availability requirements.
Can ThingsBoard integrate with ChirpStack?▼
Yes. ChirpStack can forward LoRaWAN application data into ThingsBoard through MQTT, HTTP integrations or custom middleware.
NextGrafana vs ThingsBoard for IoT

The platform decision is only the start.

After tool selection come deployment, integrations, monitoring, backups, updates and ongoing operations. merkaio designs and operates IoT stacks with ChirpStack, ThingsBoard, Grafana, MQTT and custom applications.

Managed IoT hostingCustom IoT platform development
Timo Wevelsiep

Written by

Timo Wevelsiep

Founder, merkaio

Builds and operates LoRaWAN and IoT platforms, from ChirpStack to custom applications.

LinkedIn