Case Study
TakshivaSchool ERP
A multi-tenant school ERP built for Indian schools and colleges, from the admission enquiry to the report card.
- Industry
- Education
- Services
- erp development, mobile app development
- Platforms
- Web (PWA) · Android
- Modules
- 54Modules
- Database tables
- 161Database tables
- Data importers
- 13Data importers
- Role-based portals
- 7Role-based portals
1. Project Overview
Most Indian schools run on a fee register in one tool, a WhatsApp group for parents and a spreadsheet for marks. Principals cannot see dues, attendance and results in one place, and every board exam season means rebuilding reports by hand.
Takshiva puts the whole school on one system. Each school gets its own subdomain and its own data. Admins, principals, accountants, teachers, staff, parents, students and bus drivers each see a screen made for their job.
At a Glance
- Client
- Own product
- Product
- School ERP SaaS
- Platforms
- Web (PWA), Android
- Live since
- 3 August 2026
- Live at
- takshiva.com
2. The Challenge
- Different grading rules for CBSE, ICSE and state boards, plus the new NEP 2020 holistic progress card.
- Government data returns such as UDISE+, which schools usually type in by hand.
- Fee structures that vary by class, route and concession, with dues that parents dispute.
- Schools moving over from old software with years of student records.
- Parents who want updates on their phone, not on a printed circular.
3. What We Built
- Academics: admissions CRM with a public apply form, attendance in school or college mode, timetable, exams, online exams, a question paper builder and result analytics.
- Grading presets for CBSE 8-point, ICSE and state boards, and an NEP 2020 holistic progress card.
- Finance: fee structures, a fee collection desk, dues tracking, accounting with Tally export, payroll and salary payments.
- Operations: transport with GPS tracking and a driver trip screen, hostel, library, inventory, medical room and visitor log.
- Communication: notices, events, a PTM scheduler, grievances, chat and an early-warning list for at-risk students.
- Documents: certificates, a document vault and ID cards in 7 designs.
- A migration toolkit with 13 importers to bring records over from other systems.
4. How It Works
Laravel 12 serves the API with token auth, and the web app runs as a PWA so staff can pin it to a phone home screen. Each school lives in its own tenant, reached through its own subdomain. The live servers run MySQL 8 and PHP 8.3 on Ubuntu 24.04 behind nginx.
For Indian compliance, the system exports UDISE+ data, stores the APAAR ID with recorded consent and keeps a consent register under the DPDP Act. Fee and accounting entries export to Tally, which most school accountants already use.
A Flutter parent app for Android gives parents one view of every child linked to their account. Role access is checked on the server and covered by its own automated test gate.
5. The Outcome
Takshiva has been live at takshiva.com since 3 August 2026, with the API on its own subdomain. Schools reach it through their own subdomain, and parents use the Android app or the installable web app.
The product now spans 54 modules on 161 database tables. Each major area carries its own automated test gate; the role access gate alone runs 207 checks, and the parent portal gate runs 221. Teacher and student apps for Android have also been built on the same API.
- Modules
- 54Modules
- Database tables
- 161Database tables
- Data importers
- 13Data importers
- Role-based portals
- 7Role-based portals
- Live at takshiva.com
- Aug 2026Live at takshiva.com
Technologies Used
- Laravel 12
- Next.js 14
- Flutter
- MySQL 8
- PHP 8.3
- nginx + PM2
- Ubuntu 24.04
Have a Similar Challenge?
Let’s build a solution that drives real results for your business.