01
Clubs first
Every club gets a home page, member roster, and an event calendar — no more Google Docs bureaucracy.
CampusConnect × Open-Source Student Communities
Every club. Every event.
One brutally simple OS.
CampusConnect is an open-source operating system for college clubs and tech communities. Run events, grow membership, ship certificates — without the spreadsheet chaos.
About the platform
Built for the way student communities actually work.
02
Events that ship
RSVPs, check-ins, feedback, and post-event reports in one flow. Nothing lost to Instagram DMs.
03
Proof of work
Auto-issued certificates and portable member profiles for hackathons, workshops, and volunteer hours.
Core benefits
Less admin. More building.
500+
Events run
120
Active clubs
12k
Members onboarded
100%
Open source
How it works, in one line
Create a club. Publish an event. Ship certificates.
CampusConnect collapses the tools clubs juggle — forms, spreadsheets, chat, posters, email — into one workflow that respects your time.
- Spin up a club page in under 60 seconds
- Publish events with automatic RSVP + calendar sync
- Check members in at the door with a QR scan
- Auto-generate signed PDF certificates
- Post updates to a shared discussion feed
- Export data as CSV whenever you want
Why this matters
Student communities deserve infrastructure, not workarounds.
Handoff hell
Every year, club leadership rotates, and half the knowledge dies in a personal Notion.
Data locked in DMs
Attendance in a WhatsApp group, RSVPs in a form, feedback nowhere. Never joined up.
No proof, no trust
Members do real work but leave with nothing verifiable to show recruiters.
The landscape
Where CampusConnect fits.
vs. Google Forms + Sheets
Great for one event. Falls apart across a year, across clubs, across handoffs.
vs. Discord / WhatsApp
Perfect for chatter. Not designed to be a source of truth for membership or attendance.
vs. Eventbrite / Luma
Solid for the general public. Doesn't understand semesters, clubs, or student verification.
vs. Custom college portals
Locked to one campus, no interop, no open-source community driving improvements.
Two ways to run your club
Hosted or self-hosted. Same features either way.
Grab the managed cloud instance and start today, or fork the repo and deploy on your college's infra. The core is MIT-licensed and hackable to the bone.
Recommended
Cloud
Managed hosting, SSO with your college email, zero DevOps.
Fork it
Self-host
Docker Compose up. Own the database, own the data.
Under the hood
Boring, proven tech.
| Layer | Choice |
|---|---|
| Frontend | React + TanStack Start |
| Styling | Tailwind CSS v4 |
| Backend | Supabase (Postgres + Auth + Storage) |
| Certificates | PDF-lib, signed server-side |
| Auth | Email + Google OAuth |
| Deploy | Cloudflare Workers |
Integrations & tools
Plays nice with the tools you already use.
Google Calendar
Publish once, sync everywhere. Members subscribe to a club's iCal feed.
Discord + Slack
Auto-post event announcements, ping RSVPs, close the loop with reminders.
GitHub
Link hackathon submissions and workshop repos directly to member profiles.
Zapier / Webhooks
Every action fires a webhook. Wire it into whatever weird workflow you love.
Known issues & notes
We ship honestly.
Certificate generation
Bulk certificate jobs are throttled to 200/min on the shared cloud tier. Self-host to lift the cap.
Mobile check-in app
The native iOS/Android app for door-scanning is in alpha. PWA works today.