ThingsBoard Cloud

Best Self Hosted Alternatives to ThingsBoard Cloud

A curated collection of the 9 best self hosted alternatives to ThingsBoard Cloud.

Cloud-hosted IoT platform for device connectivity, telemetry ingestion, rule-based processing, device management, dashboards and alerts. Exposes APIs and integrations to collect, visualize and act on data from distributed IoT deployments.

Alternatives List

#1
ThingsBoard

ThingsBoard

Open-source IoT platform for device management, telemetry collection, rule-based processing, alarms, and real-time dashboards using standard IoT protocols.

ThingsBoard is an open-source IoT platform for connecting, managing, and monitoring devices while collecting, processing, and visualizing telemetry data. It supports both on-premises and cloud deployments and is designed for scalable, fault-tolerant IoT solutions.

Key Features

  • Device and asset management with entity relationships and server-side APIs
  • Device connectivity via MQTT, CoAP, and HTTP(S)
  • Telemetry ingestion and storage with real-time visualization dashboards
  • Extensible widgets and dashboard building, including SCADA-style dashboards
  • Rule Engine with configurable rule chains for processing, enrichment, routing, and actions
  • Alarms management with propagation across entity hierarchies
  • Multi-tenancy support for tenants, customers, and role-based administration
  • Remote device control via RPC and attribute management

Use Cases

  • Industrial monitoring and SCADA dashboards for operational control
  • Fleet and asset tracking with real-time maps and alerts
  • Smart metering/energy monitoring with threshold-based alarms and reporting

Limitations and Considerations

  • Full functionality (e.g., clustering/microservices capabilities) depends on the chosen deployment mode and supporting infrastructure.

ThingsBoard is well-suited for teams that need a device-agnostic IoT backend with strong visualization, rule-based automation, and multi-tenant support. It provides a solid foundation for building production IoT applications that require reliable ingestion, processing, and operational dashboards.

20.9kstars
6kforks
View Details
#2
Eclipse Mosquitto

Eclipse Mosquitto

Eclipse Mosquitto is a lightweight, open-source MQTT broker supporting MQTT 5.0 and 3.1.1, plus client libraries and CLI tools for pub/sub messaging.

Eclipse Mosquitto screenshot

Eclipse Mosquitto is an open-source message broker that implements the MQTT protocol (MQTT 5.0, 3.1.1, and 3.1). It is designed to be lightweight and efficient, making it suitable for IoT-style publish/subscribe messaging from small devices to full servers.

Key Features

  • MQTT broker with support for MQTT v5.0, v3.1.1, and v3.1
  • TLS support for encrypted client connections
  • Authentication options including username/password and pluggable security extensions
  • Access control via ACLs to restrict topic publishing and subscribing
  • WebSockets support for MQTT clients in web environments (optional build feature)
  • Includes client utilities (mosquitto_pub, mosquitto_sub) and C/C++ client libraries

Use Cases

  • IoT messaging backbone for sensors, gateways, and embedded devices using pub/sub
  • Smart home and industrial telemetry aggregation and command distribution
  • Lightweight MQTT broker for development, testing, and internal messaging systems

Limitations and Considerations

  • Advanced enterprise features like clustering and high availability are not part of the core open-source broker
  • Some capabilities (for example, WebSockets or SRV lookups) may require optional build-time dependencies

Mosquitto is a solid choice when you need a small, fast, standards-compliant MQTT broker with strong protocol support and common security mechanisms. It scales from simple local testing to production deployments where reliable MQTT message routing is required.

10.5kstars
2.6kforks
View Details
#3
ESPHome

ESPHome

ESPHome generates custom firmware for ESP32/ESP8266 and other boards from YAML, enabling local smart home devices with Home Assistant, API, and MQTT integration.

ESPHome screenshot

ESPHome is an open-source firmware framework that turns supported microcontrollers into configurable smart home devices using simple YAML files. It generates and builds device firmware, then lets you control and monitor devices locally via integrations such as Home Assistant, native API, web interfaces, and MQTT.

Key Features

  • YAML-based configuration for creating custom sensors, switches, displays, and more
  • Broad hardware support via modular components (many sensors, buses, and peripherals)
  • Seamless Home Assistant integration (commonly used via the Home Assistant add-on)
  • Multiple control interfaces including native API, web UI, and MQTT
  • On-device automations for local logic and reduced dependency on a central controller
  • Over-the-air (OTA) firmware updates for remote maintenance
  • Local-first operation designed to work without cloud dependencies

Use Cases

  • Build DIY smart home sensors (temperature, air quality, presence) and actuators (relays, lights)
  • Deploy locally controlled smart devices for homes and small commercial installations
  • Prototype and standardize firmware for hardware products targeting ESPHome ecosystems

Limitations and Considerations

  • Requires flashing compatible hardware and ongoing firmware management practices
  • Hardware feature support varies by chip family and component; some advanced use cases may require custom components

ESPHome is a strong fit for anyone who wants reliable, locally controlled smart home devices without writing embedded C++ from scratch. Its YAML workflow, broad component ecosystem, and OTA updates make it practical for both hobbyist and professional deployments.

10.4kstars
5kforks
View Details
#4
evcc

evcc

Open-source EV charge controller that optimizes vehicle charging with PV, batteries and dynamic tariffs; supports many chargers, vehicles and smart-home integrations.

evcc screenshot

evcc is an open-source energy management system focused on electric vehicle charging. It controls chargers and smart sockets to maximize PV surplus, use favorable tariffs, and coordinate with home batteries and vehicles.

Key Features

  • Local-first EV charge control that adjusts charging power to PV surplus and dynamic electricity prices.
  • Broad hardware support: many EV chargers, vehicle APIs, inverters, home batteries, smart plugs and energy meters are supported and tested.
  • Protocol and plugin support including OCPP, EEBus, Modbus, SunSpec, MQTT, HTTP/JSON and scriptable extensions for custom devices.
  • Dynamic tariff and price-based scheduling, PV-surplus charging, load management for multi-vehicle and multi-system setups.
  • Responsive web UI with light/dark modes and a public demo instance for exploration.
  • Lightweight Go backend with a TypeScript/Node-based frontend toolchain; designed to run on low-resource devices (Raspberry Pi) or in Docker.
  • Integrations with common smart-home platforms (Home Assistant, openHAB, ioBroker) and vehicle services for SOC, remote charge and preconditioning.

Use Cases

  • Homeowners with PV systems who want to prioritize solar surplus for EV charging and lower grid consumption.
  • Multi-vehicle homes or small installations needing coordinated load management to avoid overloading the connection.
  • Installers, power users and developers evaluating integrations or testing via the public demo and extensive device plugin support.

Limitations and Considerations

  • Initial setup requires intermediate technical knowledge (editing YAML, CLI familiarity) and can be time consuming for complex integrations.
  • The project relies primarily on community channels for support; individual paid support is not directly offered by the core team.
  • Feature availability depends on device APIs and vendor interfaces; some integrations may be partially limited by manufacturer capabilities.

In summary, evcc is a flexible, community-driven EV charge controller and home energy manager designed for local operation and broad device compatibility. It is optimized for PV-first charging scenarios and offers extensible plugins for custom hardware and smart-home integrations.

6kstars
1.2kforks
View Details
#5
WebThings Gateway

WebThings Gateway

Self-hosted smart home hub that unifies device control, automation, and floorplan visualization while preserving privacy.

WebThings Gateway screenshot

WebThings Gateway is a self-hosted software distribution that lets you monitor and control your smart home from a private hub. It provides a unified web interface, automation rules, and a floorplan view while emphasizing privacy and interoperability.

Key Features

  • Unified web interface to monitor and control all devices
  • Drag-and-drop rules engine for automations
  • Interactive floorplan to visualize device placement
  • Time-stamped data logging for trends and insights
  • Adapter add-ons to connect new devices and protocols
  • Docker and Snap packaging for flexible deployment
  • Open, standards-based Web of Things API

Use Cases

  • Private home automation hub with local data storage and control
  • Cross-protocol device integration via add-ons for centralized management
  • Local data visualization and scheduled automations without cloud dependence

Limitations and Considerations

  • WebThings Gateway 2.0 introduces API and OS changes; some add-ons may require updates to remain compatible
  • Raspberry Pi OS-based images for earlier versions are deprecated; migration to Docker or Snap is recommended
  • Some advanced features may require technical familiarity or manual configuration

Conclusion WebThings Gateway enables private, standards-based control of your smart home with local-only operation and an extensible add-on ecosystem. It is actively developed by an open community with ongoing updates through containerized deployments.

2.6kstars
330forks
View Details
#6
OpenRemote

OpenRemote

OpenRemote is a 100% open-source IoT platform for device management, data dashboards, and automation with rules, APIs, and multi-tenant user management.

OpenRemote screenshot

OpenRemote is a 100% open-source IoT platform for connecting, managing, and monitoring devices and assets. It provides device provisioning, automation rules, and dashboards to analyze and visualize live and historical data, with multi-tenant support for serving multiple customers or organizations.

Key Features

  • Device and asset management with customizable asset types
  • Secure connectivity via APIs and protocol integrations (e.g., MQTT, HTTP/REST, WebSocket)
  • Automation using a rules engine with drag-and-drop flows and scripting (JavaScript and Groovy)
  • Alerts and notifications based on live telemetry and events
  • Dashboard and insights builder for data visualization
  • Multi-tenancy (realms) with users, roles, and restricted access
  • Extensible web components for building custom web apps for installers and end-users

Use Cases

  • IoT manufacturers managing distributed devices with provisioning, monitoring, and updates
  • System integrators unifying multiple on-site systems into a single monitoring and control platform
  • Energy management and smart building scenarios using rules, alarms, and dashboards

Limitations and Considerations

  • Historical attribute data retention is governed by configurable purge policies, which may require tuning for long-term analytics needs

OpenRemote fits teams that need an end-to-end, customizable IoT foundation: connectivity, asset modeling, automation, and visualization in one platform. Its multi-tenant architecture and extensibility make it suitable for both single deployments and solutions delivered to multiple customers.

1.6kstars
406forks
View Details
#7
ioBroker

ioBroker

Open source IoT integration and automation platform with an adapter ecosystem, centralized state database, and tools for visualization and data logging.

ioBroker screenshot

ioBroker is an integration platform for IoT and smart home automation that connects many different systems through a large adapter ecosystem. It provides a common data model with object metadata and state values, enabling automation, visualization, and data logging across devices and services.

Key Features

  • Adapter-based architecture to integrate heterogeneous smart home and IoT systems
  • Central object and state databases with event-based updates
  • Optional Redis backend for state storage and pub/sub messaging
  • Runs on many platforms supported by Node.js (Linux, Windows, macOS; ARM/x86)
  • Designed to run multiple adapter instances as separate processes for flexibility

Use Cases

  • Unify devices and services from different vendors into a single automation system
  • Build dashboards/visualizations and log sensor/actuator data for analysis
  • Implement home automation and building automation workflows using adapters

Limitations and Considerations

  • Memory usage scales with the number of adapter instances because each runs as a separate process
  • Intended for trusted networks; exposing components to the internet requires careful hardening (HTTPS, VPN, reverse proxy)

ioBroker is a solid choice when you need a self-managed automation hub that focuses on interoperability and extensibility. Its database-centered model and adapter ecosystem make it suitable for both small smart homes and more complex IoT deployments.

1.4kstars
156forks
View Details
#8
Emoncms

Emoncms

Open-source web app to collect, process, store, and visualize energy, temperature, and other environmental time-series data with dashboards, graphs, and an API.

Emoncms screenshot

Emoncms is an open-source web application for processing, logging, and visualizing energy, temperature, and other environmental sensor data. It is part of the OpenEnergyMonitor ecosystem and is commonly used to build local energy monitoring and reporting systems.

Key Features

  • Input processing pipeline to transform, scale, filter, and route incoming measurements into stored feeds
  • Time-series feed storage optimized for sensor data logging, including built-in PHP-based engines (e.g., PHPFina and PHPTimeSeries)
  • Dashboards and advanced graphing via modular components (dashboard and graph modules)
  • HTTP API for posting data and querying feeds for integration with external devices and systems
  • Optional Redis buffering and processing to reduce disk writes and support certain input processors
  • CSV export and tools for backups/imports depending on installed modules

Use Cases

  • Home and building energy monitoring (electricity, solar PV, heat, hot water)
  • Logging and visualization of temperature, humidity, and other environmental metrics
  • Creating shareable dashboards for energy and sustainability reporting

Limitations and Considerations

  • Some features and workflows depend on optional modules and background workers; deployments without Redis may have reduced functionality for certain processors
  • Official installation guidance and testing focus on Linux environments (notably Debian/Ubuntu and Raspberry Pi OS)

Emoncms is a practical choice when you need a customizable, self-managed platform to ingest sensor readings, store them as time series, and present them through dashboards and graphs. Its API- and module-driven design makes it suitable for both DIY monitoring setups and more integrated energy data systems.

1.3kstars
529forks
View Details
#9
BunkerM

BunkerM

Containerized MQTT management solution bundling a Mosquitto broker with a web UI for ACLs, dynamic security, client management, monitoring and cloud bridges.

BunkerM is an open-source, containerized MQTT management platform that bundles a pre-configured Mosquitto broker with backend services and a web-based management interface. It provides ACL and client management, dynamic security controls, real-time monitoring, and optional cloud bridge integrations for IoT deployments.

Key Features

  • Pre-packaged Mosquitto MQTT broker with a web management UI and backend services
  • Dynamic security module for runtime user/role/group ACLs and permission management
  • Real-time dashboard with connected clients, message statistics, retained message counts and activity logs
  • Client management: create clients, set credentials, assign roles/groups and control connections
  • Role and group-based ACLs with topic permission rules and priority handling
  • Protocol support for MQTT v3.1.1 and v5, TLS/MQTTS and WebSockets/WSS
  • Container-first deployment with Docker images and persistent volume support for data and configuration
  • Cloud bridge integrations (Pro/Enterprise) for AWS IoT Core, Azure IoT Hub and other backends
  • Enterprise features (Pro/Enterprise): RBAC, SSO/LDAP, clustering/HA, enhanced monitoring and REST APIs

Use Cases

  • Manage and monitor MQTT brokers and fleets of MQTT clients in edge and IoT environments
  • Enforce fine-grained topic-level access control and role-based permissions for devices and applications
  • Bridge on-premises MQTT deployments to cloud IoT platforms and exporters for metrics/analytics

Limitations and Considerations

  • Several enterprise-grade features (clustering/HA, LDAP/SSO, advanced analytics, some cloud bridges) are gated behind Pro/Enterprise editions
  • Audit trail, offline authentication and certain protocol extensions require higher-tier or on-demand/custom implementations
  • Primary distribution is containerized; production deployments should plan persistent storage, TLS cert management and appropriate network/firewall configuration

BunkerM is suitable for small to large MQTT deployments that need an integrated management interface and dynamic ACL controls. It lowers the operational overhead of running Mosquitto while offering paid upgrades for enterprise requirements.

329stars
17forks
View Details

Why choose an open source alternative?

  • •Data ownership: Keep your data on your own servers
  • •No vendor lock-in: Freedom to switch or modify at any time
  • •Cost savings: Reduce or eliminate subscription fees
  • •Transparency: Audit the code and know exactly what's running