Owning more than one home usually means managing more than one set of vendors, credentials, and blind spots. HINQ organizes every property you own into a single account, so you're never logging into five different things to check on five different homes.
Every property's platform interface organized under a single login.
Each home runs its own dedicated SHINQ platform interface, on site.
Check on every property from one screen, without juggling logins.
One HINQ profile does not mean a single interface remotely operates multiple properties. Each property requires its own dedicated local SHINQ platform interface, physically present on that property. What one profile does is organize every property's individual interface into one account, giving you unified remote management and preview across all of them, from wherever you are.
Every property under your account runs its own SHINQ platform interface, physically present on site. HINQ does not remotely operate a home from a device located somewhere else.
Your HINQ profile links every property's local interface into a single account, so you view and manage them together instead of separately.
An anomaly flagged at one property is weighted into monitoring at your other properties, because HINQ recognizes they belong to the same household.
Check network health, security status, and maintenance schedules for every property from one place, without switching logins.
Household staff and vendor access credentials managed centrally, revocable across every property at once.
HINQ adjusts monitoring sensitivity for properties occupied seasonally, distinguishing "unoccupied and normal" from "unoccupied and anomalous."
A member with a primary residence in Highland Park and a second property in Lake Travis receives an alert when unusual overnight network activity occurs at the Lake Travis property while the family is at the primary residence. The Lake Travis platform interface, running locally on that property, is what detected the anomaly. Because both properties' interfaces are organized under one HINQ account, the system already knew that property was expected to be unoccupied, and treated new device connections as worth flagging rather than routine. One profile made that cross-property context possible. The detection itself still happened locally, at the property, the way it has to.
Multi-Property Management is platform-native, organizing every property's data across every service pairing into one unified view.
It does not extend monitoring to a property without deployed hardware. One HINQ profile is an organizing and remote-preview layer, not a substitute for a local SHINQ platform interface at each property, every home still needs its own.
Properties outside current Seiits service markets cannot be added to a HINQ profile until that market is active. See Locations for current and upcoming coverage.