About OpenApp

OpenApp is physical security as a service: it connects to access control hardware and automation systems, normalizes them into a consistent model, and exposes them through a single platform.

API-first

OpenApp is API-first. Everything in the product is designed to be automated and integrated into your workflows.

• API reference: OpenApp API Reference

What the product does

At a high level, OpenApp helps you:

• Connect integrations (Home Assistant, KNX, MQTT, Shelly, PalGate, etc.)
• Model devices and entities consistently across vendors
• Organize entities into zones (rooms/areas/floors) when applicable
• Control and observe through a unified interface and APIs
• Apply access controls via orgs, users, and roles

How the hierarchy works

The core hierarchy is:

flowchart TD
  Organization --> Integration
  Organization --> User
  User --> Role
  Integration --> Device
  Integration --> Zone
  Device --> Entity
  Zone --> Entity

Quick definitions

• Organization (org): tenant boundary; can be hierarchical.
• User: identity (name/email).
• Role: permission grant within an org (stored on the org as user_id -> roles[]).
• Integration: a configured provider connection owned by an org.
• Device: a physical/virtual device owned by an org and bound to an integration instance.
• Entity: a controllable/observable unit on a device (relay, light, sensor, etc.).
• Zone: a logical/physical space (hierarchical) typically sourced from an integration; entities may optionally belong to a zone.

For the full data model and “source of truth” pointers into the repository, see:

• Repository hierarchy (data model)