Multi-Tenant School SaaS API

I need a production-ready backend that powers a multi-tenant School Management SaaS. The stack is fixed—ASP.NET Core 8 Web API with EF Core and SQL Server—so you should be completely comfortable designing clean, modular code in that environment.

Core scope
• Build the entire API layer only; no front-end work.
• Architect true multi-tenancy from day one, separating data per school while keeping shared services efficient.
• Implement rock-solid authentication and authorization, plus fine-grained role-based access control. Day-to-day users include Students, Teachers, Parents, School Admins, Platform Admins and other school-specific roles, so permissions must be both flexible and secure.
• Model every major domain: school setup/configuration, student/parent/teacher records, enrollments, academics, timetables, planning, attendance, assignments, exams, marks, notifications and audit logs.

Notifications
Assignments & exams, attendance and general announcements all need real-time or near-real-time notifications. I’d also like the system architected so other features can easily hook into the same notification pipeline later.

What I’m looking for in your reply
– Examples of SaaS or large-scale API backends you have built, preferably with multi-tenant experience.
– A high-level architecture outline (tenant isolation strategy, RBAC approach, suggested use of EF Core features, caching, logging, etc.).
– Estimated timeline with major milestones.
– Cost estimate broken down by milestone or phase.
– Your team composition or, if you’re solo, the role you will personally cover.

Quality and maintainability are more important than rushing, but I do expect production-grade practices: unit/integration tests, well-structured repositories, sensible domain boundaries, secure secrets management and performance considerations from the outset.

If this sounds like a fit, let’s talk details. Show More