ThingsBoard hosting in Germany,
on a dedicated instance.
M: from 159.80 € · L: from 219.80 € net per month with Essential. Higher service levels follow WZ-IT terms and include the first registered workload. Non-binding monthly indication for a standard environment in Germany. Setup, migration, additional integrations and vendor licences are quoted separately according to scope. Term and notice period are defined in the proposal.
- Dedicated instance, not a shared tenant
- Data centre in Germany
- Data processing agreement included
- Setup according to agreed scope
WZ-IT assesses your configuration and agrees provisioning and operations with you.
Non-binding monthly indication for a standard environment in Germany. Setup, migration, additional integrations and vendor licences are quoted separately according to scope. Term and notice period are defined in the proposal.
What GDPR-compliant ThingsBoard hosting actually means
Four things decide whether your IoT platform holds up in an audit. Server location is only the first of them.
- 01
Telemetry looks harmless at first: timestamp, value, device ID. The moment a device is tied to an apartment, a vehicle, a meter or a workstation, personal data enters the picture. Consumption curves reveal presence, position data produces movement profiles, machine data allows conclusions about individual shifts. At that point the GDPR applies, and the place of processing stops being a matter of taste.
- 02
Anyone using a hosted platform remains the controller, while the operator is a processor. Article 28 GDPR requires a contract that defines subject matter, duration, nature and purpose of the processing and documents the technical and organisational measures. Without it, the processing is formally exposed no matter how clean the technology is. You get the data processing agreement from us; it is part of every plan.
- 03
If processing happens outside the EU, or the provider belongs to a US group, Chapter V of the GDPR is added on top. Third-country transfers need their own legal basis, and the US CLOUD Act obliges US companies to hand over data even when the servers sit in Europe. The EU-US Data Privacy Framework eases the situation but does not end the debate.
- 04
A German location with a German processor keeps that chain short: no third-country transfer to justify, no additional transfer risk assessment, and one supervisory authority responsible for both sides. At thingshost that is the default setup, not a special configuration.
A dedicated instance instead of a shared tenant
Your devices, telemetry and rules run on a dedicated instance with its own database and assigned resources.
Your own database
Devices, attributes, relations and telemetry live in a PostgreSQL instance that belongs to your deployment alone. No shared table with other tenants.
Your own resources
CPU, RAM and NVMe storage are assigned to your instance. A load spike at another customer never reaches your rule engine.
Your own domain
A subdomain under thingshost.de by default, your own domain with your own certificate on request. The interface then carries your name, not ours.
Coordinated maintenance
Updates and maintenance windows can be scheduled with you instead of applying to an entire platform at once.
Full export
A complete export of the instance including the database is available at any time. Moving back in-house or to another provider stays open.
Tenants for your customers
You still use the multi-tenant features of ThingsBoard, but for your own departments or end customers rather than shared with strangers.
What operations include
Managed does not mean somebody sets the instance up once and hopes for the best afterwards.
Updates across the stack
ThingsBoard, PostgreSQL and the MQTT broker are patched, not just the application. Security-relevant updates are prioritised.
Automatic backups
Backups run automatically and stay in the same region as the instance. There is no silent replication into another jurisdiction.
24/7 monitoring
Availability and system metrics are monitored around the clock. What is collected are operational metrics, not the content of your telemetry.
99.9 % SLA
Essential: Initial technical response to critical incidents (P1) by the end of the next business day, Mon-Fri, 08:00-17:00 CET/CEST · Business: Initial technical response to critical incidents (P1) within 4 service hours, Mon-Fri, 08:00-18:00 CET/CEST · Priority: Initial technical response to critical incidents (P1) within 1 service hour, Mon-Fri, 08:00-18:00 CET/CEST · Production: Initial technical response to critical incidents (P1) within 60 minutes, 24/7, P1 around the clock · Critical: Initial technical response to critical incidents (P1) within 30 minutes, 24/7, including callback, P1 around the clock. Production and Critical require technical acceptance. Critical is capacity-limited. Response targets apply to P1 incidents through the agreed ticket system, not to every request or a guaranteed resolution time. The flexible operations allowance applies to planned work during regular service hours and expires at month end. Operations, monitoring, backups, maintenance and updates within the agreed scope do not reduce it. Additional and incident work costs €120 net per hour in 6-minute increments during regular service hours and €240 net per started hour outside them.
Growth without migration
Storage and instance size can be extended without changing platform. For larger jumps we plan the maintenance window together.
No lock-in
Setup according to agreed scope, contract term according to proposal. On exit you get a complete export, not just temporary API access.
Data center certifications
Germany is the standard location. Other locations and their operating conditions are assessed on request before quoting. Location, backup destinations and responsibilities are documented.
What we are responsible for is the operation of your instance: patch levels, backups, access management, monitoring and incident response. That is exactly the part you need documented for your own ISO 27001 certification or for evidence under NIS2, and that is the part you get from us.
Eight regions, when it does not have to be Germany
Germany is the default region. If your devices or your users sit elsewhere, the instance can run there too: Netherlands, USA, Canada, Singapore, Japan, Australia and India.
For deployments across several countries, two things matter: latency between devices and instance, and which data protection regime applies at the location. Inside the EU, Germany and the Netherlands avoid a third-country transfer entirely. Outside the EU the location becomes a deliberate decision, one we walk through with you before you start rather than hiding it in the checkout.
Who runs the instance
thingshost is a hosting service by WZ-IT. The team takes responsibility for operations and support. Timo and Robin agree requirements, responsibilities and service levels with you.
This is a small operation, and we write that down instead of hiding it behind a logo. What follows from it is handled explicitly: backups are kept independently of the running system, administrative access to your instance is documented in the data processing agreement, and a full data export is yours at any time, including when you decide to move to another provider.
How you get to your instance
From signup to a running platform it takes four steps.
- 1
Start the instance
Provisioning, any pilot and contract terms are agreed in the proposal. There is no automatic trial subscription.
- 2
Connect devices
MQTT, CoAP or HTTP, plus the usual integrations. Existing device profiles and credentials can be carried over.
- 3
Bring your dashboards
Export dashboards, widgets and rule chains from your current instance as JSON and import them here. Same software, not a rebuild.
- 4
Hand over operations
Provisioning, any pilot and contract terms are agreed in the proposal. There is no automatic trial subscription.
Hosting by WZ-IT
One team for your hosting and everything running on it.
thingshost is a hosting service by WZ-IT. We connect infrastructure, software and ongoing operations. Timo and Robin discuss your requirements and agree who is responsible for what.
- Directly with Timo and Robin - no sales handoff
- Operations and support under the agreed WZ-IT service levels
- Commission hosting and additional project work separately
A WZ-IT team consultation to get acquainted and discuss your requirements.
More about WZ-IT
Read on
ThingsBoard Cloud alternative
When a dedicated ThingsBoard instance fits and which operating questions to clarify before moving.
Cloud or managed hosting
The decision guide on the blog: which operating model fits which fleet size and which compliance need.
EU Data Act and IoT platforms
What the new rules on switching, data export and vendor lock-in mean for your platform.
Frequently asked questions about ThingsBoard hosting in Germany
What does ThingsBoard hosting in Germany cost?+
M: from 159.80 € · L: from 219.80 € net per month with Essential. Higher service levels follow WZ-IT terms and include the first registered workload. Non-binding monthly indication for a standard environment in Germany. Setup, migration, additional integrations and vendor licences are quoted separately according to scope. Term and notice period are defined in the proposal.
Is hosted ThingsBoard GDPR-compliant?+
When operated in the German region, all telemetry, device metadata, dashboards and configuration stay in Germany, so there is no third-country transfer to justify. A data processing agreement under Article 28 GDPR is part of every plan. GDPR compliance is always a property of your entire processing operation, though, not of the hosting alone: legal basis, purposes, retention periods and data subject rights remain with you.
Do I get a data processing agreement?+
WZ-IT agrees requirements and scope with you and provisions the instance after commissioning. Access and operations documentation are provided at handover.
Where exactly is the data stored?+
In the default configuration, in Germany. That covers the instance itself, the PostgreSQL database holding device metadata and telemetry, and the automatic backups. Seven further regions or an on-premise deployment are available on request.
Which certifications does the data center hold?+
Data centers with ISO 27001 and BSI C5 for the German region, data centers with ISO 27001 and SOC 2 Type II for the others.
How is the instance sized?+
The Community Edition has no licence limit on devices. The limiting factor is how the instance is sized: CPU, RAM, storage and above all the message rate of your fleet. Ten thousand sensors sending one value per hour create less load than a hundred machines sending every second. That is why we discuss your use case before you start and size the instance accordingly, rather than promising a device count that does not match your sending behaviour.
What happens when we grow?+
Storage and instance size can be extended without changing platform. For larger jumps we schedule a maintenance window. For deployments running permanently high message rates there are dedicated configurations with their own database sizing on request.
Can I migrate my existing ThingsBoard instance?+
Yes. Dashboards, widgets, rule chains, device profiles and asset structures export as JSON and import into the new instance. It is the same software, not a rebuild, so your configuration survives. Historical telemetry can be transferred via the REST API, and we help with larger volumes.
Is there a setup fee or a minimum term?+
No. There is Setup according to agreed scope and the contract can be cancelled monthly. On exit you receive a complete export of your instance including the database.
How are a pilot and contract start agreed?+
Provisioning, any pilot and contract terms are agreed in the proposal. There is no automatic trial subscription.
Have ThingsBoard operated for you in Germany
Provisioning, any pilot and contract terms are agreed in the proposal. There is no automatic trial subscription.
WZ-IT assesses your configuration and agrees provisioning and operations with you.
Non-binding monthly indication for a standard environment in Germany. Setup, migration, additional integrations and vendor licences are quoted separately according to scope. Term and notice period are defined in the proposal.