The Operating System for Campus Management — A modular, scalable platform for managing the complete lifecycle of campus activities.
CampusOS is an open-source campus management platform designed to replace fragmented tools like WhatsApp groups, Google Sheets, and email for coordinating campus activities.
Instead of building "just another event management tool," CampusOS provides the complete infrastructure layer for campus ecosystems, handling everything from organizational structure to operations to growth.
- Coordination Chaos — Centralized platform replacing scattered WhatsApp groups
- Manual Operations — Automated workflows for event management and logistics
- Data Fragmentation — Single source of truth for all campus activities
- Vendor Management — Streamlined vendor and resource coordination
- Analytics Gap — Comprehensive insights into campus activity health
- Club Organizers — Easy event planning and coordination
- Event Managers — Streamlined check-in, RSVP, and logistics tracking
- Institute Administrators — Complete visibility into campus activities
- Sponsors — Measurable campaign performance and ROI tracking
- Developers — Clean, modular architecture for contributions
- ✅ Modular Architecture — Pluggable modules for easy scaling
- ✅ Authentication — JWT-based secure auth system
- ✅ User Management — User profiles and role management
- ✅ Club Management — Club creation and hierarchy
- ✅ RBAC — Role-based access control
- 🚧 Event Management — Create, edit, and publish events
- 🚧 RSVP System — Registration and attendance tracking
- 🚧 Check-in — Event-day attendance management
- 🚧 Analytics — Event metrics and reporting
- 📋 Task Management — Create and assign tasks
- 📋 Workflows — Track task execution states
- 📋 Calendar — Schedule and deadline management
- 📋 Vendor Management — Vendor coordination and procurement
- 📋 Resource Allocation — Resource scheduling and management
- 📋 Budget Tracking — Expense and budget management
- 📋 Sponsorship Management — Sponsor tracking and engagement
- 📋 Marketing Tools — Campaign management and assets
- 📋 System Analytics — Comprehensive reporting
- Node.js v18.0.0 or higher
- pnpm v8.0.0 or higher
- MongoDB (local or cloud instance)
- Git
# Clone the repository
git clone https://github.com/NITRR-Official/CampusOS.git
# Navigate to project directory
cd CampusOS
# Install root dependencies
npm install
# Install backend dependencies
cd backend && npm install && cd ..
# Install frontend dependencies
cd frontend && npm install && cd ..
# Copy environment template
cp backend/.env.example backend/.env.local
cp frontend/.env.example frontend/.env.localBackend Setup (.env.local)
NODE_ENV=development
PORT=3000
MONGODB_URI=mongodb://localhost:27017/campus-os
JWT_SECRET=your-secret-key
Frontend Setup (.env.local)
NEXT_PUBLIC_API_URL=http://localhost:3000
# Terminal 1: Start Backend (from project root)
cd backend
npm run dev
# Terminal 2: Start Frontend (from project root)
cd frontend
npm run dev- Backend: http://localhost:3000
- Frontend: http://localhost:3001
- Project Structure — Detailed architecture and module layout
- Problem Statement — The problem we're solving
- Architecture Decisions — ADRs and design decisions
- Roadmap — Development phases and timeline
- Copilot Guidelines — AI development rules and patterns
- Humanet Context — Project documentation and governance
- Backend: Node.js + Express.js — Fast, lightweight server
- Frontend: Next.js + React — Modern, full-stack framework
- Database: MongoDB — Flexible schema for rapid development
- Architecture: Modular, plugin-based system with dynamic loading
Every feature is a self-contained module in /apps/:
- Routes, controllers, services, and schemas together
- No direct module-to-module dependencies
- Communication via shared services or database
- Dynamic module loading at startup
- Enable/disable features per deployment
- Extensible without core changes
- Foundation — Auth, Users, Clubs, RBAC
- Event — Events, RSVP, Check-in
- Execution — Tasks, Workflows, Calendar
- Operations — Vendors, Resources, Budget
- Growth — Sponsorship, Marketing
- System — Notifications, Audit, Analytics
We welcome contributions from everyone!
Quick Links:
- Read the docs — Start with COPILOT.md
- Understand the architecture — Check .humanet/
- Pick an issue — Look for
good-first-issuelabel - Create a feature branch —
git checkout -b feature/your-feature - Make your changes — Follow modular structure
- Update documentation — Update Humanet if needed
- Submit a PR — Include description of changes
- Follow modular architecture strictly
- Keep modules independent
- Write tests for new features
- Update Humanet documentation
- Keep controllers thin, logic in services
This project is maintained by:
- NITRR Open Source Team — Maintained by NIT Raipur
Need help?
- Open a GitHub Issue
- Start a Discussion
- Check Humanet docs
- Project structure setup
- Humanet documentation
- Architecture decisions
- Auth module
- User management
- Club management
- RBAC system
- Event management
- RSVP system
- Check-in system
- Task management
- Workflow system
- Calendar management
- Vendor management
- Resource allocation
- Budget tracking
- Sponsorship management
- Marketing tools
- Analytics
- Performance optimization
- Security hardening
- Production readiness
See Project Board for real-time progress.
This project is licensed under the MIT License — see the LICENSE file for details.
- Open Source Community — For inspiring modular architecture patterns
- Campus Ecosystem — The problem domain that inspired this project
- All Contributors — Thank you for making this better
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- Documentation: .humanet/
- Architecture: Discussions
Made with ❤️ by Students-NIT Raipur
CampusOS — The Operating System for Campus Management