Infrastructure
Buildings, floors, spaces, and the ownership hierarchy that structures your entire portfolio.
IFC 4.x · BOMA 2017 · OmniClass
Digital Grid
One foundation. Every object in your portfolio.
The Digital Grid is the shared intelligence layer that powers everything on hqo.ai — an open scheme HqO developed for modeling the built world. Your buildings, spaces, companies, people, leases, and systems in one typed model, with memory you own.
The Foundation
Three layers. One system.
The Grid models what exists. Memory holds what happened and why. Connectors and APIs keep both in sync with the systems you already run.
The Grid
A unified, typed model of your buildings, spaces, companies, people, leases, and systems. One object, one definition, everywhere.
Memory
Institutional knowledge that remembers what happened, why it happened, and what to do next. It stays when people leave.
Connectors & APIs
Connect the Grid with the systems you already use. One open API behind every surface.
The Grid
Every CRE object. One model.
For decades, CRE data lived across disconnected platforms — each a separate island with no common language. The Grid defines one typed schema across six domains, built on the standards your industry already uses. When one object changes, everything connected to it updates.
Leasing
Every lease object from LOI through execution — obligations, critical dates, CAM, and renewal.
ASC 842 · IFRS 16 · RICS
People
Every occupier, prospect, and stakeholder unified. Tenant health, relationship history — always current.
Finance
NOI, CAM reconciliation, budget actuals, distributions, and investor reporting from the same canonical source.
NCREIF · ARGUS Enterprise
Operations
Work orders, vendors, preventive maintenance, energy, and compliance — running against the same asset objects.
ENERGY STAR · GRESB · LEED
Experience
Tenant programming, amenity access, and engagement data connected to occupier health and retention outcomes.
Leesman
Memory
Institutional knowledge that stays.
The property manager who knows why a tenant is always late on maintenance. The amenity program that flopped — and why. The concession that closed the last deal. Memory captures what happened, why it happened, and what to do next, and makes it available to every person and every agent who needs it.
01
Retain
Every meaningful event becomes a structured fact — a complaint, a program and its outcome, a renewal and the concessions behind it. Not raw text: typed, timestamped facts linked to the building, tenant, lease, and program they belong to.
02
Recall
Ask a question and multiple strategies run in parallel, then fuse — semantic for intent, keyword for exact names, graph traversal for relationships, temporal for time-bounded queries. “What were we dealing with before this tenant last renewed?” returns a real answer.
03
Observe
Memory consolidates. Three HVAC complaints over two years become one observation: a persistent facilities sensitivity, evidence strengthening. Deduplicated, evidence-tracked, and carrying a freshness signal — so you know what is true now versus what used to be.
04
Reflect
When an agent needs a recommendation, it reasons over the full context — retained facts, consolidated observations, and the building's own history — to produce a grounded recommendation, not a retrieval result.
You own it.
Agents will change. Models will ship. Memory lives on the Grid — not inside a model or a vendor's system. Switch agents, add agents, swap providers: the memory stays, and every new tool starts with the full context of everything that came before.
Connectors & APIs
Connect the systems you already use.
The Grid does not replace your systems of record — it gives them a common model. Property management, lease administration, accounting, and access control write to the same schema and read from it. No rip and replace.
Your existing systems
Connectors for the categories you already run — property management, lease administration, accounting, CRM, and access control.
Your documents
Leases, contracts, and reports parsed into structure. Obligations surfaced. Nothing left trapped in a PDF.
One open API
Every surface — REX, your apps, your own tools — consumes the same API. The specification is public on GitHub, open to your engineers from day one.
Why It Matters
The foundation is the strategy.
Disconnected data is liability.
Property management, lease administration, accounting, access control — each system captures part of the picture. None share a common model. Every insight requires reconciliation. That is not a reporting problem. It is an infrastructure problem.
AI without context doesn't compound.
A better search box over disconnected data impresses in demos. It does not build advantage. When data shares one model and one memory, every answer, every workflow, and every decision makes the next one better.
The Grid is what makes REX trustworthy.
REX answers from typed objects, not loose documents. Every recommendation traces back to the lease, the ledger, and the history behind it. That is the difference between a plausible answer and one you can act on.