Subcult OS is software for the people running a small event: independent venues, collectives and crews. The plan, the staffing, the guest list and the end-of-night report sit on one sheet that the whole team reads. It is in alpha development, and no real-event operation has been verified on it.

Explore Subcult OS · Feedback and feature requests · Development guide

What it covers

Stage	What you can do
Plan	Create a workspace, draft an event, reuse event templates, and publish a public event page.
Coordinate	Invite collaborators, assign staffing, keep private contacts and commitments, prepare the run of show, and collect private act tech sheets into one input list.
Welcome guests	Let guests reserve free tickets, open their ticket links, and check them in by lookup or ticket code.
Run the night	Use the mobile client for scanning, door search, the run of show, and the live dashboard.
Close out	Run End of Night and review the private event report.

Attendees find published events on the public discovery page. Workspace notes, staffing, contacts and reports stay private to the organizer workspace.

Web and phone

Planning and public event pages are on the web. The Expo mobile app carries the event-time tools: scanner, door search, run of show and the dashboard, with organizer, staff and attendee flows. It runs in Expo Go for development. App-store availability is not promised.

Private venue and event access worksheets let owners record observations, unknowns, and review dates without publishing unverified accessibility claims.

The private input list combines act inputs, shared channels, monitor needs and backline. Operators can open it from the run of show; owners and organizers edit sheets and print them from the web.

Current scope

Subcult OS is in alpha development. The documented lifecycle starts with workspace creation and free ticket reservations and ends with door check-in and an event report. Qualification so far uses local rehearsal data; no live event operation has been verified. Paid ticketing code exists but needs a configured Stripe integration and has not been qualified with a live provider; outbound email requires explicit provider setup. AT Protocol integration remains outside the qualified live-provider scope.

See the development guide for the implemented lifecycle, mobile setup, integration limits, and production readiness checklist.

Development

To run a rehearsal or contribute, start with the local setup and run make verify before proposing a change.

Built by Subcult. Licensed under GPL-3.0-only.

The web build renders the public discovery introduction into HTML and emits its canonical URL, robots file, and sitemap using PUBLIC_WEB_URL. Published event metadata is filled from the public API response. Private workspace, account, and ticket pages emit noindex; unknown static routes return HTTP 404.