For clients

You are an organization that wants an event site. CCM deploys one Firebase project per event and operates it. Your staff run the admin. You do not fork the repo.

What you are buying#

The code is Apache-2.0. Anyone can read it. CCM's service is:

1. A managed deployment for your event
2. Setup and onboarding (sender domain, tickets, first admin)
3. Support while the event is live

The Event Runner name is CCM's. Apache-2.0 does not give anyone else the right to sell hosting under that name.

What v1 includes#

Schedule, speakers, attendees, a block CMS, emailed login codes, announcement email to your registered attendees or speakers, session materials, a media library, Eventbrite or spreadsheet tickets, and your colors and fonts.

Confirmation emails, speaker mail, and event announcements go through one agreed email provider (Postmark) from a sender address on your domain. Announcements use their own broadcast stream, apart from login codes and receipts. Every announcement has a one-click unsubscribe link, and the site does not send announcements to anyone who used it.

What v1 does not include is in the triage record: video generation, invoicing, social feeds, speaker chat. Announcement email reaches your event's attendees and speakers only; it is not a newsletter or marketing list tool.

What you will need to give us#

• Event name, dates, timezone, venue
• The public URL you want
• Who the first admins are
• Whether tickets are Eventbrite, a spreadsheet, or neither
• A sender address on your domain (for login codes). We will ask you to add SPF, DKIM, and a DMARC policy. Without that, emailed codes get quarantined.

How to start#

Open a General thread or email info@collaborativejournalism.org. Do not send an attendee list to GitHub.