Gladys

Self-hosted home automation, honestly reviewed. For founders and families who want smart home control without feeding data to Google, Amazon, or Apple.

TL;DR

• What it is: Open-source (Apache-2.0) home automation platform — think Google Home, but the server lives in your house and every device event stays local [1].
• Who it’s for: Non-technical homeowners who want Zigbee, Matter, and voice control without monthly SaaS fees or a command-line obsession. Also founders building privacy-first products who need a self-hosted automation layer [website].
• Cost savings: Smart home SaaS subscriptions (SmartThings, Google Nest, Apple Home hubs with cloud-dependent devices) accumulate fast — $10–30/mo per platform. Gladys core is free; remote access requires Gladys Plus at an undisclosed subscription price. Local operation: unlimited, free [1][website].
• Key strength: Genuinely the cleanest UI in the self-hosted home automation space. No YAML files, no config editors, no terminal once Docker is running. Community testimonials repeatedly call it “simple and intuitive” [website].
• Key weakness: 3,036 GitHub stars vs. competitors with ten times that. Integration catalog is narrower than the market leader. Gladys Plus pricing for remote access is opaque — you don’t know what you’re committing to before you need it [website][1].

---

What is Gladys

Gladys is a self-hosted home automation hub. You run it on hardware in your home — a mini-PC, NAS, or Raspberry Pi — and it becomes the central brain connecting your smart devices, automating your routines, and responding to your voice. Every event, every sensor reading, every command stays on your local network by default [website][1].

The project was started by Pierre-Gilles Leymarie, a French developer who is still the primary maintainer, and has accumulated 3,036 GitHub stars under an Apache-2.0 license. The community has contributed integrations for Zigbee, Matter, MQTT, Google Home, Shelly, Sonos, Somfy, and cameras, among others [README][website].

What makes the Gladys pitch distinct from the pile of other self-hosted automation tools is the stated design priority: “No terminal commands. No config files. Just a beautiful interface that works.” [website] The project also ships Watchtower alongside its Docker image to handle automatic updates — a detail that matters for non-technical users who won’t remember to SSH in and pull a new image [2].

The latest major release at the time of this review is v4.58, which added Matter support — the cross-brand, cloud-free device protocol that the big consumer platforms (Apple, Google, Amazon) have been adopting. Gladys added it via Matterbridge, an open-source bridge project that also makes Shelly, Somfy, and Zigbee2MQTT devices Matter-compatible [5].

---

Why people choose it

The five community testimonials on the Gladys homepage are unusually specific, and they cluster around two themes: simplicity and vacation peace of mind.

One user (@lmilcent) runs alerts for overheated rooms, an open fridge, motion-triggered morning lamps, and leak detection — all from a Raspberry Pi, all without touching code [website]. Another (@guim31) manages gate control, evening lights, pool pump scheduling, and intrusion alerts for a property they monitor remotely while away [website]. A third (@jparbel) notes the free local version covers everything but remote access requires the paid tier — a real tradeoff to flag [website].

The pattern is people who started with ad-hoc home automation tinkering, hit complexity limits with DIY setups, and landed on Gladys as a stable long-term base. The word “stable” comes up repeatedly — including from the creator’s own positioning (“Built to last decades”) [website].

Versus Home Assistant. Home Assistant is the undeniable category leader with a vastly larger integration ecosystem and community. The tradeoff is complexity: Home Assistant rewards YAML fluency and config editing. Gladys explicitly trades raw power for accessibility. If your household has no one who wants to debug a configuration.yaml file, that tradeoff is worth taking seriously.

Versus proprietary hubs (Google Nest Hub, SmartThings, Apple Home). This is where Gladys makes its clearest argument. Every event on a Google or Amazon hub goes through their infrastructure — that’s how their products work. Gladys running on a local machine means the temperature sensor in your bedroom never phones home [website][1]. The Matter integration in v4.58 extends this further: Matter devices communicate locally over your home network, bypassing any manufacturer’s cloud entirely [5].

On the privacy angle. The website is clear and the README repeats it: “No cloud required, no tracking, ever.” [website][README] For users who connect automations to cameras, door locks, and presence sensors, the question of where that data goes is not paranoia — it’s a reasonable operational concern. Gladys’s answer is structural: the software is designed to never need an outbound connection for core functionality.

---

Features

Based on the website, README, blog posts, and installation docs:

Dashboard and monitoring:

• Visual dashboard with customizable widgets [website]
• Gauge widget for tank fill levels, battery levels [5]
• Charts widget with aggregation functions (sum, min, daily/weekly/monthly grouping) — useful for electricity consumption tracking [5]
• Camera integration with live view [website]
• Temperature, humidity, presence monitoring [website][1]

Automation engine (Scenes):

• Visual scene builder — no coding required [website][1]
• Supports conditions, loops, delays [5]
• “Wait” block now supports dynamic values and calculations — useful for presence simulation [5]
• AI block (“Ask AI”) — send a question to an AI model and inject the response into a scene variable, e.g. identify a car in a camera image and trigger an action [5]
• Variables from sensors can flow into scene logic [5]

Integrations:

• Zigbee (via Zigbee2MQTT) [website][5]
• Matter (added v4.58, via Matterbridge) — covers Shelly, Somfy Tahoma, Zigbee2MQTT, Home Assistant devices as Matter bridges [5]
• MQTT [website]
• Google Home, Amazon Alexa, Apple Siri (via voice integration) [website]
• Shelly, Sonos, Somfy directly [website]
• Netatmo thermostats, valves, weather stations [4]
• Camera integration [website]

Voice and messaging control:

• Voice commands via Google Home, Alexa, Siri — “Turn on the light in the kitchen” [website]
• Control and alerts via Telegram, WhatsApp, Signal, NextCloud Talk [5]
• Update notifications sent to administrators via configured messaging channels [5]

Security:

• Alarm system with full and partial arming modes [5]
• Partial arming locks all tablets in the house to prevent intruder access to the UI [5]
• Intrusion detection and notifications [website]

Infrastructure:

• Docker single-container or Docker Compose deployment [1][2]
• Watchtower for automatic updates (bundled in the Compose config) [2]
• SQLite database stored on local volume — no external database required [2]
• Runs on mini-PC, Synology NAS, Unraid, Raspberry Pi, any Docker-capable Linux host [1]

---

Pricing: SaaS vs self-hosted math

Gladys core (local access):

• Free, Apache-2.0, unlimited devices, unlimited automations [website][1]

Gladys Plus (remote access):

• Required for controlling your home when you’re away from the local network
• Pricing is not published on the website or in the provided documentation — you have to contact or sign up to learn the number
• One community reviewer (@jparbel) calls it the “full power” unlock [website]

Self-hosted hardware cost:

• Beelink Mini S12 Pro (recommended): $169 one-time [3]
• Raspberry Pi 4 (not recommended by the Gladys team for long-term use): ~$50–80 plus accessories [1]
• Running cost on a mini-PC: roughly $3–5/month in electricity at typical household rates

Starter kit (Europe only):

• Pre-installed Gladys on a Beelink mini-PC
• Includes 6 months of Gladys Plus and official training videos
• Price not listed in the documentation [1]

Proprietary hub alternatives for rough comparison:

• Google Nest subscriptions (Nest Aware): $6–12/mo
• SmartThings hub: $130 hardware + compatible cloud subscriptions per platform
• Apple Home: free but requires Apple hardware and iCloud account

The honest math here is harder to do than for something like Activepieces because Gladys Plus pricing isn’t public. For purely local use, Gladys is free on hardware you already own. For remote access — which most people want — you’re committing to an unknown recurring cost. That opacity is a real purchasing friction point.

---

Deployment reality check

The installation story is genuinely simpler than most self-hosted tools. The Docker Compose config is 30 lines, includes Watchtower for auto-updates, and requires no external database [2]. The official docs recommend a Beelink mini-PC over a Raspberry Pi — explicitly, and with good reasoning: SD card corruption risk, Zigbee/Z-Wave dongle instability from power supply noise on the Pi [1].

What you need:

• A Linux machine (mini-PC, NAS, VM) with Docker installed [2]
• No external PostgreSQL or Redis — SQLite is the default [2]
• Network access from your browser on the local network
• For remote access: Gladys Plus subscription (remote tunnel or similar mechanism)

Install commands (from Docker Compose):

curl -sSL https://get.docker.com | sh
# create docker-compose.yml from docs
sudo docker compose up -d

Access Gladys by typing your machine’s local IP into a browser [2]. That’s it for local operation.

What can go sideways:

• Zigbee USB dongle compatibility is hardware-specific — not a Gladys problem, but a home automation reality. Budget time for dongle selection [1].
• Matter integration (v4.58) requires running Matterbridge separately — Gladys doesn’t ship it in the default Docker Compose [5]. Another container to manage.
• Remote access requires Gladys Plus, and the setup path for remote tunneling isn’t documented in the materials available for this review.
• Raspberry Pi is officially not recommended by the Gladys team themselves [1]. If that’s what you have, plan a hardware upgrade before going all-in.
• The Compose config mounts /dev into the container and uses --privileged mode, which is necessary for USB device access but worth noting from a security posture standpoint [2].

Realistic setup time for a technical user on a mini-PC: 45–90 minutes including Ubuntu Server installation, Docker setup, and Gladys configuration. For someone following step-by-step docs: 2–3 hours. Remote access setup depends entirely on Gladys Plus onboarding, which isn’t documented in publicly available materials.

---

Pros and Cons

Pros

• Genuinely no config files. The installer guides you through a browser UI from first boot. Community reviews confirm non-technical users can configure rooms, devices, and scenes without touching a terminal [website][1].
• Apache-2.0 license. More permissive than some home automation alternatives. Commercial use, embedding, and redistribution are allowed [README].
• Matter support. v4.58 adds the modern, cloud-free cross-brand protocol, including via Matterbridge which extends compatibility to Shelly, Sonos, Somfy, and Zigbee2MQTT devices [5].
• AI integration in automations. The Ask AI scene block is a concrete, practical implementation — analyze camera images, evaluate sensor values, inject results into automation logic [5].
• Auto-updates via Watchtower. Non-technical users don’t need to remember to maintain the stack [2].
• Active, specific development. v4.58 release notes show concrete, useful additions: gauge widgets, chart aggregation, dynamic wait blocks, alarm tablet locking — not marketing fluff [5].
• Privacy architecture is structural. Core operation requires no outbound internet connection. This isn’t a configuration option — it’s how the software is designed [website][README].
• Presence simulation. Dynamic random delays in scenes (e.g., “wait between 5 and 30 minutes”) for light randomization while away [5].

Cons

• 3,036 stars is small for the category. Home Assistant, the market leader, has orders of magnitude more community, integrations, and documentation. The long-tail device coverage gap is real.
• Gladys Plus pricing is opaque. The one feature most users will eventually want — remote access — is paywalled with no public price. You discover the number after you’ve already committed to the hardware [website].
• Matterbridge is a separate concern. Matter support is real, but it requires running and maintaining an additional container [5]. Not a dealbreaker, but it’s not “automatic.”
• Single primary maintainer. Pierre-Gilles Leymarie is credited across all major decisions and communication. That’s a bus-factor risk for anyone betting a long-term home setup on it.
• Europe-centric starter kit. The recommended plug-and-play hardware bundle ships to Europe only [1]. US users get documentation pointing to Amazon hardware with a DIY install.
• Remote access documentation gap. How Gladys Plus actually works for remote tunneling — the security model, the infrastructure — isn’t explained in the public docs reviewed here.
• Raspberry Pi actively discouraged. If that’s your existing hardware, the official project guidance is to buy different hardware [1]. That’s honest, but it adds cost.

---

Who should use this / who shouldn’t

Use Gladys if:

• You want a smart home hub where all data stays in your house and the software is free to run locally.
• Your household has at least one person comfortable running docker compose up -d once.
• You’re equipping a home with Zigbee, Matter, or Shelly devices and want a visual dashboard without YAML configuration.
• Privacy of sensor data (cameras, presence, door locks) is a genuine concern, not just a preference.
• You want voice control via Google Home, Alexa, or Siri without paying Google or Amazon for a hub subscription.

Skip it (pick Home Assistant instead) if:

• You want the largest possible integration catalog — including obscure or niche devices.
• You’re comfortable editing YAML and want maximum control over every automation.
• You need an active forum with tens of thousands of members troubleshooting edge cases.
• You’re already invested in Home Assistant’s HACS ecosystem.

Skip it (use a proprietary hub) if:

• You have zero tolerance for any maintenance — even occasional Docker container updates.
• Your compliance or lease situation prohibits running a server on-premises.
• You’re fully in Apple’s ecosystem and HomeKit already covers your devices without issues.

Wait before deciding if:

• Remote access is essential to you and you need to know the Gladys Plus price before committing hardware. Get that number first.

---

Alternatives worth considering

• Home Assistant — the obvious comparison. 70K+ GitHub stars, thousands of integrations, active HACS community, Python-extensible, more complex to configure. Apache-2.0. If you’re technically inclined and want maximum coverage, this is the baseline to measure against.
• openHAB — older, Java-based, rule-engine focused. Powerful but steeper learning curve. Good enterprise pedigree.
• Domoticz — lightweight, fast, long-established. UI has not aged as cleanly as Gladys. Smaller active community.
• ioBroker — popular in German-speaking markets, modular adapter system, good hardware support. Less polished UI.
• Homey Pro — commercial hub hardware with a polished app ecosystem. No self-hosting, but genuinely non-technical friendly. ~€400 upfront + possible subscription.

For the target reader — a non-technical homeowner who wants privacy and control without ongoing SaaS bills — the realistic shortlist is Gladys vs Home Assistant. Pick Gladys if UI simplicity and zero configuration matter more than breadth. Pick Home Assistant if you want the largest possible ecosystem and don’t mind the learning curve.

---

Bottom line

Gladys is the best-looking, lowest-friction self-hosted home automation option for genuinely non-technical users. It does what it promises: runs from a single Docker command, shows a clean dashboard, automates scenes without code, and keeps your data local. The Matter support, AI scene integration, and Telegram/WhatsApp alerts are concrete recent additions that show active, practical development.

The real risks are scale and sustainability. A 3,036-star project led by one primary maintainer is a real long-term bet. The integration catalog narrows past mainstream protocols. And remote access — the feature you’ll eventually want — carries an unknown price tag that you should uncover before buying hardware.

If your needs are Zigbee sensors, Shelly devices, presence-based automations, and privacy-first local control, Gladys delivers cleanly. If you need unusual devices, deep API extensibility, or the security of a massive community, look at Home Assistant first and treat Gladys as the friendlier alternative you might migrate to once you’ve outgrown tinkering.

---

Sources

1. Gladys Assistant — Getting Started Documentation. https://gladysassistant.com/docs/
2. Gladys Assistant — Install with Docker Compose. https://gladysassistant.com/docs/installation/docker-compose/
3. Gladys Assistant — Install on a Mini-PC. https://gladysassistant.com/docs/installation/mini-pc/
4. Gladys Assistant — Netatmo Integration Guide. https://gladysassistant.com/docs/integrations/netatmo/
5. Pierre-Gilles Leymarie, Gladys Assistant Blog — “Gladys Assistant Now Compatible with Matter” (v4.58 release notes). https://gladysassistant.com/blog/gladys-assistant-4-58-with-matter-support/

Primary sources:

• GitHub repository: https://github.com/gladysassistant/gladys (3,036 stars, Apache-2.0 license)
• Official website: https://gladysassistant.com