WebThings Gateway

Self-hosted smart home hub, honestly reviewed. Built on W3C standards. Currently showing signs of abandonment.

TL;DR

• What it is: Open-source (MPL-2.0) smart home gateway originally built at Mozilla, now an independent community project. Lets you monitor and control IoT devices via a web interface without a cloud middleman [3].
• Who it’s for: Privacy-focused tinkerers who want a browser-based smart home dashboard with W3C standards compliance and a clean, minimal interface. Raspberry Pi hobbyists and small-scale home automation setups [4][5].
• Cost savings: Commercial smart home hubs like Samsung SmartThings or Apple Home tie you to their cloud forever. WebThings Gateway runs free on a Raspberry Pi or a VPS, with no subscription and no vendor dependency — in theory.
• Key strength: Genuinely clean interface, drag-and-drop rules engine, device floorplan view, and built on actual W3C Web of Things standards rather than proprietary protocols [4][5].
• Key weakness: The project appears to have stalled. Last commit on GitHub was January 2023 [2]. The official website was reported as unreachable by community members as recently as June 2024 [1]. The Raspberry Pi image — the primary way most people ran this — is officially deprecated as of v2.0 [4]. For a smart home hub, that’s a serious concern.

---

What is WebThings Gateway

WebThings Gateway is a self-hosted web application for monitoring and controlling smart home devices. You install it on a server or Raspberry Pi, connect it to your devices via add-ons (Zigbee, Z-Wave, Bluetooth, HTTP, and more), and then access a unified web interface from any browser to view device states, create automation rules, and log sensor data over time [4].

The project started at Mozilla in 2017 as “Project Things,” Mozilla’s attempt to apply its open-web philosophy to the emerging IoT market. Mozilla wanted to create an IoT layer that was “decentralised, open and interoperable” — devices with URLs, accessible through standard web APIs, rather than locked into cloud silos [3]. For four years Mozilla’s IoT team shipped twelve gateway releases, translated the software into 34 languages, built out over a hundred add-ons, and reported over 100,000 downloads [3].

Then in August 2020, Mozilla restructured and cut the IoT team. The project was spun out as an independent community project, webthings.io went live, and in December 2020 WebThings Gateway 1.0 shipped as the handover release [3]. Mozilla’s remote access tunneling service was shut down on December 31, 2020, to be replaced by community-run alternatives [3]. That was the pivot. What happened after is the story this review is actually about.

The project is built on W3C Web of Things (WoT) specifications, which is both its primary technical differentiator and the reason it has a smaller ecosystem than alternatives: it demands devices implement the WoT protocol, which most IoT hardware does not natively speak, requiring adapter add-ons to bridge the gap [4][5].

---

Why people choose it

The honest answer is: most people chose it between 2017 and 2021, when it was actively developed by Mozilla. The reviews that exist are largely from that window.

The interface. A developer who built their own home automation setup on WebThings Gateway wrote in December 2020 that it offered “a responsive web interface with essential features well organized” — Things view, Rules, Logs, Floorplan, Settings — and praised it for being lightweight enough to run comfortably on a Raspberry Pi, using approximately 300MB of RAM [5]. That’s still true. The UI is genuinely clean for a self-hosted IoT tool.

The standards bet. The strongest case for WebThings over proprietary hubs was always the W3C WoT foundation. Devices that speak the Web Thing Protocol don’t need per-vendor cloud APIs. A developer documented their entire multi-Raspberry-Pi setup using WebThings Node (a companion server that exposes any device as a WoT thing) to handle GPIO sensors, relays, cameras, and temperature sensors through a single WebThings Gateway instance [5]. That architecture — local, decentralized, all-in-browser — is still appealing in principle.

Mozilla’s trust halo. Early adoption was significantly driven by trust in Mozilla as the stewards. That halo evaporated when Mozilla cut the team. The community has been trying to maintain it, but the numbers tell the story: 2,639 GitHub stars and a last code commit in January 2023 [2].

The tunneling convenience (past tense). One early reviewer specifically praised the *.webthings.io subdomain tunneling service that made remote access work without any router configuration [5]. That service shut down at the end of 2020, and the community replacement has had reliability problems — the official website itself was unreachable for multiple days in June 2024, with community members reporting “server not found” [1].

---

Features

Based on the official website, README, and first-hand accounts from users who ran it:

Core dashboard:

• Grid view of all connected devices with real-time state [4]
• Responsive, browser-based — works on phone, tablet, desktop without an app [5]
• Floorplan view — drag devices onto a floor plan image for at-a-glance room status [4]
• Per-device detail pages with controls

Automation:

• Rules engine with drag-and-drop “if this then that” interface [4]
• Trigger types include device state changes, time schedules
• Action types include device control, notifications
• Rules are visually composed, not scripted — non-technical friendly [4][5]

Logging:

• Time-series sensor data logging built in [4]
• Interactive graphs for identifying trends and anomalies [4]
• No separate InfluxDB or Grafana required for basic sensor history

Add-ons:

• Over 100 add-ons developed during the Mozilla era [3]
• Add-ons bridge protocols: Zigbee, Z-Wave, Bluetooth, TP-Link, Philips Hue, MQTT, and others [4]
• Add-ons also extend the UI and provide notification integrations
• All installable from a built-in add-on directory [5]

Deployment options:

• Docker image (recommended as of v2.0) [4]
• Snap package (experimental) [4]
• Build from source (Node.js, multiple platform dependencies) [2]
• Raspberry Pi image: deprecated as of v2.0 [4]

Remote access:

• Community-run tunneling service (reliability unclear as of 2024) [1]
• Self-managed reverse proxy (nginx/Caddy) as alternative

---

Pricing: SaaS vs self-hosted math

WebThings Gateway is free software under the MPL-2.0 license. There is no cloud tier, no freemium plan, no commercial edition. The only cost is your hardware.

Self-hosted:

• Software: $0
• Raspberry Pi 4 (4GB): ~$55 one-time (if you don’t already own one)
• Or a small VPS: $5–10/month on Hetzner or Contabo
• Power for a Pi running 24/7: roughly $2–4/month at average US electricity rates

Commercial alternatives for comparison:

• Samsung SmartThings Hub: $80–130 one-time hardware. Cloud dependent, no subscription, but Samsung has shut down or pivoted SmartThings features multiple times. No data export guarantee.
• Hubitat Elevation: ~$150 one-time. Fully local, no cloud required, active development, strong community. Closest honest comparison.
• Apple HomeKit / Home: Free if you already own Apple hardware, but locks you into the Apple ecosystem. No local processing without a Home hub ($100+ Apple TV or HomePod).
• Home Assistant (Yellow or Green hardware): $100–130 one-time. Fully local. Active project with 200,000+ community members. The dominant open-source alternative.

Pricing-wise, WebThings Gateway is competitive. The hardware investment is minimal and there’s no recurring fee. But the value of a smart home hub isn’t just the software license — it’s long-term reliability, security updates, and continued device support. On that axis, the calculus looks different.

---

Deployment reality check

The recommended installation path as of version 2.0 is Docker [4]. The old Raspberry Pi OS image that made WebThings approachable for non-technical users is deprecated and stuck at version 1.1 [4]. That’s a significant regression in accessibility.

Building from source requires a substantial dependency list: Node.js (via nvm), Python 3, libboost, libdbus, libbluetooth, and a Bluetooth permissions configuration involving setcap on the node binary [2]. For a technically experienced user on Ubuntu or Debian, this is manageable. For a non-technical founder, it’s a multi-hour battle.

Docker is cleaner, but the compose setup isn’t officially documented with the same clarity that a project like Home Assistant provides. The community wiki fills some gaps, but the wiki at github.com/WebThingsIO/wiki was last actively maintained during the Mozilla era [2].

Remote access is the real problem. The community-run tunneling service that replaced Mozilla’s has had documented availability issues. In June 2024, the entire webthings.io domain went offline for multiple days, with community members unable to reach the gateway, documentation, or website [1]. If you’re self-hosting a smart home hub that your family uses, this is not an acceptable dependency.

The practical fix is to skip the tunneling service entirely and run your own reverse proxy with a domain name and SSL. That’s a step beyond what most non-technical users are comfortable with.

Realistic effort:

• Technical user with Docker experience: 1–2 hours to working gateway, plus additional time per add-on
• Non-technical user: not recommended without hands-on help, given the deprecated Pi image and unclear Docker docs
• Ongoing maintenance: unknown — the project’s maintenance status is unclear as of early 2026

---

Pros and cons

Pros

• Genuinely clean UI. First-hand users consistently describe it as simple and well-organized [5]. The interface doesn’t overwhelm with configuration the way Home Assistant can.
• W3C Web of Things standards. Built on actual standards rather than proprietary protocols — the right long-term bet, even if the ecosystem is thin [4][3].
• Fully local, no cloud required. Device control stays on your network. No subscription, no terms-of-service changes, no data sent to a vendor [4][5].
• Free under MPL-2.0. No commercial edition, no feature gating, no usage limits.
• Lightweight. 300MB RAM footprint means it runs comfortably on modest hardware [5].
• Built-in logging and floorplan. Features that other hubs charge for or require plugins are included by default [4].

Cons

• Project appears stalled. Last GitHub commit was January 2023 [2]. No active releases since then. This is the biggest single risk for anyone betting a smart home on this software.
• Website reliability is poor. The official webthings.io site was down for days in June 2024 [1]. For a project with no other support infrastructure, that’s alarming.
• Raspberry Pi image deprecated. The most accessible deployment path is gone as of v2.0 [4]. Docker is the recommended path, which raises the technical bar.
• Thin ecosystem compared to Home Assistant. 100+ add-ons is respectable, but Home Assistant has 3,000+ integrations with active maintenance. If your specific device isn’t covered, you’ll write your own adapter [3].
• Mozilla’s remote access service gone. The tunneling feature that made this easy to access remotely was shut down at end of 2020 [3]. The community replacement has had reliability problems.
• No mobile app. Everything goes through the browser. Fine in most cases, but push notifications and background automation require workarounds.
• Small community post-spinout. The discourse forum and Matrix channel exist but traffic is light compared to the Mozilla-era activity.
• No active security patches known. With no commits since Jan 2023, any CVEs in dependencies are presumably unpatched.

---

Who should use this / who shouldn’t

Use WebThings Gateway if:

• You’re already a tinkerer who ran it during the Mozilla era and it’s working for your setup — don’t fix what isn’t broken.
• You want to experiment with W3C Web of Things standards and are comfortable potentially replacing the gateway layer later.
• You’re building a controlled demo or educational setup where long-term maintenance isn’t a concern.
• You have a small set of well-supported devices (Zigbee, Philips Hue, TP-Link) and a very simple automation need.

Skip it (use Home Assistant instead) if:

• You’re starting a new smart home setup and want something that will still be maintained in 2027.
• You need broad device compatibility — Home Assistant covers Zigbee, Z-Wave, Matter, Thread, and essentially every mainstream smart home device.
• You want an active community to troubleshoot with.
• You need guaranteed security updates.
• You’re a non-technical founder who wants to self-host a smart home without becoming a Linux administrator.

Skip it (use Hubitat Elevation instead) if:

• You want a truly local hub with hardware included, active development, and no cloud dependency.
• You’re willing to spend $150 once rather than manage a software stack.

Skip it (stay on SmartThings or Apple Home) if:

• You’re genuinely non-technical and the priority is “works without effort.”
• Your devices are natively supported by these platforms and the vendor lock-in doesn’t bother you.

---

Alternatives worth considering

• Home Assistant — the dominant open-source home automation platform. 65,000+ GitHub stars, 3,000+ integrations, active releases, large community. Runs on Raspberry Pi, x86 server, or as a VM. Has a paid cloud service (Nabu Casa, ~$7/month) for remote access, but fully local operation is supported without it. The honest answer for most people.
• Hubitat Elevation — $130–150 hardware hub. Fully local, no cloud, runs Zigbee and Z-Wave natively. Less flexible than Home Assistant but easier to operate. Strong reliability track record.
• openHAB — older open-source hub with a broad integration library. More complex to configure than either Home Assistant or WebThings Gateway. Still actively developed.
• Domoticz — lightweight, runs on low-power hardware, long track record. UI is dated. Niche community.
• Node-RED — not a hub, but a visual automation tool that integrates with MQTT and many IoT protocols. Often deployed alongside Home Assistant or other hubs rather than instead of them.
• Gladys Assistant — newer French open-source project. Clean UI, simpler feature set than Home Assistant. Docker-first deployment.

For a non-technical founder escaping cloud smart home lock-in, the realistic shortlist is Home Assistant vs Hubitat. WebThings Gateway would have been on that list in 2020. Today it’s a historical footnote with a working codebase.

---

Bottom line

WebThings Gateway made a genuinely important bet: that smart home devices should be first-class web citizens, accessible via standard URLs and protocols, not locked into corporate cloud APIs. Mozilla built something clean and technically principled. Then Mozilla’s restructuring cut the team, and the project has been quietly coasting toward inactivity ever since. The last code commit was January 2023. The website went down in June 2024. The Raspberry Pi image — the easy on-ramp that drove 100,000+ downloads — is deprecated.

If you’re considering WebThings Gateway for a new smart home setup, the honest answer is: don’t. Not because the software is bad, but because a hub that controls your lights, heating, and door locks needs to be maintained. Home Assistant has absorbed most of the audience that WebThings Gateway was built for, and it has the community, the integrations, and the release cadence to back it up. WebThings Gateway’s architecture was right. Its timing and its backer’s organizational stability were not.

If someone in the open-source community picks this back up and ships a 2025 release, revisit this review. Until then, it belongs in the “important but dormant” category of self-hosted software.

---

Sources

1. Mozilla Discourse — “Flying the Nest: WebThings Gateway 1.0” (community thread, includes June 2024 website-down reports). https://discourse.mozilla.org/t/flying-the-nest-webthings-gateway-1-0/71603
2. Libre Self-Hosted — WebThings Gateway project listing (GitHub stats: last commit Jan 2, 2023). https://libreselfhosted.com/project/webthings-gateway/
3. Mozilla Hacks — “Flying the Nest: WebThings Gateway 1.0” (David Bryant, December 2020 — full history of Mozilla IoT spinout, feature summary, transition details). https://hacks.mozilla.org/2020/12/flying-the-nest-webthings-gateway-1-0/
4. WebThings Gateway official website (feature descriptions, download options, v2.0 release, Raspberry Pi deprecation notice). https://webthings.io/gateway/
5. Cescobaz.com — “WebThings Gateway: a very lightweight and flexible IoT Gateway” (December 2020 — first-hand setup review with RAM usage figures and architecture details). https://cescobaz.com/2020/12/11/webthings-gateway-a-very-lightweight-and-flexible-iot-gateway/