Guides
Member Access OS docs
Guides below start with business and onboarding, then deployment and rollout, then technical references. Share this path: /docs.
Background
How to read this library
Member Access OS is built around Join, Pay, and Visit: sign-up, payment or proof of payment, then active membership and—when you deploy it—showing up at the door with a pass or credential. That path stays the spine whether someone is on recurring billing, prepaid credits, or a mix.
The platform supports recurring membership models, credit-based memberships (bundles of visits or balances), and hybrid setups that blend both. Typical venues include gyms, fitness studios, sports clubs, and coworking spaces. Documentation proceeds from organizational choices to rollout to deeper technical guides.
You do not need engineering depth to absorb the onboarding section. Conversely, rollout and technical guides assume you are configuring or maintaining a deployed environment—names, sequencing, and checklists—not introductory product positioning.
Reading paths by role suggests where owners, operations, facilities, marketing, finance, and technical leads usually start.
Business & onboarding
Sponsors and operators: scope and decisions without vendor-specific internals—useful in kickoffs and contracting.
Deployment & rollout
Go-live readiness: installs, preflight checklists, fleet inventory, and field steps before or during cutover.
Technical
Engineering-facing: edge nodes, certs, integrations, and infrastructure you operate—not sponsor-facing rollout copy.
Other
Unclassified guides (assign a category when you edit doc-registry.ts).
- ArticleAccess Engine Memory Safety & StabilityRead →
- ArticleGoogle Smart Tap on the gate (Pi + Wallet Mate II)Read →
- ArticleInstitutional & Group AccessRead →
- ArticleMember guide: tap your NFC tag at the gateRead →
- ArticleMember guide: tap your phone at the gateRead →
- ArticleSite router swap runbook (Pi + Shelly on same Wi‑Fi)Read →
- ArticleSystem Architecture: The Four Control PlanesRead →