
Overview
The problem
Most LMS platforms are built as marketplaces first and learning tools second, which meant unnecessary payment infrastructure and complexity for a client who just wanted a focused, private space for their own students.
What it is
Most LMS platforms are marketplaces first and learning tools second. EduNest was built for a client who wanted the opposite — a focused, private environment where instructors control exactly who gets in. Token-based enrollment replaces the payment flow entirely, removing the need for payment infrastructure and keeping the experience clean for both instructors and students.
My role & approach
Solo client project — I handled the build end to end, from architecture through the token-based enrollment system, role-based access control, and Google OAuth integration, working directly with the client on requirements.
The entire codebase is structured around the repository pattern, keeping business logic out of controllers and making the data layer swappable. Role-based access control is enforced at the middleware level so route protection is declarative rather than scattered through individual controllers. Google SSO was added to reduce signup friction without storing passwords.
"A focused, private environment where instructors control exactly who gets in."
Stack
Impact
Deployed and live for a real client
Token enrollment removes payment infrastructure entirely
Google SSO reduced signup friction significantly
Role-based access control covering instructor, student, and admin flows