Mimir
01How it works

How 160M+ records become one answer you can check.

Two different things happen inside Mimir, and most vendors blur them. Identity is settled by fixed rules. Who controls whom is inferred, scored, and shown with its evidence. Keeping those separate is the whole design.

02The distinction

Identity follows fixed rules. Control is a judgment.

One record per building and one per person, made by fixed rules. The machine is the Rune Engine; the id it gives each building and person is a Rune ID. Same inputs, same answer, every time, with no machine learning involved. That is what lets an answer be re-checked instead of trusted.

Who controls whom is different: no filing states it. It has to be read from behaviour, so every link carries the evidence behind it and a confidence value — on the screen, not buried in a single score.

441 Vanderpool Street, Brooklyn, NY 11215synthetic
Ownership chain
Block 1042 · Lot 17 · 12 units · built 1928
  1. Owner of record
    VANDERPOOL HOLDINGS LLC
    Deed recorded 2019-04-11nyc_acris
  2. Controlled by
    HARROW STREET CAPITAL LLC
    Shared registered agent + mailing addressny_dos_corps 0.82
  3. Ultimate controller
    A. Reyes
    DOS process address across 6 entitiesny_dos_corps 0.74
The receipt
ACRIS 2019041100428001
Source
nyc_acris
Document type
DEED
Recorded
2019-04-11
Grantor
ESTATE OF M. OKONKWO
Grantee
VANDERPOOL HOLDINGS LLC
Consideration
$2,150,000

Every value on the left opens a record like this. Nothing is asserted without one.

03The pipeline

Six layers, each rebuildable from scratch.

01HarvestRaw public records

Government dumps pulled whole and never filtered at collection — county recorders, tax rolls, corporate registries, code enforcement, parcel geometry. Filtering at intake destroys answers you cannot get back.

02StandardiseSame form, every source

Every parcel number, address and name is cleaned into one standard form. The same input always comes out the same way.

03MatchThe Rune Engine

Overlapping identifiers collapse to one record per real building and one per real person, through a fixed ladder of match rules we call the Rune Engine. No machine learning. Nothing drifts between runs.

04AssembleThe working record

Matched records become the tables you search: properties, owners, sales, mortgages, liens, distress. Every field keeps a pointer to the source row that produced it.

05LinkWho controls what

Filing behaviour connects properties to companies, and companies to people. This layer is inference, so every link carries its evidence and a confidence value.

06ServeThe terminal

Search, dossiers, portfolios, stacks and alerts all read that one clean record. Any value on screen opens back to the government document underneath it.

The whole chain runs self-hosted on commodity hardware and can be rebuilt from the raw dumps. Nothing in the answer depends on a vendor feed we cannot reproduce.

See your market.

Twenty minutes on the live terminal.

See your market