Waitlist open

The AI-native platform for calmer, more profitable vacation rentals

One calendar, one inbox, one place to price and publish to every channel. Leah, the agent inside it, works the same data you do and asks before she writes.

A full channel manager · two-way sync on every channel

  • Airbnb
  • Vrbo
  • Booking.com
  • Expedia
  • Google Vacation Rentals
  • Agoda
  • Trip.com
The platform

A full property management system, not a bolt-on.

  1. 01

    One calendar, every property

    Every property, room type, and channel sits on a single availability grid. When a night books anywhere, Supahost blocks it everywhere, so you never take two bookings for the same night.

    Multi-property grid, live availability

  2. 02

    Rates and restrictions in one edit

    Set a nightly rate, a minimum stay, or a stop-sell across a date range and every rate plan you pick. It publishes to the channels those plans belong to.

    Bulk edits, min stays, stop-sells

  3. 03

    Every guest, one inbox

    Messages from every channel land in one thread per stay. Reply once from Supahost and the guest gets it where they booked, with delivery confirmed or flagged so you can retry.

    One thread per stay, delivery receipts

  4. 04

    Turnovers that run themselves

    Rules fire on the events that matter: a reservation is created, an arrival is coming, a checkout finishes, a task runs late. Cleaning and guest work lands on the right person with a due date.

    Four triggers, assignees, priorities

  5. 05

    Bookings you can actually work with

    Every channel resolves into one canonical reservation list: arrivals, in-house, pending, booked value. Filter it, work it, export the view. Guest and owner profiles build themselves from it.

    Filters, stats, CSV export

  6. 06

    And Leah, inside all of it

    Ask her anything about your properties and she inspects the same data you can see, then proposes the change. Every write waits for your approval before it touches a channel.

    Reads freely, writes on approval

This is Leah.

She is the operations agent living inside Supahost, working your real properties. Ask in plain words, watch her check, and approve the change before it reaches a channel. Pick a job and she will run it.

LeahThread

Block Driftwood Cottage for a deep clean, Mar 3 to Mar 5.

listProperties · Driftwood CottageinspectAvailability · Driftwood Cottage · Mar 1 to Mar 8

All three nights are open and the closest stay checks out Mar 2, so nothing has to move.

Proposed change · createAvailabilityBlock

Driftwood Cottage · Mar 3 to Mar 5 · Deep clean

Approved by you · queued to 4 channels
inspectChannelUpdate · update 0f31c8 · completedinspectProviderSync · Driftwood Cottage · 4 of 4 verified

Blocked. Every channel read the nights back, so they are gone out there too, not just in here.

Proposed change in your Google Calendar · create event

Ops calendar · Mar 3, 9am · Deep clean, Driftwood Cottage

Approved by you · the crew has it

One more thing while I was in there. Back on Feb 11 you held these nights with the reason “microwave dead, replace before next stay”, and the repair has not had a slot since. The cleaners are already coming. Want me to start the block a day early so the fitter can ride along on the same trip?

Yes, start it Mar 2 · you
updateAvailabilityBlock · Mar 2 to Mar 5 · approvedinspectChannelUpdate · update 0f31d4 · completedinspectProviderSync · Driftwood Cottage · 4 of 4 verified

Moved to Mar 2, reason now reads “deep clean and microwave replacement”. One visit instead of two.

Proposed change in your Google Calendar · move event

Ops calendar · Deep clean, Driftwood Cottage · Mar 3 to Mar 2

Approved by you · the crew has the new day

The crew’s calendar moved with it, so nobody turns up on the wrong day.

  • Google Calendar
  • +24 connected

Ask Leah about your properties

Pick a job and watch it run

  • Google Calendar
6 of 34 tools used here
8 read · 26 approval-gated by default
1 of your accounts, granted by you

  • You set the boundary

    All 26 write tools pause for your approval by default. Only a playbook you explicitly make autonomous can act inside the tools and rules you saved.

  • She cannot reach past you

    Her 34 tools read the same records the dashboard reads, under your own permissions. Beyond that she reaches only the accounts you grant, one at a time.

  • You can check her work

    Every thread keeps the tool trail. What she read, what she changed, and where it landed.

Teach her your playbook. Then give her your stack.

A skill is a playbook you write once and she reads before she acts: how you price a shoulder season, what your turnover standard is, how you answer a late checkout. Without one she is competent. With one she works the way you would have.

  • Auto-invoke

    Runs on its own when its trigger matches. No prompt needed.

  • On request

    Stays quiet until you ask for it by name.

25 accounts Leah can work in once you connect them, across 8 categories. The approval rule follows her into every one.

  • Communication
    • Gmail
    • Outlook
    • Slack
    • WhatsApp
  • Marketing & email
    • Mailchimp
    • Klaviyo
    • Brevo
  • Finance & payments
    • Stripe
    • QuickBooks
    • Xero
    • PayPal
  • Scheduling
    • Google Calendar
    • Calendly
    • Cal.com
  • Productivity
    • Google Sheets
    • Google Drive
    • Notion
    • Airtable
    • Dropbox
  • Forms & contracts
    • Typeform
    • DocuSign
  • CRM & sales
    • HubSpot
    • Pipedrive
  • Developer tools
    • Linear
    • Apify

Be first in line.

We onboard hosts in small groups, so every workspace gets set up right. Add your email. We will reach out when a spot opens.

A year of nights, every channel, one calendar77% booked