Memberships
Self-signup creates an invited member, then subscription payment activates access.
Operations software for makerspaces
Run memberships, equipment booking, paid and free events, reporting, Stripe Connect payments, and public tenant pages from one tenant-scoped platform.
MakerOps source-backed
MakerOps is built for operators who are stitching together spreadsheets, shared calendars, one-off payment links, email threads, and manual waiver checks. The app repo describes a pilot implementation spanning memberships, scheduling, events, Stripe Connect, Keycloak auth, Postmark email, audit logs, and observability.
Self-signup creates an invited member, then subscription payment activates access.
Equipment reservations enforce operating hours, maintenance windows, tier gates, and overlap rules.
Published events can be free or paid, with capacity, waitlist, discounts, and connected-account payment paths.
Admins can export lists and grant-ready monthly reports as CSV or PDF.
MakerOps source-backed
Tenant resolution starts at the host: platform subdomains and active custom domains establish the organization before protected requests continue through JWT, membership, role, and EF query-filter checks.
Every org is reachable at its MakerOps-managed slug.
Admins can verify DNS and keep the original subdomain working.
Owner, admin, accountant, staff, and member policies keep surfaces scoped.
Questions
Both. The authenticated product has member self-service flows and admin/operator workflows, while this static site explains the public platform.
No. The workflow specs keep self-signup at invited status until the first successful subscription charge or comped/admin state makes the member active.
Yes, after DNS verification and active domain status. Tenant-public wording remains review-needed in the tenant site templates.