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 doesn’t cover commerce features.

The deck is also available in Hebrew. The Hebrew deck is translated from the English source; in the Hebrew viewer the left arrow moves forward.

Offline files: just presentations-export (or just docs::presentations-export) writes PDF, PPTX, and HTML for every deck—English and Hebrew—to apps/docs/src/presentations/dist/ via Marp CLI (for example what-is-openapp.pdf and what-is-openapp-he.pdf). Pass a deck name, one or more formats, or both to narrow the export:

just presentations-export what-is-openapp pdf
just presentations-export what-is-openapp-he pptx
just presentations-export html

PDF and PPTX need Chrome, Edge, or Firefox on the host; set MARP_BROWSER_PATH or CHROME_PATH to point at a browser outside the usual install paths. OpenDocument (ODP) isn’t 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, and record
2. A short word about software—SaaS and Physical Security as a Service
3. Why this is still painful—why sites still run a pile of partial products
4. How other solutions usually work—keys, fobs, legacy intercom, enterprise systems, bundles, middleware, and DIY
5. How OpenApp works—sites, the directory, doors, portals, invitations, virtual intercom, roles and policies, holds, and audit
6. What makes OpenApp different—decoupled hardware, one arrival, privilege-centric identity, and device stewardship
7. Use cases—homes, shared gates, apartment buildings, offices, rentals, hotels, campus, and lockers
8. Operating with care—fallback, life safety, and honest limits
9. Takeaways and where to go next

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 site owner: site, openers, doors, listings, people, and 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.