A conference is a system
Programming, people, money, partners, places, communication, and event-day decisions affect one another. The software should understand those relationships.
About ConferenceOS
AI should do more than help plan the event.
ConferenceOS is built around a simple idea: your chosen AI should understand the live conference, complete governed work across it, and leave the organizer firmly in control.
01Why it exists
Make the event operable, not merely searchable.
ConferenceOS gives AI the event-specific context and boundaries needed to be an operations partner, not another disconnected writing tool.
Organizer attention is scarce
AI should absorb reconciliation work and repetitive handoffs so the team can focus on judgment, experience, and the people in the room.
Each event should compound
Structure, workflows, decisions, and operating history should make the next conference better instead of disappearing across one-off tools.
02What we believe
Open at the edges. Governed at the core.
An agent-ready platform should preserve choice and control as models, providers, workflows, and conference formats change.
Bring the AI you trust
Claude, ChatGPT, and other MCP-compatible assistants connect through a model-neutral interface instead of a captive embedded copilot.
Make authority explicit
Roles, permissioned tools, approval gates, and action history keep AI useful without giving it invisible or unlimited control.
Keep the operating layer portable
Provider choice, isolated deployments, versioned APIs, webhooks, exports, and an SBOM keep the platform inspectable and adaptable.
Conference operations, rethought for agents
Open the live demo