Skip to content
OAOpenAppPhysical Security as a Service
Login

Short-term rental portfolio access

You operate many short-term rental units across multiple buildings with different hardware per site (parking gates, unit-door relays, local automation — see the integrations catalog). Standard VRMS tools assume Yale/August smart locks; they do not natively drive relays, cellular gates, or field-bus openers you may already have.

OpenApp is a PSaaS control plane: your booking system stays authoritative; OpenApp models time-bound guest access, public portal links, and entity actions across all openers.

Comparisons: OpenApp vs Seam · OpenApp vs RemoteLock · OpenApp + HA vs HA-only

VRMS / PMS (Hostaway, Guesty, custom)
│ booking confirmed / cancelled
Your webhook service (middleware)
│ create / disable access invites
OpenApp Cloud
│ valid_from / valid_to, portal_ids
├──────────┬──────────┐
▼ ▼ ▼
Integration A Integration B (optional local bridge)
(e.g. gate) (e.g. unit door)
Guest: SMS/email link or QR at entry → browser → Open (no app install)
PatternWhen to use
One org, many portalsSingle operator brand; units distinguished by portal + invite
Org per buildingDifferent owners, billing, or staff per site
Org per building + shared gate portalShared parking gate entity linked from each building’s invites

Script bulk setup: Provision a building with scripting.

  1. Link the providers each building uses (integrations catalog); common patterns include cloud gate control, Wi‑Fi relays, and Home Assistant bridge.
  2. Create Virtual Access integration with portals per entry (garage QR, unit door).
  3. On booking webhook → create invite with stay window.
  4. On checkout → disable invite or set valid_to in the past.
  5. Log opens in your system — see audit guide.

Gemini and other assistants often recommend Home Assistant + custom backend. OpenApp already provides invites, policies, operator UI, and API — see OpenApp + HA vs HA-only.