Skip to main content

Fully Managed OpenHAB
as a Service

Deploy OpenHAB as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

OpenHAB is the vendor-agnostic open-source smart-home hub — a Java OSGi runtime that brings Z-Wave, Zigbee, KNX, Matter, MQTT and 200+ other bindings under one rules engine, local-first and on your own server.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

OpenHAB

OpenHAB

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
OpenHAB Preview Image

ABOUT THE SOFTWARE

What is OpenHAB

openHAB is the open-source home-automation hub maintained by the openHAB Foundation e.V. — a vendor-neutral Java OSGi runtime that brings every consumer and commercial smart-home protocol under one rules engine, running on your own server.

openHAB started in 2010. It runs on Java, ships with a native Matter binding and a Matter Bridge that exposes your items back to Apple Home, Google Home and Alexa locally, and includes the new Python Scripting add-on built on GraalPy. The codebase is licensed under EPL-2.0 and maintained by a non-profit registered in Germany.

The community is broad and durable. The official Docker image has been pulled more than 50 million times, the openhab/openhab-addons GitHub repository hosts 200+ official bindings, and the community forum at community.openhab.org has thousands of active members worldwide. openHAB 5.0 alone was contributed to by 140 maintainers across 2,470 commits.

FEATURES

What OpenHAB does

openHAB integrates every major smart-home protocol — Z-Wave, Zigbee, KNX, Matter, MQTT, Modbus and 200+ device-specific bindings — into a single rules engine. Write automations in DSL, JavaScript, JRuby or Python; query state through one REST API; build dashboards in MainUI or Grafana.

Matter binding (Matter 1.4.1)

Native Matter client over Wi-Fi and Thread border routers, with a Matter Bridge that exposes openHAB items to Apple Home, Google Home and Alexa locally. Matter 1.5 device classes — cameras, closures, soil sensors — are on the binding roadmap.

200+ official bindings

Hue, Tado, Netatmo, Shelly, Tuya, Meross, KNX, Modbus, EnOcean, BACnet, IKEA Dirigera, Fronius Wattpilot, Sense Energy, Daikin, LG ThinQ, Mercedes, BMW, Tesla, Ring, Bambu Lab and many more — all in the openhab/openhab-addons repo.

Persistence: rrd4j, MapDB, InfluxDB, JDBC

Five persistence services ship in the distribution. We default to InfluxDB for long-term sensor data plus MapDB for restoreOnStartup; the upstream rrd4j default stays available for sparkline charts where you want it.

HomeKit binding (new in 5.1)

Pull Apple HomeKit devices into openHAB items, alongside the Matter Bridge that pushes openHAB items back out. Useful for households with mixed iOS and Android users who want a single source of truth.

Z-Wave JS for external radio servers

The 5.0 binding talks to a Z-Wave-JS server over TCP, so the radio stays at the property and openHAB itself runs anywhere. Same pattern works for Zigbee via Zigbee2MQTT. Cloud-hosted openHAB stops being limited to cloud-API bindings only.

Rules in DSL, JavaScript, JRuby, Python

Rules DSL for legacy installs, JS Scripting on GraalJS for modern JavaScript, JRuby for full Ruby and the HABApp ecosystem, and the new Python Scripting add-on on GraalPy. Run any combination on the same instance.

Karaf-based modular runtime

OSGi means add-ons load and unload at runtime; you can swap a binding version without restarting openHAB. The Karaf shell gives you a real CLI for diagnostics, reachable through the dashboard's terminal pane.

MainUI + REST API + Grafana

MainUI for the in-house dashboards, the REST API for any meta-tool or fleet dashboard, and Grafana on top of InfluxDB for long-term charts. The REST API is what property managers use to roll multiple instances into one view.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed OpenHAB

openHAB 5 shipped in July 2025 with mandatory Java 21, the end of 32-bit support, and a native Matter binding. Anyone on a 32-bit Raspberry Pi OS image or a frozen openHAB 2.x install has the same decision to make: re-platform the hardware, freeze and lose the new bindings, or move it off the kitchen shelf.

Running openHAB sounds simple on the documentation page — apt install, click around in MainUI, point some bindings at devices. The operational layer that nobody documents is where it gets expensive. JVM tuning at 200+ items. Persistence database choices that look fine in week one and produce sawtooth graphs in month three. The Karaf cache that bloats silently. Add-on ABI mismatches after a minor upgrade. The annual round of breaking changes — Rules DSL to JS Scripting in OH3, Nashorn deprecated in OH4, the Jython add-on superseded by GraalPy in OH5, 32-bit support dropped along the way.

The gotcha most self-hosters hit first is USB radio passthrough. Z-Wave and Zigbee sticks plug into the host machine; Docker, LXC, and most virtualization layers handle USB unreliably, especially after host reboots and kernel updates. The forum has years of threads documenting the chmod o+rw /dev/ttyACM0 ritual and ABI mismatches between a running 4.0.3 core and an upgraded binding. The clean answer for production is to keep a small Z-Wave-JS or Zigbee2MQTT server at the property and let the rest of openHAB run somewhere stable — which is exactly what the new Z-Wave JS binding in openHAB 5 was designed for.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run OpenHAB on DANIAN

openHAB doesn't have one canonical user. The pattern across our customer base is mixed-protocol setups where one rules engine has to talk to everything — and where the operator has stopped wanting to be the family or the building's IT department.

12-PROPERTY SHORT-TERM RENTAL HOST

Replacing per-property hubs with a fleet of openHAB instances

One DANIAN-hosted openHAB per rental, all in the Germany region; small Zigbee2MQTT bridge at each property for the radios. Booking webhooks rotate door PINs and pre-heat the unit before arrival. A meta dashboard on a 13th VPS pulls fleet state through the REST API for a single view.

14-ROOM BOUTIQUE HOTEL

One openHAB instance running rooms, lighting, and front-desk telemetry

Hosted in Netherlands. KNX-IP on the property reachable over a site-to-site WireGuard tunnel; Hue, Tado and IKEA Dirigera over their cloud APIs. The Matter Bridge exposes the lobby and back-of-house items to staff iPads. InfluxDB powers a Grafana energy dashboard for the GM.

SOLO DEVELOPER WITH 280-ITEM SETUP

Moving openHAB off the kitchen Raspberry Pi after the OH5 upgrade

Hosted in Sweden. Zigbee2MQTT on a Pi Zero 2 W at home handles the radios; everything else — rules in GraalJS, InfluxDB persistence, Grafana, Mosquitto — runs on DANIAN. The SD card and the family's "is the smart-home down again" reputation both retired.

COMPARISON

Four ways to run OpenHAB

The math turns on hardware, ops time, and lock-in — not just the subscription line. openHAB doesn't have a like-for-like proprietary SaaS, so the honest comparison is against the closed cloud smart-home platforms most buyers come from, against running it yourself, and against keeping a home server fed.

 PATH1 INSTANCE5 INSTANCES 10 INSTANCESTRADE-OFFS
Closed cloud smart-home 
(SmartThings, Apple Home, Google Home)
$10–15/mo + $100–300 hub$50–75/mo + $500–1.5k hub$100–150/mo + $1k–3k hubVendor's device list; cloud-locked; platform rules engine only.
Self-host openHAB
on a $24/mo production VPS
$24/mo + 5–10h/mo ops$120/mo + 25–50h ops$240/mo + 50–100h opsFull openHAB catalog; you patch, back up, on-call.
Home server 
(Raspberry Pi 5 / Synology DS923+)
€120–150 hardware + 2–4h/mo€600+ hardware + 10–20h/mo€1,200+ hardware + 20–40h/moFull catalog; SD-card wear, kernel updates, hardware fails.
DANIAN Managed OpenHAB€9/mo€45/mo€90/moFull catalog; we patch, back up, monitor; 0 hours of your time.

BY INDUSTRY

OpenHAB for specific industries

openHAB's protocol coverage and rule-engine flexibility make it the natural pick for environments where one closed platform won't cover every device — hospitality estates, multi-property rentals, commercial buildings, and shared workspaces. Each one has its own regulatory and operational shape.

Small hospitality operators run one openHAB instance per property, with the KNX or Modbus gear on the property reachable over a site-to-site tunnel and cloud-API bindings (Tado, Netatmo, Shelly, Hue) handled directly from the hosted instance. The Matter Bridge introduced in openHAB 5 lets front-desk staff see and trigger rooms from any Apple Home device on the local network — a single iPad becomes the lobby control panel.

We pre-tune the JVM heap for 200–500 items, swap out the default rrd4j persistence for InfluxDB so the operator gets clean per-room energy and occupancy logs, and front the dashboards with a reverse proxy that has real authentication. Booking webhooks drive arrival-day HVAC prep; checkout rules rotate door PINs and switch HVAC back to eco. Occupancy-driven climate control is commonly cited in the 15–25% savings range for small hotels at €0.30/kWh — enough to pay back the hub cost in a single winter at most properties.
Hosts with three or more units typically run one DANIAN-hosted openHAB per property plus a meta dashboard pulling everything together over the REST API. The cloud-API bindings (Tado, Shelly, Tuya, Meross, Hue, smart-lock APIs) work fine from hosted instances since the devices have their own cloud paths. Where Z-Wave or Zigbee is in the mix, we recommend a small Z-Wave-JS or Zigbee2MQTT server on-site connected to the hosted openHAB over an encrypted tunnel — the new Z-Wave JS binding in openHAB 5 was built for exactly that split.

The Short-Term Rental Regulation (Regulation 2024/1028) applies from May 2026 and brings new requirements on registered host identity, data sharing with platforms, and stay records. Clean per-property instances with documented data flows are easier to defend than a single shared hub. Typical smart-lock cycle at 4 PINs/property/month × 10 properties = 40 automated rotations a month, with one avoided linen-run paying for hosting at each property.
The recast Energy Performance of Buildings Directive (Directive 2024/1275, in force since 28 May 2024, national transposition deadline 29 May 2026) requires building automation and control systems in non-residential buildings above 290 kW today and above 70 kW by end-2029. A Smart Readiness Indicator must be published for the largest non-residential buildings by 30 June 2027. openHAB on DANIAN handles KNX-IP, Modbus-TCP, BACnet bridges and submeter inputs cleanly; we ship InfluxDB persistence by default so the operator has the long-term energy log a Smart Readiness assessor will ask to see.

Typical building-automation projects following EN 15232 Class A deliver 25–30% energy savings against an unmanaged baseline, per industry guidance from the building-automation industry trade body. The configuration knobs that matter at this scale — schedule-driven ventilation reduction at night, lighting off after last occupant detection, automatic submeter logging into Influx for monthly energy reports — all express cleanly as openHAB rules in JS Scripting or the new Python Scripting add-on.
Coworking operators wire openHAB into the member-management backend (Cobot, OfficeRnD, or a hand-rolled directory) via the HTTP binding or MQTT. RFID badge at the door fires an event; openHAB checks membership status, unlocks the door, switches on the workshop lights, logs the entry. Because openHAB's built-in authentication is light, we put a reverse proxy with proper OAuth in front of every instance so staff and member roles are separate at the network layer, not just inside MainUI.

A typical site automates 8–15 distinct zones — printers, soldering room, laser cutter, kitchen, meeting rooms — from one hosted openHAB. Equipment that has a real safety risk (laser cutters, kilns) gets a hardware interlock rather than a software rule, with openHAB logging access and runtime for the operations log. Local fire and electrical codes apply; smart automation is layered on top of the certified hardware, never instead of it.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

We run the current stable line. We adopt minor releases within roughly two weeks of the official tag landing on Docker Hub, after we've run them in our own staging cluster. We pin the version per customer instance so a major upgrade is always a deliberate choice, not a Tuesday surprise.
Not directly — radios need to be on the same physical machine as their USB stick, and a hosted VPS does not have a USB port at your house. The clean way is to run a small Z-Wave JS or Zigbee2MQTT server at the property and connect our hosted openHAB to it over an encrypted tunnel. The Z-Wave JS binding that shipped in openHAB 5 was designed for that split.
We front every instance with a reverse proxy that terminates TLS, handles authentication, and rate-limits the public surface. openHAB's built-in auth is light, so we never put port 8080 or 8443 directly on the public internet. The Karaf SSH console is closed by default and only reachable through our private network. Customers get a stable custom domain, with HTTPS that renews on its own.
The official minimum is 1 GB free RAM and a single-core CPU, which is fine for a few dozen items. For a real setup with 200+ items, InfluxDB persistence and Grafana, we run instances on 2–4 GB and set EXTRA_JAVA_OPTS to a 2 GB max heap with a 512 MB initial heap so the JVM doesn't spend its first minute warming up. We monitor GC pauses and reach out if a heap bump is the better answer.
Yes — third-party JARs go into the addons/ directory. We do a quick read of the source to make sure nothing surprising is reaching outside the container, but the call on whether to run a community add-on is yours.
openHAB 5 dropped legacy openHAB 1.x add-ons. Most OH2 bindings have OH3+ replacements; for the few that don't, the workaround is either a Python or JRuby rule talking to the device's HTTP or MQTT API.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed OpenHAB for 7 days

No card. Cancel from the dashboard.