multi-tenant school management SaaS · EdTech / School management SaaS

Nuxused

A multi-tenant school-management SaaS — platform control plane, per-school portals and one Flutter app for parents, teachers and students.

nuxused.com ↗

Problem

Schools each want their own system and nobody wants to run one. Selling school management as SaaS moves the hard problems up a level: provision a new school without touching a server, keep one school's data provably invisible to another, and handle the reality that subscriptions lapse — without cutting a school off from its own records or letting an unpaid tenant keep writing. And the same domain has to be right for three very different audiences at once — a platform operator thinking in tenants and dunning, a school admin thinking in sections and payroll, and a parent thinking about one child's attendance and one bill.

Solution

NestJS services over PostgreSQL, with Redis for caching and background work, containerised with Docker behind Nginx on AWS EC2. Two distinct web surfaces sit on one API — a platform control plane (tenants, schools, franchises, subscriptions, invoices, payments, plans, roles, audit logs, service health) and the per-school portal — plus a Flutter client that serves parents, teachers and students from one codebase, routed by role at sign-in. Subscription state is a first-class platform concern: an expired school drops into read-only mode, with writes disabled, its own data still fully readable and renewal one click away. School provisioning is an instrumented async pipeline with a transactional outbox, so partial failures surface as real operational signals instead of vanishing into a log file.

Key features

• Multi-tenant architecture with per-school data isolation
• Platform control plane: tenants, subscriptions, invoices, payments, plans, audit logs
• Subscription lifecycle (active → expiring → expired → suspended) with read-only enforcement
• Instrumented school-provisioning pipeline with a transactional outbox
• Per-school portal: academic sessions, classes, sections, timetable, grading, fees, payroll
• One Flutter app, three products: parent multi-child view, teacher one-tap attendance, student

Technology

Results

• New schools provisioned as SaaS tenants without server work
• The commercial model (subscriptions / dunning) is enforced at the platform layer, not per feature
• Silent partial failures made visible — provisioning, outbox and auth-setup retries all surfaced