What is OpenApp

OpenApp is Physical Security as a Service: a control plane for doors, gates, virtual intercom, invitations, policies, and audit across hardware you choose.

The slide deck is the orientation talk. It starts from everyday doors—no physical-security or SaaS background required—then explains the need, how other approaches work, how OpenApp works, what is distinctive, and how the same model fits homes, housing, work, hospitality, campus, and lockers.

This deck covers access control only. It does not cover commerce features.

Offline files: just presentations-export (or just docs::presentations-export) writes PDF, PPTX, and HTML to apps/docs/src/presentations/dist/ via Marp CLI. PDF and PPTX need Chrome, Edge, or Firefox on the host (or MARP_BROWSER_PATH). OpenDocument (ODP) is not a Marp CLI format.

Open the presentationFull-screen slides. Arrow keys or space to move, Esc to return to the OpenApp home page, F for fullscreen, ? for keyboard help. Print from the browser for a PDF handout.

In the deck

1. A door is a decision (identity, credential, barrier, record)
2. What SaaS and Physical Security as a Service mean
3. Why sites still run a pile of partial products
4. Keys, fobs, legacy intercom, enterprise systems, bundles, middleware, DIY
5. How OpenApp works (portals, invitations, virtual intercom, roles vs policies)
6. What makes that model different
7. Use cases, fallback, and honest limits

Each part is written so it can become a deeper talk later.

Continue in the written docs

About OpenAppValue proposition, sectors, and how APIs and scripting sit beside the dashboard.

Set up access controlWizard-first path for a building owner: site, openers, doors, people, policies.

Access portalsThe sign at the door: directory, resident open, and invitation open.

Model by sectorHow the same platform maps to home, housing, office, rental, hotel, campus, and lockers.