
Control everything. Manage nothing.
Every system in the building on one platform — controlled from the wall, from a phone, or not at all, because most of the time it runs itself.
Three parts, one system
Nexus is the platform. Underneath it are three named pieces: the hardware on the property, the software people actually touch, and the connection to our support team. Every project has the first two. The third is yours to decline.
A local controller, one per space. It speaks to your lights, locks, thermostats and screens directly, and it holds the schedules and automations itself. Power and a network drop are all it asks for. If the connection to the outside world drops, nothing in the building notices.
The interface everyone actually uses — dashboards, schedules and automations, laid out the same way on a wall panel, a phone or a tablet. We design the layout around the space at commissioning, so what a person sees is what that room needs rather than a list of devices.
Secure access from off the property, platform updates, monitoring, and real-time remote support from the same team that programmed the system. Optional by design: decline it and everything above keeps running exactly as it did.
What it controls
The systems below are where projects usually start. They are not the boundary. If a thing can be controlled, it belongs on the same dashboard as everything else.
The part that runs without anyone
A control system that only responds to being touched is an expensive light switch. Most of what Nexus does happens because a condition changed, not because somebody asked.
Nothing to figure out
The best outcome is that nobody thinks about the system at all. Every install has a physical control that behaves the way a light switch behaves, and an app for the people who want one.
Keypads and switches that do the obvious thing. Somebody can walk into a space, press one button and get the room they wanted without being taught anything first.
Dashboards on a phone, a tablet or a wall panel, laid out per space at commissioning. For the people who do want the detail, all of it is there.
Most of the time nothing gets pressed. The system has already set the room from occupancy, daylight and schedule before anyone reaches for a control.
Open by default, local by design
None of this is a tier, a setting or an upgrade. It is how the platform is built, and it does not change from one project to the next.
It runs on the property
Control, schedules and automations execute on the hub itself. The system does not need the internet in order to work, and it does not stop when a connection does.
It is vendor-agnostic
Nexus talks to thousands of devices across the common wired and wireless standards, so the lights, locks and thermostats you already own generally stay where they are. We will tell you what integrates before you commit to anything.
Your data stays put
Device data lives on the property by default. What leaves is what you choose to send.
Nothing is licensed per feature
There is no premium tier and no per-feature unlock. A capability the platform has is a capability your system has.
Want the detail for your project?
Tell us the building. We will come back with the system design, the hardware list, and exactly what your trades would be doing.
Talk to us about your project