PropEasy assembles a property's documented history — the permits pulled on it, the systems installed in it, the conditions inspected in it — and puts it to work for the people responsible for the building.
Pick the one that describes you — each has its own page, because they want genuinely different things from the same data.
Read your property's documented history, know how old your systems really are, and see the lawn and driveway on the season's clock.
Homeowners →Run turnovers, dispatch to your own crews first, and keep per-unit records across a portfolio — including short-term rentals.
Rentals & property managers →Work from verified owners, in a sealed round, with no fee for a lead that never replies.
Trades →Know what the inspection will surface before the contingency clock starts, and price it on day zero instead of conceding on day eight.
Real estate →What your landlord can see about your unit, what they cannot, and a record of what you reported with a date on it.
Renters →Your product has actuation and telemetry. We are the building layer underneath it — era, systems, condition and history.
Home technology →Roof age, mechanical age and dated storm exposure at parcel grain — evidence rather than an estimate.
Insurance →What PropEasy is, what's built, how integrations work, and who to talk to.
Partners & company →A building accumulates a documented history — permits, sales, inspections, the equipment installed in it. That history exists in public records, scattered across counties and decades, and almost nobody responsible for a property ever gets to read it.
Scanned archives that were never machine-readable — index cards, permit files, certificates of occupancy — turned into records and placed on the specific parcels they describe. In Minneapolis alone that's most of a million documents that previously belonged to no address at all.
Millions of digitized permits, classified by trade and tied to the firm that pulled them, joined to that archive on the same parcel — plus recorded sales, condition reports and equipment across all seven metro counties.
Depth is uneven and we chase it city by city — some municipalities run to the 1980s, some are mid-ingestion now. We go as far as each record allows and state where that ends, rather than presenting one flat surface.
Not a forecast widget. Weather is an input the platform runs decisions on — and the unit of the answer is your parcel, not your county.
A hail report says a storm crossed the area. That isn't the same question as whether stones fell on your address. We localize each storm to individual parcels and keep the result as a permanent history.
Public storm reports are scanned continuously to answer "did anything happen at all?" Only on days something did does the per-parcel work run. It's what makes property-level resolution affordable.
Daily temperature, rainfall and snowfall back to 2000, per grid cell. The seasonal models are tested against a quarter-century of real Minnesota weather rather than tuned to last season and hoped for.
These are constraints in the architecture, not aspirations in a values page. Each one cost something to build that way.
Every fact carries where it came from — county-attested, permit-verified, decoded from a data plate, or told to us by the owner. Different kinds of fact are never quietly merged into one confident number.
The system abstains rather than guessing, and says which question it couldn't answer. Absence of a record is reported as absence of a record — never as evidence that nothing happened.
The engine that makes recommendations has no access to commercial relationships. It isn't a policy we promise to keep; it's an input the code doesn't have.
Every real-world action — a door code, a thermostat, a job sent outside your own crew — stays off until switched on for a specific property. Until then the intended action is written down where you can read it.
It's a neutral account of the building, not a sales surface, and it's meant to transfer with the home when it changes hands.
When the system concludes something on your behalf, the inputs and the version of the rule are recorded — so it can be reconstructed later rather than defended from memory.