FoundationRequired
Vercel
Hosting, deployment, edge delivery, and scheduled execution.
Required services
Opinionated core. Replaceable edges.
ConferenceOS keeps the foundation intentionally small, then enables specialist services only when the event needs their capability.
01Service map
A small foundation with clear jobs.
Each service exists for a defined capability and stays outside the core event model whenever practical.
People + teams→ ConferenceOS core→Specialist services
FoundationRequired
PostgreSQL / Neon
The persistent system of record for events, people, money, and content.
IdentityFull platform
Clerk
Authentication, profile management, roles, and protected workspaces.
CommerceFor paid events
Stripe
Hosted checkout, payment confirmation, discounts, and refunds.
CommunicationFor email
Resend
Transactional email for confirmations, reminders, and reports.
IntelligenceFor AI operations
Anthropic or OpenAI
The selected assistant for event questions, planning, and permissioned operational work.
AssetsFor uploads
UploadThing
Managed uploads for speaker photos, sponsor assets, and event media.
AutomationOptional
Inngest + ESP adapters
Background jobs plus optional Beehiiv, Kit, and Mailchimp audience sync.
Provider keys are environment-scoped. ConferenceOS keeps application secrets out of the codebase and degrades non-core integrations when they are not configured.
02What is actually required
Match the stack to the event.
A free community event and a multi-track paid conference can share the same core without carrying the same service footprint.
Always required
Application delivery and a durable PostgreSQL event record form the minimum operational foundation.
Enabled for the full platform
Identity, payments, email, and managed uploads turn on when the deployment needs those capabilities.
Optional and replaceable
Automation, audience synchronization, and AI operations sit at the edge so they can be configured without changing the event model.
Every connection has a defined boundary
Explore integrations