New build
New-build home automation and post-renovation smart homes
Design the smart home before the concrete is poured.
A whole-house project on one screen — planned now, installed in stages.
In short
A new build or a full renovation is the rare moment when automation costs the least: walls are open, cable routes and key points are planned in advance. HoumeOS gives you a local platform that unifies lighting, blinds, climate, security and scenarios on one screen — without locking into a single vendor and without the cloud. The system can be built in stages as the house fills with devices.

Why new construction is the moment
While walls are open, cable routes, positions for key points, panel power and sensor locations are decided once and cheaply. Imposing the same after finishing means chasing walls and compromise. Automation designed into the project costs roughly a tenth of the same automation retrofitted later.
What to plan while walls are open
Runs for switches and blinds, positions for wall panels, power for the server and network, points for leak, smoke and motion sensors. You decide where low-voltage goes now, so you do not have to stretch it later. The specifics are made on a site survey with your designer or electrician.
The whole house on one screen
Lighting, blinds and alarms, climate by room, doors and garage, irrigation, energy and scenarios — on a kiosk with thirteen screens that lives on a tablet, wall panel, phone or computer. One interface instead of ten disconnected apps, every brand in its place inside a shared model.
Scenarios and modes that work offline
Morning and evening modes, leaving home, holiday, emergency actions on leak, gas, smoke and freeze — described without code as trigger → conditions → exclusions → action and executed on the local server. They keep working when the internet drops, because the logic is not in a cloud.
Step by step: from project to handover
We start with analysis and design, then configure the platform and validate scenarios in simulation before the install, connect devices on site, train and maintain. The house grows in stages: new room, new device, new rule — without rewriting the whole system.
What works today and what is coming
We do not present upcoming work as available. This list matches the roadmap.
Works today
- Local platform: rules, modes and history on the server in the LAN
- Kiosk with thirteen screens for the whole house on one interface
- No-code scenarios and roles with PIN, verified on the server (scrypt)
- Grow in stages without lock-in to a single manufacturer
Coming soon
- Built-in voice assistant and interactive floor plan
- More ready device-brand drivers for equipment specified in the project
Later
- Own radio layer inside the platform
- Advanced presence scenarios and tuned automations
Frequently asked questions
Do I need a specific structured-cabling solution from the start?
Not necessarily centralised, but it helps to plan cable routes and power at the key points while walls are open. Some devices can also be wireless (through a bridge to MQTT). The concrete answer depends on the project and is settled on a site survey with your electrician, not from a template.
Can things be done in stages?
Yes, and that is the normal path. The platform is set for the house and devices come in gradually — lighting now, climate and blinds later, cameras and energy at the end. A new model or a new rule never requires rewriting screens that already work.
Am I locked to a single manufacturer?
No. HoumeOS works with a unified device model, so every brand enters as a driver and stays replaceable. That is exactly what makes it a platform rather than one brand’s app: devices change, interface and rules do not.
Does the system work when the internet drops?
Yes. Rules, modes and history run on the local server in your network, not in a cloud, so automations continue even without a link. For a new build that matters: you expect the system to be dependable, not to depend on an external carrier.
We show the system on a live screen
The demo starts from your question: which devices, which protocols, which scenarios.