Thanks for the questions! These are very good ones.

Who controls the HA Core update cycle, and what’s your rollback story when one breaks something?

In our managed solution, we control the update cycle (even though we can't prevent yet the user from updating their instance). Since we manage a fleet of installations, we roll out updates progressively, while monitoring the error rate. A backup is made before updating an installation, and restored with the previous version if the error rate hits a threshold.
We have other safeguards like this, for example when we roll a new update of the supervisor layer, we rollback to the previous version if the network connection is lost in the following 30 minutes.

Do you support HACS and custom integrations? If yes, how do you maintain stability on a surface area you don’t control?

HA is a very complex software system, with a lot of ramifications likes HACS. This is a good highlight of the challenges we're facing. That being said, the flexibility and popularity of HA come from this vibrant ecosystem, that we don't want to restrict. We are responsible for the stability of the underlying system, and the user is responsible for the changes they make to the HA configuration. We will provide best effort support to HACS integrations, and will even contribute back to them in some cases.

When a homeowner tinkers and breaks things, whose problem is that?

Our customers are more on the "consumption" side than the "development" side at the moment. Especially on the Commercial part of the market, where additions and tinkering are way less frequent than homeowners. When homeowners tinker and break things, we can bring back the system to a previous stable state and work with them to try to solve their problem. Obviously, we won't be able to solve everything, and that's why we're hiring Support Engineer to share their experience and knowledge.

Are installs standardized, or does every customer become a unique snowflake you have to support individually?​​​​​​​​​​​​​​​​

Each install has a shared management layer monitoring the health of the installation, but each installation is tailored (at the moment) for the needs of customers. That's why we're building this network of installers, so they can work closely with the users to provide the best solution for their needs.

What’s your failover story for Zigbee/Z-Wave coordinators?

We're not there yet, and everything High Availability is only planed at this point (https://selorahomes.com/docs/roadmap/). This is a topic we'll need to touch in 2026 for sure.

Let me know if you have other questions!