Gladys vs Domoticz: Which to Self-Host?

Quick Verdict

Gladys Assistant is the better choice for users who want a modern, privacy-focused automation platform with a clean UI. Domoticz is better if you need the lightest possible deployment or need support for legacy hardware protocols that Gladys doesn’t cover. For most new installations, Gladys offers a better experience.

Overview

Gladys Assistant is a Node.js-based home automation platform focused on privacy and simplicity. Built by a single developer (with community contributions), it emphasizes a polished user experience over raw feature count. All processing happens locally.

Domoticz is a veteran C++ automation system that’s been running since 2012. It supports a wide range of hardware protocols and runs on extremely constrained devices. It’s functional but shows its age in UI design.

Feature Comparison

Feature	Gladys Assistant	Domoticz
Language	Node.js	C++
UI design	Modern, responsive	Functional, dated
Zigbee	Zigbee2MQTT integration	Zigbee2MQTT
Z-Wave	Z-Wave JS UI	Native Z-Wave
MQTT	Built-in	Built-in
Automation	Scene-based, UI-driven	Lua/dzVents scripting
Camera support	RTSP integration	IP camera support
Docker support	Official image	Official image
RAM usage	200–400 MB	50–150 MB
Mobile app	PWA (installable)	Third-party
Telegram integration	Built-in	Via plugin
CalDAV sync	Built-in	No
API	REST API	JSON API

Installation Complexity

Both platforms deploy easily with Docker. Gladys uses a single container with SQLite — no external database needed. Domoticz is equally simple — single container, single volume.

The difference is in ongoing configuration. Gladys uses a wizard-style setup and scene builder that guides you through adding devices and creating automations. Domoticz dumps you into a functional but dense web UI where you configure hardware and create events through menus and script editors.

Gladys is more approachable. Domoticz is more flexible for power users who prefer scripting.

Performance and Resource Usage

Domoticz is the clear winner here. At 50–150 MB RAM, it runs on hardware that Gladys can’t. A Raspberry Pi Zero handles Domoticz; it would struggle with Gladys.

Gladys needs 200–400 MB RAM — still reasonable for a Pi 3 or any modern mini PC, but noticeably heavier than Domoticz. For any hardware built in the last 5 years, this difference is irrelevant.

Community and Support

Gladys has a smaller but enthusiastic community, primarily French-speaking (the developer is French) with growing English documentation. The project has a clear roadmap and consistent development pace.

Domoticz has a larger community due to its longer history. The forum is active with a mix of languages. Documentation is more extensive but less polished. Development continues but at a slower pace than in earlier years.

Use Cases

Choose Gladys Assistant If…

• You want a modern, clean UI for home automation
• Privacy is a top priority
• You prefer visual scene-building over scripting
• You want CalDAV calendar integration
• You’re comfortable with Zigbee2MQTT and Z-Wave JS

Choose Domoticz If…

• You run extremely constrained hardware
• You need support for legacy RF protocols (RFXCom, etc.)
• You prefer Lua scripting for complex automations
• You need the broadest hardware protocol support
• You want the absolute lightest automation system

Final Verdict

Gladys Assistant is the better platform for new installations. Its modern UI, privacy focus, and growing feature set make it a solid choice for users who want home automation without the complexity of Home Assistant or openHAB.

Domoticz is the pick for resource-constrained setups or users who need legacy hardware protocol support. Its age shows in the UI, but the underlying engine is reliable and battle-tested.

Neither matches Home Assistant’s ecosystem, but both serve specific niches well.

Related

• How to Self-Host Gladys Assistant
• How to Self-Host Domoticz
• Home Assistant vs Gladys
• Home Assistant vs Domoticz
• openHAB vs Domoticz
• Best Self-Hosted Home Automation
• Replace Apple HomeKit