~/edgeos
The operating system for curated gatherings.
Applications, passes, payments, housing, check-in — and a program your attendees can build themselves. Everything your gathering needs. One platform.
7 days · full platform · real tenant · no card required
8 organizations run their gatherings on EdgeOS.
~/the-problem
You're running a multi-day program on spreadsheets.
Applications in one tool. Reviews in a shared doc. Payments in loose links. Housing in a spreadsheet. Check-in on a printed list. The community in a group chat. And next year, you start from zero.
EdgeOS replaces the whole stack — and remembers everything for the next edition.

~/how-it-runs
From applications to check-in, and everything in between
01 applications flow in
01 applications flow in
02 reviewers curate
03 passes are issued
04 the calendar fills
05 check-ins light up
A. Khumalo
applied · weeks 2–3 · housing
M. Vidal
applied · weeks 1–4 · scholarship
J. Okonkwo
applied · full program · +1 companion
L. Sato
applied · weeks 3–4
M. Vidal
3 reviews · above threshold
A. Khumalo
2 reviews · 1 required approval left
L. Sato
3 reviews · above threshold
J. Okonkwo
below threshold · moved to waitlist
~/checkout · pass issued
M. Vidal · Full pass
weeks 1–4 · housing: cabin B · 3 installments
~/program · thursday · by venue
The Barn
Greenhouse
Commons
Repair Café
10:00 · 24 RSVP
Zine workshop
10:30 · 12 RSVP
Morning run club
07:00 · 31 RSVP
Biology of aging
14:00 · 58 RSVP
Open studio
15:00 · drop-in
Community dinner
19:00 · 140 RSVP
every session above was created by an attendee
412 attendees checked in · QR + self check-in · door-staff role
8
organizations run their
gatherings on EdgeOS
21
editions
across the platform
8,400+
attendees
across all editions
7,700+
applications
curated
~/product
One system, from application to next year.
~/applications
Pick the right people.
The application is a first-class object, not a throwaway form. Per-popup form builder, no code. Reviewers with weighted scoring — define your scoring rules, acceptance thresholds and required approvals. Scholarships and application fees built into the flow.
draft → pending fee → in review → accepted / rejected / withdrawn
~/checkout
Sell weeks, not seats.
You design the checkout. A visual builder for custom checkout funnels — a different funnel per edition and per pass type. Every kind of product: passes, housing with dates, meal plans with dietary restrictions, merch, patron tiers. Atomic stock, sale windows, per-order limits.
Ways to pay built for gatherings: installments, cancellation insurance, pay-it-forward, coupons, group discounts, ambassadors, scholarships, credits, bulk grants, abandoned-cart recovery. Card or crypto, multi-currency. Companions — +1s, partners and kids — as real attendees without their own account.
~/program
Control the program while attendees create events.
Attendees create their own sessions — venue by real availability, track, tags, capacity, recurrence. RSVP, invitations, collaborators, optional organizer approval. Real venues with weekly schedules, exceptions and A/V properties. Public calendar with no login; export to .ics, Google and Apple Calendar.
Across the platform, attendees have created ~900 sessions — with 14,600+RSVPs. You didn't write the program.
~/live-ops
Run the days.
QR check-in from the backoffice with scan history. Self check-in from the attendee's phone. A dedicated door-staff role that sees check-in and nothing else. Filterable attendee directory, CSV export. Groups: cohorts, leaders, whitelists, invite links.
scan · pass valid · door: main gate
~/people
Keep the people.
The database outlives the event. One person, one persistent record — across every edition, application, pass and payment. Ratings and flags with comments and an activity timeline; flag someone once and they stay flagged next year. Enriched profiles by source. Open the next edition with your alumni already in.
L. Sato
3 editions · 2 applications · organizer of 4 sessions
~/portal
Two surfaces. One system.
A portal for your attendees and a backoffice for your staff — both under your brand: your domain, your logo, your colors, your emails.
~/api
Your gathering has an API.
Full REST API with auto-generated OpenAPI and scope-filtered discovery. Scoped keys and third-party apps: external tools — and AI agents — read and write your popup. Not just for staff: attendees issue their own keys from the portal, scoped to what their pass can see. Passwordless for everyone. Multi-language with AI-assisted translation.
$ curl api.edgeos.example/v1/popups/esmeralda-26/attendees \
-H "Authorization: Bearer <scoped-key>"
// 200 · scope: attendees:read · demo tenant
~/how-it-works
Design the steps.
01
Open applications
Build the form, pick the reviewers.
02
Optional curation
Score, discuss, accept. The rest to waitlist.
03
Sell passes
Weeks, housing, meals, companions, installments, scholarships.
04
Run the days
QR check-in, and the community publishes its own calendar.
05
Keep the people
Everyone stays in the system when you open the next edition.
~/organizers
Eight organizations run their gatherings on EdgeOS — pop-up villages, retreats, fellowships. Edge Esmeralda is one of them: a month-long pop-up village of ~1,000 people who apply, get curated, buy passes with housing and meals, and build the program themselves. Every application, payment, session and check-in runs through the platform.







8 organizations · 21 editions
~/bring-your-own-agent
Agentic access. Ask anything about your data — plug it in.
Connect your own Claude — or any LLM you use — to the EdgeOS MCP and API. Copy the Agent Brief, paste it into your agent, and ask from your own chat.
"how many people are checked in?"
→ 412 of 600 · demo tenant
"what's on today at 5pm?"
→ 4 sessions · Repair Café is nearest to you
"flag applicants below threshold with no fee paid"
→ 7 flagged · scope: applications:write
~/start
Bring your gathering online.
Seven days, full platform, your own tenant. The system behind 21 editions across 8 organizations.
