The hospitality showroom for FallHub · Wishwood live

Your holiday rental. Running itself.

Roost is the hospitality showroom for FallHub — the sovereign AI-first operating system for stays. See Wishwood, a real cottage taking real bookings today, running the whole thing. Deploy your own with the same substrate in an afternoon. Own everything. Zero monthly rent. MIT.

The IRL proof

Wishwood is not a demo. It's the R&D lab.

Wishwood is a real property with real guests, real bookings, real complaints, and a real owner learning the system. Every improvement built for the hospitality vertical of FallHub lands at Wishwood first. Every rough edge gets sanded down against real load. Every socket gets stress-tested by an actual cottage handling actual holidays.

What you see at wishwood live is what you deploy when you fork FallHub's hospitality template. Same code. Same substrate. Same autopilot. Same training simulator.

The relationship: Wishwood is the reference implementation. FallHub is the vertical-neutral substrate. Roost is the showroom that lets hospitality owners see the proof and buy in.

Try it live

  • Hub · operator surface · inbox, calendar, autopilot pill
  • Autopilot · BYOK config, kernel viewer, autonomy dial, event stream
  • Training simulator · WebLLM fake guests · practice before real ones
  • How it works · plain-English tour of the whole thing
What FallHub does for a stay operator

The autopilot · concretely.

Inbox

Reads across Airbnb, Booking, VRBO, direct, email, WhatsApp, DMs. Drafts every reply in your voice, grounded in your kernel. Sends the safe ones automatically.

Quotes

Prices stays with seasonal + occupancy-aware curves. Reads your kernel for cleaning fee, deposit, extras. Confidence-gated auto-send below thresholds.

Guest care

Arrival codes, wifi passwords, checkout instructions, follow-up review nudges. Everything a great host does · at scale.

Ops

Housekeeper tasks generated automatically at turnover. Maintenance callouts routed to the right contractor. Cleaning invoices auto-triggered.

Compliance

GDPR guest data consent flow. Fire / gas cert reminders. Local council registration tracking. Sovereign — never our servers.

Learning

Training simulator with fake guests so you learn the flow before real customers arrive. WebLLM-powered · free forever · runs on your device.

The stack owner-side

What you get. All MIT.

Browse all 60+ modules
Three paths to Roost

How to get in.

1 · Free · deploy yourself

Fork the FallHub repo. Pick the hospitality vertical. Fill the kernel with your property. Live in an afternoon.

Free setup guide

2 · Pro · done for you

We deploy for you within 48 hours. Kernel pre-populated from your reviews. Autopilot calibrated. £199/month.

Book Pro setup

3 · List on Roost commons

Whether you deploy FallHub or not, list your stay on the Roost commons — a host-owned marketplace, zero fees, protocol-based.

Host protocol
The commons underneath

Roost as a protocol.

Behind the FallHub-hospitality showroom, Roost also runs as a host-owned protocol — a directory of stays declared by hosts themselves, not owned by any middleman. Every FallHub instance can publish its availability to the commons via a JSON manifest. Guests browse the commons directly.

The commons is optional. You can run FallHub without ever listing on Roost. But if you do list, you get a distribution channel that takes zero fees, harvests zero data, and can never delist you for arbitrary reasons.

  • Zero-fee listing · zero booking commission
  • Zero data harvest · guest contact goes direct
  • Protocol-based · anyone can host their own Roost node
  • JSON registry · queryable, forkable, mirrorable

Commons stats

0fees taken

0data harvested

nodes possible

Read the protocol
Why this pairing works

FallHub runs your property. Roost connects it.

Most stay-tech offers either the operator surface (Guesty, Hostaway) or the distribution channel (Airbnb, Booking). FallHub does one, Roost does the other. Both MIT. Both sovereign. Both zero-fee.

Get started · hospitality path

Next steps.