For property managers

Smart home operations for property managers

At ten properties the smart-home layer is a chore. At a hundred it is a job nobody has time for — and the tooling usually assumes one owner, one home, one person holding every credential.

Homatic is built for the other case: several buildings, a team with different responsibilities, and owners who should not all see each other’s data.

Access is per capability, not per person

Most systems offer read or write. That does not describe a management company, where one person handles bookings, another handles guest messaging, and the owner keeps control of their own devices.

Homatic splits access into six transferable functions — bookings, guest messaging, access codes, guidebook, expenses, automations — each of which a property manager can hold exclusively, with the owner stepping back from that function while it is assigned. Two further grants, editing the property and controlling devices, the owner always keeps.

Three things are never delegable, because they are what delegation would otherwise let someone grant themselves: adding devices, deleting the property, and managing the team.

Buildings, not a list of sixty names

Units belong to a building — or a complex, portfolio or region; the label is yours. Buildings carry their own address, because two “Building A”s in different cities are otherwise the same row twice.

Name collisions are prevented in the database rather than by a check, so two people creating “Harbor View” at the same moment cannot end up with a portfolio listing both “Harbor View” and “harbor view” and splitting one building’s units between them.

Deleting a building releases its units; it never deletes them.

Grouping also works across ownership. A manager can group units owned by two different people in the same physical building, because visibility is decided by what you can already see, not by who holds the deed.

Portfolio views that stay honest

The dashboard scopes to a building on the server, so its totals come from one definition of revenue rather than a second one computed in the browser. Analytics is per-property, so its building filter narrows the picker and moves your selection when the current unit falls outside the chosen building — otherwise the picker lists one building while every panel below describes a unit from another.

Asking for a building you cannot see is refused rather than answered with an empty portfolio, because “this building is empty” is a different statement and an untrue one.

Operational detail that matters at scale

• Device command limits are enforced per user, per property and per device — the third exists because some vendor quotas are shared across every customer of that vendor, so one person hammering a thermostat can degrade someone else’s.
• Cross-request anomaly detection watches shapes a single authorisation check cannot see: bulk device control, one account touching an unusual number of properties, repeated authorisation denials, off-hours unlocks in the property’s local time. It alerts; it never refuses.
• Every physical action is audited — locks and unlocks, whether a person or an automation did it, access codes created or revealed, cameras viewed.
• Background jobs skip suspended accounts, so an account you have cut off is not monitored, not acted for, and not reported on.

Running a pilot

Start with one building. Connect the properties, let the device summary fill in, and write two or three rules that map to work someone currently does by hand — the checkout setback, the door-left-open alert, the per-guest code.

The free trial runs 30 days with Starter features and no card. That is enough to see whether the automations hold up across real turnovers, which is the only test that matters.

For a portfolio beyond twenty properties, or if you need SSO, custom onboarding or a security review, get in touch at contact@homatic.ai — that scale is an Enterprise conversation rather than a signup.