What we've built, how integrations work, and how we handle evidence and credentials.
A property intelligence platform for the Minneapolis–Saint Paul metro, and a two-sided marketplace built on top of it.
The data layer, the property record, the marketplace rails and the short-term-rental operations suite are working today. Public launch follows supply.
Locks and thermostats reach the world through a single adapter, so adding a manufacturer is an adapter, never a rewrite. We don't build one-off SDK integrations per brand.
Every device action runs in a recorded mode first: the call is written down and sent nowhere. Going live takes an explicit switch, provider credentials, and the owner's per-unit consent.
Access codes and secrets are encrypted at rest, never logged, never placed in a message body, and every read of a value is recorded against the person who asked for it.
County-attested, permit-verified, decoded from a data plate, or owner-confirmed — every fact is labeled with which it is, and they're never silently merged into one confident number.
Anything the system decides on a homeowner's behalf is logged with its inputs and the version of the rule that produced it, so it can be explained after the fact rather than defended.
The intelligence behind all of this — the measurement instruments, the season models, the AI-fronted ticket engine, and the informed marketplace — is shown, not asserted: real renders, real benchmarks, and the boundaries stated.