ThingsBoard Self-Hosted
Source-available IoT device, telemetry and dashboard platform.
7 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Kubernetes manifests
Runs in
Documented customer environment
ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths.
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
AWS ↗ · Source checked 2026-11-19
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Azure ↗ · Source checked 2026-11-19
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
GCP ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Kubernetes manifests |
|---|---|
| Infrastructure | Servers / containers ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Source Available Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions. |
| License | Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The ThingsBoard guide configures OAuth2/OIDC clients and domain-specific callbacks for Web UI or mobile login, including Keycloak, Okta, Azure and social providers. Configure issuer/JWKS, trusted claims, tenant/customer mapping and account-creation policy. Device transport credentials and API tokens are separate; the selected release licence still applies.
Current self-hosted ThingsBoard user login and identity mapping, distinct from device authentication · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The current Ubuntu guide installs a versioned application package, Java and database, then initializes the schema and starts the service. AWS guidance separates single-VM, EKS monolith and microservice topologies. Select matching application/manifests and dependencies, replace sample secrets, and configure TLS, persistence, mail and licence activation.
Official native package installation; AWS reference topologies and provider images have separate versions · Source ↗ · Deployment artifact ↗ (v4.4.0.2 application package release; match provider image/manifests separately) · Official AWS deployment choices ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Ubuntu guide distinguishes a 1-core/4 GB/20 GB proof of concept from small production at 2 cores/8 GB/50 GB SSD and a larger starting tier at 4+ cores/16+ GB/100+ GB SSD. Queue/database choices add resources; the heap example is not total host capacity. Device/message rate, retention and HA require separate sizing.
Current single-host tier recommendations; not a 1 TB microservice/HA sizing guarantee · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
Edition-dependentEvidence and scope for License pricing
Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.
ThingsBoard Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Edition-dependent · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Reviewed upstream v4.4.0.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
ThingsBoard Self-Hosted upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
Category fit
- Data & analytics
- Source-available IoT device, telemetry and dashboard platform.
- Observability
- Source-available IoT device, telemetry and dashboard platform.
Compare within Data & analytics
- ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
- Azure
- Airbyte Self-ManagedSelf-managed data movement and ELT platform with customer-operated connectors and job execution.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
- AWS
- Azure
- Alibaba Cloud
- Apache DruidColumn-oriented analytics database for interactive queries over streaming and historical event data.
- AWS
- Azure
- Google Cloud
- Apache SupersetBusiness intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.
- AWS
- AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
- AWS
- Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
- Azure
- Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
- Google Cloud
Showing 8 of 43 other listings in Data & analytics. These products address related workflows; read their category-fit notes before comparing scope. See all of Data & analytics →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- AWS ↗thingsboard.io
- Azure ↗thingsboard.io
- GCP ↗thingsboard.io
- v4.4 Unification ↗thingsboard.io
- Smart Energy ↗thingsboard.io
- BUSL-1.1 ↗github.com
- Releases ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- AWS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
- Azure ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
- GCP ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.
- AWS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked