What is live now, and what is coming.
We would rather you know where this is going than discover it later. Here is the honest state of the system and the order we are building in.
Live across three states.
NY · NJ · FL — 22.0M properties, 21.4M with a documented owner, a source on every field
NY · FL — 961K properties traced through a company to a person, each with a Rune ID, our permanent record id
Plain-English questions answered from the record, and actions that run the screens — on models on our own hardware
A deal package’s claims checked against the record: supported, contradicted, or honestly unanswerable
Residential, multifamily, industrial and commercial presets across the screener, map and property pages
Filter 22.0M properties on recorded conditions; saved screens feed the Watchtower digest
Cross-entity rollup to the person; recorded debt with a timeline and payment schedules where the terms support them
48 authored plays across 5 clusters, two modes
A task-grouped guide, plain-English definitions, and a dated changelog, built into the product
What we are working on next.
New Jersey property and owner records are live, each one backed by its filing. Extending the control graph across the state brings it to New York and Florida parity.
A labelled evaluation set, with published precision and recall on the ownership chain: how often we are right, measured and made public. This converts coverage figures into proven accuracy.
Adjacency-based assemblage, abatement expiry dates and flood-zone exposure become live gates, widening how much of the play library evaluates automatically.
The engine is state-agnostic — adding a state is a data problem, not a rebuild. Expansion order is driven by where customers are waiting.
The same machine works on any messy public-records domain. Property is first.
Expansion order is set by customers, not by a plan written in a vacuum. If your market or your record type is not on this list, tell us and it goes into the calculation.
Want it sooner?
Design partners set the order.