Build on Building OS
The platform is a module host. The same SDK, contracts and federation our own teams use are the ones you get.
Modules are independently deployed
A module is its own frontend, its own backend and its own release train, federated into the shell at runtime. Shipping one does not rebuild the others, and a building only loads what it has licensed.
The building graph is the contract
Buildings, storeys, spaces, equipment and their relationships live in one graph, however it was sourced — IFC or CAD, a CSV, an existing CAFM or BMS, or drawn by hand. Modules read and extend it rather than each keeping a private copy of the floor plan.
Events, not polling
State changes are published as events, so a module can react to a lease activating or an occupancy threshold being crossed without knowing which module produced it.
Every module speaks MCP
Modules publish Model Context Protocol tools — 83 across the platform today — so an AI copilot can act on a building through the same typed interface a developer uses.
Build on it
Want to build a module?
Tell us what it should do and we will get you a sandbox tenant to build it against.