Seven cabins and a pool
is not seven listings.
Your software thinks it is. That's why the pool heater ends up filed under Cabin 3, why telling every guest something means seven separate messages, and why a wedding that books the whole property has to be entered one unit at a time.
Pilot stage · first 100 customers: first unit free for life
A per-property switch, not a separate product · Free for your first unit
The operational difference
A compound isn't a bigger STR. It's a different job.
Most of what makes a multi-unit property hard has no equivalent in single-listing software, because the assumption underneath it is that every problem belongs to exactly one unit and every booking is for exactly one unit. Both are wrong here.
One failure, every guest
A broken dishwasher affects one cabin. A closed pool affects all seven, plus everyone arriving this week. In single-listing software there's nowhere to put that, so it gets logged against whichever cabin happened to report it and stays invisible to everyone else.
Shared amenities are their own record in TraxKey, with their own status and maintenance thread. Not a ticket on a cabin.
Telling people is a broadcast, not a reply
When the hot tub goes down, the people who need to know aren't one guest — they're every party currently on the property, across every cabin, regardless of which platform booked them. Doing that by hand means checking each unit's calendar and sending the same message repeatedly.
One action notifies every guest currently on-site. TraxKey works out who that is from the calendars.
The best bookings are for the whole place
Weddings, reunions, corporate retreats. They're the highest-value nights on the calendar and the hardest to enter, because a per-unit booking system has no way to express "all seven cabins, one party, one rate" — so it becomes seven bookings you have to keep in sync by hand and pray nobody double-books a cabin.
A buyout is one booking. TraxKey blocks every unit at once and refuses it if any cabin is already taken, including via synced Airbnb or Vrbo calendars.
Guests report the pool, not their cabin
A guest who finds the firepit unusable doesn't have a problem with their unit, and asking them to file it against their cabin produces a maintenance record that's wrong the moment it's written and useless to whoever handles it.
The guest link lets them report a shared amenity instead of their own unit. No login, same as everywhere else in TraxKey.
Turning it on
One switch, per property
It's a mode on a property you already have, not a separate plan or a migration. Flip Experiential / Micro-Resort on from the Onboarding page and that property gains amenities, on-site broadcast, and buyouts. Everything else — maintenance, vendors, turns, calendars — keeps working exactly as it did.
It's per-property on purpose. Plenty of operators run a compound and a few ordinary listings across town, and those shouldn't be forced into the same shape. Standard properties stay standard.
Main pool
Notify guests currently on the property
Pool heater is being repaired, back online Thursday.
Notified 6 of 6 active guests by email.
Why you haven't found this elsewhere
Too big for STR tools, too small for hotel software
This isn't a feature nobody got around to. It's a segment that falls between two markets, and neither has a commercial reason to come get it.
Single-listing STR tools
Hostaway, Guesty, Hospitable, Lodgify. Built around the listing as the atomic unit, which is the right call for the vast majority of their customers. There's no object in the data model that a pool could be, and adding one changes assumptions everywhere.
Hotel PMS
Cloudbeds, Mews, and similar. They understand shared facilities perfectly well — for a property with a front desk, a night audit, and a department that owns the pool. Priced and shaped for 80 rooms, not 7 cabins run by two people.
Turnover tools
Breezeway, Turno. Genuinely deeper than us on cleaning workflows and inspections. But they schedule work on units, and a shared amenity is not a unit, so a compound's most disruptive failures live outside what they track.
Straight about where this is
What's built, and what isn't yet
Everything on this page is working software you can use today: amenities with their own status and maintenance history, on-site guest broadcast, whole-property buyouts with conflict checking across synced calendars, and guest-side amenity reporting.
What isn't built yet, and matters for a compound: a buyout checkout doesn't batch the turns. When a wedding party leaves and seven cabins need cleaning against one deadline, TraxKey opens those turns per unit the way it always does rather than treating it as one coordinated job with a crew. That's the next real piece of this, and we'd rather say so than let you discover it in your second week.
Amenity-level dynamic pricing — charging differently because the property has a lake — isn't there either. Pricing works per unit today, and buyouts take a total rate you set.
Everything else comes with it
This is a mode, not a stripped-down product
A compound still has maintenance, vendors, cleaners, supplies, damage, parts on order, and guests reporting problems at 10pm. All of that is the same platform: the AI maintenance coordinator that reads the request and matches a vendor on real performance history, occupancy-aware urgency from your synced calendars, automatic cleaning turns, and dynamic pricing with no per-listing fee.
Add your property, flip the switch
Free for your first unit. No credit card. If a compound is what you run, you'll know within an afternoon whether this fits.
Pilot stage · first 100 customers: first unit free for life