Skip to content
OAOpenAppPhysical Security as a Service
Login

Boutique hotel access — PMS, virtual lobby, and gate preservation

Boutique hotels (~50–120 rooms) need enterprise-grade audit and automation without legacy chain infrastructure. Typical requirements:

  • PMS-driven check-in / check-out access windows
  • Virtual lobby directory — visitors call front desk or room from a phone
  • Preserve perimeter gate vendor where possible (integrations — not always Wiegand retrofit)
  • Phased room-key migration may keep Salto / VingCard for RFID or mobile wallet keys

OpenApp orchestrates lobby, gates, staff policies, and guest portal links. It is not a replacement for in-room lock credential systems — see OpenApp vs Salto / Brivo.

Usually no for software-first lobby flows. OpenApp Virtual Access provides directory, call, message, and unlock on the same portal surface. Compare: OpenApp vs ButterflyMX.

Choose dedicated lobby touchscreen hardware only when branded panel UX is a deliberate amenity.

PMS (Opera, Mews, Cloudbeds, custom)
│ reservation lifecycle webhooks
Your integration service
│ staff roles, guest invites, checkout disable
OpenApp
├─ Virtual Access directory (lobby QR/NFC)
├─ Staff / housekeeping time-bound policies
├─ Guest invite links (browser, no app)
└─ Gate / relay entities (parking, service entrances)
Room locks (optional): Salto / VingCard — parallel stack during migration

Gate path: pick a provider from the integrations catalog (cellular gate cloud, relays, and others — not only Wiegand perimeter panels).

RequirementOpenApp approach
PMS integrationInbound webhooks → your middleware → OpenApp invite API
Phased RFID + mobile keysRoom keys on lock vendor; OpenApp for lobby + gates
Existing gate vendorMatch to integrations catalog
Audit deliveryDashboard review + invite usage; log switchable.open in your layer — no outbound audit webhooks
Virtual lobbyIncluded — not a separate intercom SKU