Callboard vs OpenCFP

Callboard is an open-source system for managing event proposals and the work from submission through schedule publication. Organizers can build CFP forms with conditional questions, shared character limits, participant rules and close dates, then route proposals to tracks. Reviewers see their assigned submissions, while organizers can apply weighted scores in two rounds. Accepted speakers use a portal to update session details, upload headshots and materials, finish tasks and read event resources.

For planning, organizers place sessions in rooms and time slots and use a conflict view to spot overlaps. Published schedules can be embedded and provide ordered speaker and co-speaker names, calendar invites, CSV exports and API access. Documented integrations include Accelevents CSV export, optional API push, an Airtable mirror and signed webhooks, with optional Svix delivery. AI abstract triage offers an advisory score and recommendation; it cannot write committee reviews or change submission status. The main application is described as one Cloudflare Worker using D1 and R2. Callboard is self-hosted under the MIT license, at free.

OpenCFP is a free, PHP-based system for collecting conference talk proposals and managing their review. Speakers register with contact information, submit proposals, and manage profiles through a dashboard. Reviewers can view and rate talks, while administrators can review speaker information, favorite proposals, and make selections. Command-line utilities support administration of users and reviewer or administrator groups.

The application sends notifications through configured SMTP settings, and its configuration includes options for OpenCFP Central single sign-on. A Docker Compose file is provided for building and running it in containers. The README lists PHP 7.4 and recommends Apache 2 or later with mod_rewrite and AllowOverride enabled. OpenCFP is listed for Linux, self-hosted, and web use, and costs nothing. The project is in maintenance mode and accepts security fixes only. Setup guidance recommends enabling secure_ssl when possible; it requires a valid SSL certificate. The project also advises protecting collected personal information and deleting database data within 15 months of accepting submissions.