A building your software can reason about
Most building software stores documents about a building: drawings, spreadsheets, PDFs. Building OS stores the building itself — one live model of its storeys, spaces and equipment that every module, and your own software, can read and change.
One graph per building
Storeys, spaces, equipment and the relationships between them live in a single model. A work order, a lease and a route all refer to the same room, because there is only one room.
A BIM model is optional
The graph can be built from an IFC or CAD model, a CSV of spaces and equipment, an existing CAFM or BMS through its API, or a RealEstateCore export. Where a building has none of those — and plenty do not — the plan is drawn directly in the map editor. Buildings that were never modelled are the normal case, not the exception.
Versioned like code
The building has a history. A re-import is a revision you can diff, not an overwrite, so you can see what a floor looked like before the fit-out and what changed with it.
Modules, not a monolith
Capability arrives as modules on that graph — 32 of them — each deployed on its own schedule. A building loads what it has licensed and nothing else.
The building talks to the people in it
The same graph drives what visitors see: kiosks, multi-floor routing to a shop or a meeting room, step-free alternatives, and a tenant directory that updates when a lease does. It works from any phone through a QR code, with nothing to install. Most of the platform improves a building for the people who run it; this is the part the people who visit it actually notice.
Runs where the data has to stay
The whole platform can be deployed inside your own perimeter. On-premise is the same software rather than a cut-down edition, because for a lot of buildings sovereignty is not negotiable.
Sensing without cameras
Occupancy comes from Wi-Fi channel state — the distortion a body makes in an ordinary Wi-Fi signal — reported per zone as occupied or still. Nothing is filmed, and nobody has to carry a device or install an app.
Built for copilots, not just dashboards
Every module publishes typed tools over the Model Context Protocol — 83 across the platform — so an assistant can act on the building through the same interface a developer uses.
What is in it
32 modules across 5 areas. Licence the ones a building needs.
1 modules
AI
Models that read the building's history and act on it.
3 modules
Analytics
What the building is telling you, and what to do about it.
6 modules
Engagement
Everything the people inside the building actually touch.
5 modules
Infrastructure
Sensors, events, identity and the audit trail underneath it all.
17 modules
Operations
Running the building day to day — maintenance, space, equipment, money.
Start where it hurts
Bring one building. Then the portfolio.
A working session on your own floor plans and asset register — not a slide deck.