PalGate Cloud via OpenApp vs the native PalGate app
PalGate provides cloud control of gates and controllers through its mobile app and API. OpenApp links PalGate Cloud as one integration among many — so gates participate in the same policies, invites, and automations as doors on other vendors.
Task guide: Open a gate with PalGate Cloud. Integration setup: PalGate Cloud.
Use the PalGate app directly when
Section titled “Use the PalGate app directly when”- One gate, one household, no guest-access product requirements
- You only need manual open/close from a phone
- No external software (PMS, parcel, agent) must orchestrate access
Use OpenApp + PalGate Cloud when
Section titled “Use OpenApp + PalGate Cloud when”| Scenario | Benefit |
|---|---|
| Building with intercom + parking gate | One org, portals + PalGate entities |
| API / SDK automation | switchable.open like any other entity |
| Mixed vendors (PalGate + Shelly + HA) | Single control plane |
| Time-bound guest access | Invites apply to portals; gates via entity actions |
| Audit and roles across sites | Org model beyond a single PalGate account view |
Trade-offs
Section titled “Trade-offs”- Extra layer — OpenApp must stay available for API path; PalGate cloud is still authoritative for the gate hardware link.
- Setup — Initial PalGate linking (QR or credentials) is required once per integration.
- Account — PalGate subscription and terms still apply; OpenApp does not replace PalGate licensing.
Agent note
Section titled “Agent note”Automations should target OpenApp entity ids, not PalGate device strings directly, so policy and audit stay consistent. Map external_id to PalGate gate ids during device provisioning.