“The whole platform shares one shape: a stay, the people around it, and the work it asks of each of them.”
Platform overview
Every stay, every team, one flow.
SuperNest connects the guest app, host app, cleaner workflow, AI concierge, and ops console around the stay itself, from invite to checkout.
Connected operating graph
One product, one shared stay context.
4connected surfacesHost, guest, cleaner, and ops
6stay workflow stagesInvite through checkout
12ops console areasFrom properties to AI controls
0external QR providersLocal QR generation by default
Connected operating graph
Surface 01
Host app
A clear inbox, task view, property context, and review signals for the host behind the stay.
- — AI-informed replies
- — Tasks tied to every stay
Surface 02
Guest app
A polished stay hub for arrival, AI concierge, house guide, requests, local picks, and checkout.
- — Invite code handoff
- — Voice notes in chat
Surface 03
Cleaner app
Schedules, assigned tasks, checklists, offline drafts, photo proof, and escalation in one flow.
- — Proof gallery
- — Issue escalation
Surface 04
Ops console
Operational visibility across properties, stays, guests, hosts, tasks, trust, analytics, AI, and network ops.
- — Filters and bulk actions
- — Demo-mode gating
V2 operating network
The next SuperNest connects hospitality, operations, revenue, trust, and local commerce.
V2 moves SuperNest from stay software into an AI-assisted hospitality network for premium independent properties. Every guest-facing promise is paired with backend state, admin control, audit, entitlement, and operational fallback.
Owners
Owner Concierge Mode
Coordinate guest requests, owner approvals, cleaner escalations, service timelines, and weekly operating digests from one accountable operating layer.
Guests
Trip Copilot
Build weather-aware itineraries, save local favorites, share plans with companions, and request supported restaurant or experience bookings.
Guests
Guest Passport
Carry consented preferences, companions, accessibility notes, favorites, and membership benefits across eligible SuperNest stays.
Hosts and operators
Quality Graph
Connect tasks, proof photos, incidents, access readiness, weather, and review themes into readiness intelligence and Quality Certified badges with evidence.
Owners
Revenue Autopilot
Review pricing actions, direct rebooking value, partner income, service costs, and owner ROI with clear assumptions and approvals.
Owners and operators
Compliance and Trust Vault
Govern compliance records, access policies, smart lock state, emergency contacts, sensitive documents, and audit trails.
Guests and partners
Partner Marketplace
Turn local recommendations into measurable partner experiences with booking state, quality review, commission, and settlement controls.
Cleaners and vendors
Workforce OS
Give field teams routes, proof guidance, supply requests, paid exceptions, vendor work orders, and approval flows.
Operators
Operator Brand Kits
Deliver co-branded or white-label guest experiences while SuperNest keeps trust, privacy, and operations controls intact.
Guests and hosts
Network Discovery
Let eligible guests discover, save, and request direct bookings for Quality Certified SuperNest properties with host-controlled rules.
Admins
AI Operations Workbench
Replay workflows, compare prompts and models, monitor cost and latency, enforce guardrails, and roll back experiments.
Enterprise operators
Developer Platform
Connect scoped API keys, signed webhooks, replayable delivery logs, exports, and sandbox workflows into operating systems.
Proof-oriented paths
Availability varies by package, market, provider readiness, and operational coverage. SuperNest distinguishes software, AI-assisted, human-reviewed, managed-service, and third-party fulfilled workflows before launch.
App, admin, backend parity
V2 features are governed from the same records the apps depend on.
SuperNest does not describe app features, admin tools, and backend automation as separate products. Each V2 workflow needs an app surface, an admin recovery path, and durable evidence for audit, entitlement, notification, provider, and policy state.
App surfaces
Role-aware workflows show the current operating state.
Guests see Trip Copilot, Passport consent, booking approval, quality badges, and direct booking state. Hosts see Concierge Mode, readiness, revenue, compliance, Access Vault, Brand Kits, and Network controls. Cleaners see route, proof, supply, exception, vendor, and escalation context.
Admin console
Every app promise has an operator control plane.
Ops teams govern owner approvals, Trip Copilot booking fallbacks, Guest Passport privacy queues, Quality Graph interventions, Revenue Lab writebacks, Trust Vault access, Partner Marketplace settlements, Workforce OS, AI Workbench, and Developer Platform delivery.
Backend evidence
Actions are tied to audit, policy, and recovery records.
V2 routes persist approval decisions, provider attempts, notification intents, sensitive access logs, webhook deliveries, data exports, idempotency keys, fallback assignments, and route ownership so app and admin states do not drift.
Invite to checkout
Every surface sees the same stay.
- 01Step
Host sends invite
Booking context, stay details, and attribution travel with the guest before the app opens.
- 02Step
Guest opens app or scans QR
Deep links open the app first, then preserve the invite through store and waitlist fallbacks.
- 03Step
AI answers common questions
The concierge answers from property facts, guide content, weather context, and approved responses.
- 04Step
Requests route to the right team
Guest needs become host tasks, cleaner assignments, or ops incidents with clear ownership.
- 05Step
Cleaner completes proof
Checklists, captions, thumbnails, retries, and local drafts keep field work accountable.
- 06Step
Ops tracks the stay
Operators see status, trust signals, analytics, tasks, hosts, guests, recommendations, and AI behavior.
Role-aware mobile app
The same SuperNest app opens in the correct mode for each person attached to the stay.
Mobile app01
Host
Dashboard, inbox, properties, tasks, review protection, team settings
Mobile app02
Guest
Stay hub, arrival guide, chat, requests, local discovery, checkout
Mobile app03
Cleaner
Schedule, assigned tasks, checklist detail, photo proof, escalation
Ops console04
Operator
Admin console, trust queues, analytics, bulk actions, AI controls
Proof-driven operations
Tasks, checklists, proof, and escalation stay connected to the work.
Step 01
Cleaner opens task with property and arrival context
Step 02
Checklist progresses with each item saved as work happens
Step 03
Photo proof attaches with caption, thumbnail, retry, and remove
Step 04
Blocked items escalate with task context already attached
Step 05
Host and ops review proof against the stay before checkout
Invite → download handoff
From a sent invite to a stay-loaded app, in four well-named steps.
- 01 · Invite issued
Host or ops creates the invite; booking context travels with it.
- 02 · Code lands
Guest receives the code via email, SMS, or QR — never as a screenshot of a screenshot.
- 03 · App opens
Deep link opens the app first, with store and waitlist as honest fallbacks.
- 04 · Stay context
The invite hydrates the stay hub — no rebooking, no re-entry, no second screen.