Why Edge Remains Controlled

Edge is live with selected users, but wider access is being held back while the product is refined against real buildings.

The goal is not simply to release another dashboard, but to build a platform that can be trusted in operational settings.

That is intentional. A building platform has to earn trust in real buildings, not just in demos. It needs to handle imperfect data, inconsistent naming, unusual plant behaviour, network issues, changing project teams and the realities of maintenance after handover.

We want Edge to be more than a good product. We want it to become a leading operational layer for commissioning, maintenance and building performance. That takes time and close validation.

Beta is a quality decision

Keeping Edge controlled lets us work with selected projects properly. We can refine how gateways are installed, how points are mapped, how assets are structured, how issues are surfaced, and how teams actually use the platform day to day.

This is not about holding back for the sake of it. It is about making sure the product is useful in the real environment it is meant to serve.

What wider release needs

Wider access will come when we are confident the product can support more projects without losing the engineering standard behind it. That means clearer onboarding, stronger project setup, better documentation, and a product experience that feels dependable.

Until then, we will keep building with real sites, real users and a high bar.