Inspiration

Education organizations still run their daily work across disconnected systems: spreadsheets for administration, separate tools for classes and communication, fragmented content libraries, and generic AI that cannot be trusted with learner-facing answers.

EduOS is our response: a single operating system for schools, coaching institutes, universities, tutors, and enterprise learning teams. It treats learning operations and AI safety as one product problem.

What it does

EduOS gives an organization one place to set up its learning environment, manage people and permissions, create courses and batches, organize approved learning material, run classroom workflows, and understand learner progress.

At the center is a grounded AI Tutor. It is designed to answer only from an organization’s approved course material, provide source citations, and refuse briefly when the right context is unavailable. This makes AI useful in education without turning it into an unverified answer engine.

The current demo shows organization onboarding and launch readiness, permission-aware people and access workflows, course creation, an AI Tutor workspace with an approved-content policy, and live-class and analytics product surfaces.

How we built it

EduOS is a TypeScript monorepo. The web experience uses Next.js, React, Tailwind CSS, and shared UI primitives. The API is structured as a NestJS service with modules for authentication, organizations, users, courses, and AI policy behavior. Shared types and SDK boundaries keep the frontend and backend aligned; the AI worker provides the foundation for material ingestion and generation jobs.

We designed the product around multi-tenancy and permission-first access from the beginning. The AI Tutor’s grounding policy is a core product rule rather than a future safety patch.

How Codex helped

Codex accelerated the project from initial repository setup through a runnable product demonstration. It helped establish the monorepo architecture, implement shared TypeScript contracts, build the dashboard and core workflows, refine responsive layouts, resolve runtime module issues, validate with typecheck, lint, tests, and builds, and shape the README and product vision experience.

What is next

The next implementation phase adds database-backed organizations, users, memberships, roles, permissions, courses, lessons, and resources. From there, EduOS will add material upload, retrieval-augmented answers with citations, live classroom integrations, assignments, assessment, attendance, and analytics that suggest the next best support for each learner.

Built With

Share this project:

Updates