PURE — Tech Report
The complete technical inventory of the PURE platform, counted at the moment you loaded this page. Nothing here is a published constant or a figure someone typed: every number below is a live read against the running database, and the two places an estimate is used say so in the line beside them. A technical review is exactly the situation where last month’s number is worse than no number.
reading…
The story, in plain language
PURE is one platform where a brokerage otherwise runs a stack of subscriptions. Listings and MLS data, CRM and lead routing, transactions and offers, meetings with recording and AI summaries, email and SMS, document handling, and an AI front desk that answers the phone — built as one system on one database, so every part sees the same live record instead of a copy synced from somewhere else.
What it runs on. A static web front served from a CDN — there is no application server to patch or scale — over a managed Postgres database. Every read and write goes through gated database functions; the browser holds no privileged credentials. Voice and video ride LiveKit; email rides a sending domain with SPF, DKIM and DMARC. Right now that one database holds … tables and roughly … rows, serving … live surfaces across two application shells.
The platform maintains itself in the open. … scheduled jobs keep it healthy and every run is recorded; … registered AI skills give Poppy, the front desk, its hands; … published standards each name the guard that keeps them true. And this report practices what it preaches: nothing on this page is a typed number — every figure, including the ones in this paragraph, was counted against the running database the moment you loaded it.
The sections below are the evidence for each claim, in the order a technical review asks for them: architecture, security, data protection, the data estate, every surface, connectors, AI, automation, identity, governance — and the competitive position at the end.
At a glance
Architecture — what it runs on
Technology stack — layer by layer
Security posture
Security protocols — and where each one applies
Data protection — the PII scale, applied
Data estate
Surfaces and the two app shells
Every surface, and who uses it
Connectors, APIs and the MCP server
External tools and services
Poppy — skills, and the second brain
Automation
Cron activity — day, week, month
Property ingestion — volume and images
Open-house ingestion — volume and calendar
Legal forms — library, brain and field mapping
MLS roster — members and offices
Where the data actually sits
The hat ladder — every hat by level
Identity — one login, many hats
Governance — how any of this stays true
Competitive position
The claim PURE makes is consolidation. Competitors sell one slice each — a showing tool, a transaction room, a lead platform — and a brokerage assembles the rest by subscription. PURE's position is the whole stack on one live database, with an AI front desk none of the point tools carry. The two documents below make that case in full; they are part of this package and open in this same site.
| Document | What it covers |
|---|---|
| Competitive Report — Rayse, Shilo & PropStream vs PURE | Full feature list of each competitor, a cross-referenced feature matrix against PURE, a live competitor radar, and recommendations. |
| Competitive Analysis & Market Positioning | The whole real-estate software landscape mapped against PURE: why consolidation wins, the NTREIS / MetroTex / NAR context, what each party saves and makes, gaps to close, and the roadmap. |
For a printed or PDF copy of this package, print this page and each linked document — the print styles strip the chrome.