Station backups tell you that something changed. They almost never tell you what. A file is different, a date moved — but did someone adjust a setpoint, rewire control logic, disable an alarm, or add a user? On systems that run buildings, that distinction matters, and today it is usually reconstructed from memory.
Status: product concept, in active development. This is something we are building, not something you can buy today. We publish our roadmap because the engineering thinking behind it is the useful part — and because we would rather show you the design than imply a finished product.
Designed Capabilities
- Scheduled station backup capture — the baseline, taken reliably rather than when someone remembers.
- Normalized station representation — a form that can actually be compared.
- Semantic component and link diff — what changed in the logic, not which bytes moved.
- User, module and permission change detection — security-relevant changes called out separately.
- Approval and release workflow — changes to production get reviewed, like any other system.
- Release notes and evidence package — a record for the client and the auditor.
- Rollback bundle generation — a way back that was prepared, not improvised.
- Unauthorized-change alerts and retention policies — know when something changed that shouldn’t have.
Building Automation Deserves Software Discipline
Every other part of the software industry settled this decades ago: changes are versioned, reviewed, released and reversible. Station configuration — which controls physical plant — is often still managed by copying files to a folder. Bringing ordinary engineering discipline to it is overdue, and the semantic diff is what makes it practical rather than theatrical.
Tell us if this matches a problem you have — early input shapes what we build first, and we will give you an honest view of where it stands.