NexSchool Knowledge Base
One place to understand the whole product — without reading ~200k lines of code across six repositories.
NexSchool is a multi-tenant School ERP SaaS. A “tenant” is a school: isolated data, its own subdomain, a subscription plan, and role-based access control for its staff. The platform is operated by a super-admin from a separate control panel.
This knowledge base is the single source of truth. It supersedes the previously scattered docs (docs/, docs-new/, server/docs/, admin-web/docs/, the old Docusaurus site). If something here disagrees with an old doc, this wins.
Start here
| If you want to know… | Go to |
|---|---|
| Why this product exists, where it’s going | Business → Vision, Roadmap |
| What a feature does for a school | Product (one page per domain) |
| How the system is built | Architecture → Overview |
| Why a key technical choice was made | Decisions (ADRs) |
| What a term means | Glossary |
The four repos that make the product
| Repo | Role |
|---|---|
nexchool/server | Flask REST API, business logic, PostgreSQL, Celery |
nexchool/school-admin-panel (admin-web) | Next.js dashboard used inside a school |
nexchool/super-admin-panel (panel) | Next.js control plane used by NexSchool operators |
nexchool/client | Expo React Native app for teachers, students, admins |
nexchool/nexchool-infra | Docker Compose, Nginx, CI/CD, deploy |
nexchool/landing-page | Marketing site (nexchool.in, Vercel-hosted) |
How this knowledge base is sourced
- Product / Architecture / Decisions / Glossary — written from the codebase and the maintained technical docs. Treat as accurate.
- Business → Vision / Roadmap — synthesised from the product roadmap and shipped state.
- Competitors and Jira (epics/stories) — scaffolds. They contain structure and prompts, not invented facts. Fill them from real market research and your issue tracker.
Scaffold pages are clearly marked with a callout at the top. Don’t cite them as fact until filled.