The platform

Every customer. Every building. One model.

Ingest from anything you already run, standardize it into one model — profiles, metrics and definitions included — and benchmark any asset against its peers.

Ingests
29 supported systems — and anything else with an export
Standardizes
150+ metrics, each with a single definition
Resolves
One profile per person, rolled up to the organization
Benchmarks
Blinded local and national peer sets per metric
Capability · 01

Integrate with anything

If the data exists, we can get it. Documented APIs, cloud warehouses, vendor connectors, direct database reads, scheduled imports — and the spreadsheet someone emails on the first of the month.

No system is too old and no export is too crude to be useful. That's deliberate: the asset with the worst tech stack is usually the one you most need to see.

See all integrations →
REST & GraphQL APIs
Cloud services
Vendor connectors
Direct database reads
Scheduled imports
Flat files · CSV, XLSX
Webhooks & streams
Landed and normalized
29 systems, one pipeline
Access control · Room booking · WiFi presence · Parking · Events & RSVPs · Ticketing · PoS spend · CRM · Financials
New sources land into the same model — no schema negotiation, no re-baselining what you already measure.
Capability · 02

A standardized data model

Every source system names things its own way. A badge event, a room check-in and a WiFi session are three schemas describing the same fact, and no two vendors agree on the field, the unit, or the timestamp.

REKalibrate maps all of it into one model with 150+ standardized metrics, each with a single definition. That's what makes a number comparable across buildings, tenants and time — and what lets a new system come online without re-litigating what "engaged" means.

Unified Profiles are part of that model, not a separate product. Identity resolution runs deterministic keys first and probabilistic signals second, collapsing every fragment of a person's day into one profile that rolls up to the organization paying the rent — and it re-runs each time new data lands.

Source fields, as they arrive
badge_in_tsAccess control
checkinDateTimeRoom booking
assoc_start_epochWiFi controller
entry_dt_localParking PARCS
One standardized metric
On-site presence
Person-resolved · UTC-normalized · deduplicated across sources · one definition in every building
Inside the model · Unified Profiles
AC
A. Chen
DonCo International · Floor 14
Systems
6 / 7
Days on site
3.4 /wk
Engagement
Highly engaged
150+ metrics defined29 systems mapped
Capability · 03

Benchmarking

Every number gets a peer set. 150+ standardized metrics across operators mean any asset can be measured against blinded local and national peers — with the subject always held out of its own benchmark.

Reach · share of population observed
illustrative
This asset22%
Local peer set14%
National set11%
Avg util.
26%
Peak util.
40%
Headroom
High
Capability · 04

Extensible by design

Every new source you connect makes the existing ones worth more. A system that arrives today lands in the same model as everything already there — no schema negotiation, no re-baselining, no separate report.

The compounding is the point. Each feed adds a dimension the others can be read against, so questions that were unanswerable last quarter become routine the moment one more system comes online.

See what connects →
Connected today
Access control · on-site presence
Room booking · reservations
WiFi · attributed sessions
Add one source · Parking (PARCS)
Three new questions become answerable
Who drives in but never books a room · Which tenants pay for stalls they don't use · Whether parking demand predicts next quarter's attendance
Nothing re-modeledNothing re-baselined
Capability · 05

Flexible delivery

Insights arrive where the work already happens. The app for your teams, the API for your stack, an MCP server so AI assistants can query the portfolio in plain language, and custom reports for the conversations that need a document rather than a dashboard.

Every door opens onto the same model, so the number in a board pack is the number in the app is the number your warehouse returns. No reconciliation, no “which version is right”.

One model · four front doors
App
Governed dashboards and drill-downs for asset, ops and leasing teams.
API
Every metric and profile available to your warehouse, BI tools and internal apps.
MCP server
Point an AI assistant at your portfolio and ask in plain language — role-gated, answered from the same definitions.
Custom reports
Board-ready output on your schedule, built from the model rather than assembled by hand.
What that buys you

Two buildings, different stacks, one honest comparison.

A 1980s tower on legacy access control and a new build on a modern tenant platform produce completely different raw data. Normalized into the same model, they produce the same metrics — so you can compare them apples to apples, and roll them into one portfolio number that means something.

Which means the intelligence arrives without a capital project. No rip-and-replace, no forced standardization on one vendor, no waiting for the laggard asset to be upgraded before it can be measured.

Building A
Legacy badge system
Spreadsheet room bookings
No tenant app
Building B
Modern access platform
Integrated booking
Tenant app + WiFi portal
Same metrics, same definitions
Engagement
A 22% · B 14%
Depth
A 26% · B 54%
Peak util.
A 40% · B 81%
illustrative · no new systems required

One foundation. Every use case reads from it.

Start with the product that answers your most pressing question, and expand when the next one arrives — the numbers agree either way.