Make organization scope part of every protected query
Tenant identity and role checks are applied at server boundaries so client state cannot broaden access to academic or financial records.
A multi-tenant operations platform for coaching institutes that connects academic structure, people, attendance, finance, biometric devices, and SMS workflows.
Coaching institutes often split student records, class structures, attendance devices, fee collection, expenses, and communication across disconnected tools. Operators need one system without allowing one organization to see or mutate another organization’s data.
Every academic and financial workflow must preserve organization isolation and granular role permissions.
Students and teachers share physical biometric devices even though they have different domain records and responsibilities.
Payments and other critical business records require audit history and recoverable soft deletion rather than destructive removal.
Bangla SMS campaigns and attendance alerts must respect provider limits, scheduling, batching, and delivery state.
Next.js App Router combines server-rendered reads with interactive client workflows, Prisma models PostgreSQL tenancy and audit state, Supabase provides database and identity infrastructure, and adapter boundaries isolate biometric devices and SMS providers.
Next.js server and client components, shadcn/ui, TanStack Table, forms, and optimistic operational workflows.
Organizations, roles, levels, subjects, class sections, enrollments, attendance, fees, payments, expenses, and audit records.
Prisma over PostgreSQL with Supabase-backed authentication, indexed tenant queries, and soft-delete history.
Vendor adapters normalize biometric devices while encrypted credentials, scheduled polling, SMS queues, and provider clients stay behind server boundaries.
Tenant identity and role checks are applied at server boundaries so client state cannot broaden access to academic or financial records.
Steller and Tipsoi integrations implement one internal device contract, allowing attendance workflows to remain stable when hardware protocols differ.
Students, teachers, payments, and related business records retain deletion reasons and history instead of disappearing through irreversible mutations.
Server Components handle initial data and access boundaries while TanStack Query supports high-interaction screens without turning the whole application into client state.
Share your challenge, scope, and timeline to start a focused conversation.