Manifesto
Conferences deserve better software
The duct-tape era should end.
Luma for tickets. Sessionize for speakers. Spreadsheets for everything else. Mailchimp for email, Notion for the run-sheet, a group chat for the panic. Five sources of truth is zero sources of truth — and the gaps between them are where conferences go wrong.
One system of record.
Events, people, schedule, sponsors, money — entered once, used everywhere, exported any time. Every surface reads from the same place, so the website, the widgets, the assistant and the team are never out of sync.
Agent-first is an architecture, not a feature.
Every capability in ConfOS is one typed, permission-checked, audited action in a single registry. The dashboard is a client of it. So is the API. So is the assistant, and so is the MCP server your agents connect to — their tool schemas are generated from the registry itself.
AI bolted onto software drifts out of date. AI generated from the registry cannot.
Humans approve every change.
Agents propose; organisers confirm; the audit log names both. There is no bypass flag — and a lint rule in the codebase makes sure there never is one. Autonomy is a dial that belongs in your hand, not ours.
Reliability is the feature.
A conference happens once a year. There is no retry. The public surface is edge-cached and keeps serving even if the origin goes down; a release-blocking isolation suite runs against every action before anything ships.
Interop over empire.
We sync your ticketing — Luma first — rather than demanding you move it. Your data imports and exports as CSV whenever you want it. Software that holds your event hostage doesn't deserve your event.
Who’s building this
ConfOS is built by the team behind Create With’s events. We run the kind of 200–1,000-person tech conferences this platform is for, and we’re onboarding a small group of founding events we can work with directly — same channel as the people writing the code.
Help us build it.
Join the waitlist and we’ll email you when founding onboarding opens.