I can share several links but, unfortunately, none will point directly to a recent web-site because the product was discontinued many years ago.
In May 2000, Premise Systems (about a half-dozen former Microsoft employees and professional systems integrators) announced the release of a beta version (Internet archive link) of Premise Home Control. Long story short, over the next 6 years there were two releases of the product and the company was sold to LANtronix and then to Motorola who ultimately discontinued it. The final version was released to the public for free (but remained closed-source). Despite only two releases, its architectural design remains impressive two decades later (even when compared to existing commercial and open-source solutions).
Internet Archive link dating back to 2003.
I created a summary of Premise and it’s posted on Cocoontech. It contains several screenshots of Premise Builder which is what is used to manage the entire product. I was actively involved in the user-community for many years.
The software has been available from Cocoontech but I recently noticed it says the download is broken. If that’s true and someone really, really wants to explore this forgotten gem, then I can point them to a different source. Please be aware that it runs exclusively on Windows.
If you’re interested, the following points contain links to Premise-related posts I have made in the past (in Home Assistant’s community forum):
Everything is object-oriented in Premise. You can easily create new classes of devices by inheriting/extending existing classes (i.e. imagine you were able to define custom domains in Home Assistant).
Premise’s objects (a.k.a entities) can be organized hierarchically (i.e. nested areas) and each one has a mandatory type (sort of like a super-charged version of device_class).
Premise’s sysevent object can tell you more about the trigger’s source than Home Assistant’s trigger object.
Premise supports the concept of a momentary boolean, where it can only maintain
true for a brief moment to serve as a pulse.
Its drivers (integrations) can be installed/uninstalled/upgraded independently of the core Premise software and without restarting it or explicitly reloading anything. Here’s a description of the UPB driver whose C++ source-code (one of the rare exceptions for this closed-source product) was offered as a reference for the creation of Home Assistant’s excellent UPB driver.
Its scripting language is an enhanced version of VBScript. It isn’t just for creating automations but can also be used to create the equivalent of integrations. This is a tremendous advantage because it permits immediate, interactive development (within Premise’s UI) as opposed to the compile/install/test cycle for C++ driver development. Over the years I created several in VBScript including one for Text-To-Speech and just one in C++ (pointers to lists of pointers, oh my!).
FWIW, I discovered Premise in mid 2007 and continue to use it today. It has a few integrations that either don’t exist in Home Assistant or I simply prefer the Premise version. Three years ago, I added MQTT functionality to Premise (akin to a bi-directional version of Home Assistant’s MQTT Statestream integration) and it provides seamless interoperability with Node-Red and Home Assistant.