01
The record is the product
Dashboards are downstream of whether the underlying account of the house is true. We spend our effort on making the record accurate, complete and durable; everything else follows from that.
About
Built for the people who get the call.
Tidewater OS began with a familiar situation: a substantial house, a competent team, and no single place where the truth about the building lived. The manuals were in a drawer. The service history was in an inbox. The one person who knew which valve isolated the guest wing was on holiday.
We built the thing that should have existed — an operating record for the property itself, detailed enough for the field and legible enough for the principal.
What we believe
Five commitments the software keeps.
02
AI proposes, people approve
Extraction and analysis are genuinely useful for reading a stack of paperwork. They are not a substitute for judgement. Nothing becomes authoritative in Tidewater OS without a person accepting it.
03
History is never rewritten
Service events and audit entries are added to, not edited. A record you cannot trust to be unchanged is not a record at all.
04
Say what is missing
A completeness score, a stated assumption, an unverified flag. The platform is candid about the limits of what it knows rather than presenting confident numbers built on gaps.
05
The house outlives the staff
Managers change, owners change, vendors change. What should survive all of it is the account of the property — which is why continuity and handoff are first-class rather than an export button.
Access
We onboard deliberately.
Each organization is brought on with help loading its first property, because a record that starts empty tends to stay that way. That is why access is by invitation rather than signup.