How Supahost works
Three ideas explain the whole product: your properties live in a workspace, every channel shares one calendar, and the agent works inside the same guardrails you do.
The workspace
A workspace holds your properties, reservations, guest conversations, and team members. Everything in Supahost is scoped to it. Invite a co-host and they see the same calendar you do — nothing more, nothing less.
One calendar
Each property has a single availability grid. Reservations from every channel land on it, and blocks you create flow back out to every channel. The grid is the source of truth; the channels mirror it.
That is what makes double bookings structurally impossible to miss: two reservations cannot hold the same night on one grid.
The agent layer
The operations agent sits on top of the same data. Ask it to find failed syncs, fix stale rates, or block a night. It inspects first, explains what it found, then proposes a change and waits.
Approvals are the contract: read tools run freely, write tools stop and ask. See Operations agent for the full model.
What Supahost is not
Supahost provides tools only. It is not a property manager, a booking agent, or a party to your reservations. You set the prices, you accept the guests, and you stay the host of record on every channel.