Infrastructure
Buildings, floors, spaces, and the ownership hierarchy that structures the portfolio.
IFC 4.x · BOMA 2017 · OmniClass
Your data foundation
One record of the building.
Every screen reads it.
The Digital Grid is one typed record of every building, space, company, person, and lease, with its history. Six domains, each carrying the standards the industry already uses. Open specification. Every product on this site reads and writes it.
Three pillars
The Grid. History. Connectors & APIs.
Everything the platform does is one of these three, and every product on the site is built on them.
The Grid
Buildings, spaces, companies, people, leases, and systems as one related model. One object, one definition, everywhere.
History
Observations and events, append-only, with both the time it happened and the time you learned it. The record keeps what changed and why.
Connectors & APIs
One interface behind every surface. Connect the systems you already run, so their data lands on the record instead of beside it.
How data moves
From your systems to an answer, in four steps.
-
Flow · 01
Your systems write to the record.
Connectors carry leases, people, access events, and work orders from the systems you already run onto the Grid. Nothing is copied beside the record; it lands on it.
-
Flow · 02
Every product reads the same object.
A building is one object with one definition, whether Leases, Service requests, or the tenant app is looking at it. Change it once and every screen agrees.
-
Flow · 03
History keeps what changed and why.
Observations and events, append-only, with both the time it happened and the time you learned it. Ask what the record said last quarter and get last quarter's answer.
-
Flow · 04
Anything can ask, under your permissions.
REX, your reports, and soon the AI assistant your analysts already use via MCP. Every answer traces to the record it came from and respects who is asking.
01 / 04
Specification
Open · published
Domains
Six, standards-aligned
History
Append-only · bitemporal
AI assistants
via MCP
Beta
The Digital Grid specification is published in the open. Your engineers can read the schema, the event types, and the API contract before they sign anything. HqO develops it and the platform runs on it. The developer portal, documentation, and keys live at digitalgrid.ai.
The Grid
Six domains. The standards your industry already uses.
The Grid is one typed schema across six domains. Each carries the standards its work is already reported in, so a lease means the same thing to leasing, accounting, and REX. When one object changes, everything connected to it updates.
The products that read and write itLeasing
Every lease from LOI through execution: obligations, critical dates, CAM, and renewal.
ASC 842 · IFRS 16 · RICS
People
Every occupier, prospect, and stakeholder, with roles and permissions on the record.
Finance
NOI, CAM reconciliation, budget actuals, distributions, and investor reporting from one source.
NCREIF · ARGUS Enterprise
Operations
Work orders, vendors, preventive maintenance, energy, and compliance against the same asset objects.
ENERGY STAR · GRESB · LEED
Experience
Programming, amenity access, and engagement connected to tenant health and retention.
Leesman
History
Observations and events. Bitemporal. Append-only.
The Grid keeps what happened to every object and when it was known. A lease amendment, a health score drop, an SLA breach: each is an event on the record, never overwritten. Ask what was true on a date, and what you knew on that date, and get two honest answers.
History is the Grid's. Memory is REX's.Observations
Facts about an object at a point in time, with the source that reported them.
Events
Things that happened, in order, with what they changed. Every product and connector writes them.
Bitemporal and append-only
Two clocks on every fact: when it was true, and when the record learned it. Nothing is deleted; corrections are new entries.
Connectors, APIs, MCP
One interface behind every surface.
The Grid does not replace your systems of record. It gives them one model. Whatever reads the record, from a tenant's phone to an analyst's assistant, reads the same interface under the same permissions.
The surfaces that read itConnectors
Property management, lease administration, accounting, CRM, and access control write to the same schema and read from it. No rip and replace.
APIs
One open API behind every surface. REX, the HqO app, the tenant portal, and your own tools consume the same endpoints.
MCP
A Model Context Protocol server exposes the record to the AI assistants your team already uses, under the same permissions.
Sovereignty
Where it resides, what it trains, who can query, what leaves.
Four questions every owner should be able to answer about their data. The Grid is built so that each has a plain answer, and the answer is enforced by the record, not by a policy document.
The sovereignty architectureWhere it resides
Hosted on AWS in US East (N. Virginia) or EU Central (Frankfurt). Encrypted with TLS 1.2+ in transit and AES-256 at rest.
What it trains
REX's Memory is scoped to your organization. The record is yours; the model is swappable. The Trust page carries the exact wording.
Who can query
Every read, by a person, a connector, or an agent, runs under the roles and permissions on the record.
What leaves
Connectors and API calls are the only doors out, and History records what was read and written through them.
Plainly
What the Grid is, and what it is not.
- It is the record.
- The one place a building, a tenant, and a lease are defined. Products read and write it; they do not keep their own copy.
- It is not a data lake.
- Nothing is dumped in to be sorted later. Every object is typed, related, and carries the standard the industry already uses for it.
- It is yours.
- Scoped to your organization, in your region. Connectors are the only thing that crosses the boundary, and only where you connect them.
- It is not a black box.
- The specification is open. Every answer REX gives traces to the object and the event it came from.
400M+
Square feet powered
1,500+
Properties
32
Countries
185+
Customers
Trusted by the world's leading owners and operators
Build on the record.
The specification is open. Connectors, APIs, and MCP are documented for your team and your vendors.