EdSeer
The complete school ERP, live - the academic core is live, pilot onboarding is open, and the wider ERP modules keep releasing on a published plan: academics, people, money, assets, logistics and communication for schools and multi-branch groups, with every organisation on its own fully isolated tenant and Ask Seer, a permission-scoped AI assistant, designed in.
Inside the product
See it, not slideware
Real captures, never staged for this site - each caption says exactly what you are looking at.
Overview
EdSeer is a live, multi-tenant school ERP, designed to be the only platform a school - or a multi-branch school group - needs. Its architecture makes one promise before any feature: every organisation gets a fully isolated tenant, with its own database and its own subdomain, on one shared application that is patched and improved centrally; inside the tenant, any number of branches run with branch-scoped isolation and group-level consolidation. The full scope is a genuine ERP: student and guardian records, admissions, staff HR and payroll, fees with online payment, academic structure and calendars, syllabus and booklists, attendance including ID-card and biometric devices, timetables, exams and report cards, homework, library, hostel, inventory and school stores, preferred-partner vendors with parent discounts, procurement, transport with live GPS bus tracking, and controlled school-to-home communication - on the web and on Android and iOS apps. Ask Seer, the built-in AI assistant, answers questions for teachers, parents and students strictly within what each of them is permitted to see. The academic core landed first - 197 automated suites green - and the platform is live with pilot onboarding open; the wider ERP modules keep releasing on the same spine in a published, sequenced release plan, opened by the multi-branch Org module.
The business problem
A school's administration is scattered across a dozen disconnected tools: an admissions register here, fee software there, attendance on paper, payroll in spreadsheets, the bus roster on a whiteboard and parent communication on personal messaging apps. Every boundary between tools is a reconciliation job, and multi-branch groups multiply every one of them. Existing school software often puts every school in one shared database, sells every feature in one licence tier, and stops at academics - leaving finance, HR, stores and transport to be stitched on. A school deserves real isolation, a scope that covers the whole institution, and the freedom to switch on only the modules it needs.
Who it is for
- Schools and multi-branch school groups
- Principals and group management needing consolidated visibility
- Administrators, office staff, accountants and HR
- Teachers and class coordinators
- Parents and students, on the portal and mobile apps
Capabilities
Key features
One fully isolated tenant per organisation - own database, own subdomain, centrally patched application - with any number of branches inside it, branch-scoped isolation and group-level consolidated dashboards
Student information system - students, guardians, sibling handling, document checklists, a permission-gated medical record and a single student 360 view
Admissions pipeline - enquiry to application, assessment, offer and one-click enrolment, plus template-driven certificates with verification codes
Staff, HR and payroll - employment contracts, leave management, salary structures, monthly payroll runs with payslips, and statutory outputs including WPS files and gratuity
Fees and finance - fee structures with sibling policies, invoicing, concessions and scholarships with approval workflows, cashier screens, online fee payment on the parent portal and apps, ledgers and collection reports
Attendance - daily and period marking, manual or via ID-card and biometric devices, with a correction workflow and lock dates
Academics end to end - years, terms and calendars, timetable builder with clash detection and substitutions, syllabus and curriculum plans, and grade/subject booklists with full book details
Exams and report cards - grading schemes, marks entry with moderation and locks, report cards published to the portal and apps; plus homework and assignments with submissions
Library, hostel, inventory and school stores for stationery and uniforms - with procurement (vendors, purchase orders, contracts) behind them
Preferred partners - approved bookshops and uniform vendors with negotiated parent discounts, booklist buy-links and offer redemption tracking
Transport with live GPS bus tracking - routes, stops, student assignment and trips
Ask Seer - the built-in AI assistant: teachers, parents and students ask about homework, announcements, holidays, books, syllabus or fees, and answers are strictly scoped to what that user is permitted to see
Platform discipline throughout - configurable role-based access with data scopes, dashboards, a broad report catalogue, notifications with delivery windows, audit trails and import/export
Benefits
- One platform replaces the tool sprawl - people, academics, money, assets and logistics on one spine, one permission model, one audit trail
- The organisation's data genuinely isolated - not one row-filter away from another school's
- Multi-branch groups get branch autonomy and group consolidation from the same system, including student and staff transfers between branches
- Parents get one app for fees, homework, report cards, the bus and school messages - not five
- Module entitlements are per-tenant, so a small school runs just records, attendance and communication while a group switches on everything
- An office that runs on workflows instead of registers - captured once, reported everywhere
Integrations
- Online fee payment through a payment-gateway adapter seam
- Single sign-on with Google and Microsoft accounts alongside local login
- ID-card, biometric attendance and GPS device event ingestion
- Email, in-app, web push and mobile push notifications with delivery windows
- CSV import with validation preview and rollback, plus export throughout - existing records come across, not get re-typed
- Booklist ISBN import feeding the library and partner buy-links
Deployment options
- Managed cloud (SaaS) - one isolated tenant per organisation, operated by PASDACS
- Web app plus Android and iOS apps for parents, students and staff
- Per-tenant module entitlements - switch on only what the school needs
Security
Isolation is the security model: each organisation runs on its own database with its own subdomain, so no query can cross tenants by construction, and branch scoping confines access inside the tenant. Role-based access carries data scopes - a class teacher sees their class, a parent sees only their own children - and sensitive records such as student medical data sit behind dedicated permissions with every access audited. Sign-in uses server-side sessions with instant revocation, TOTP two-factor authentication and strict SSO account linking; audit trails are written in the same transaction as the change they record; and Ask Seer is designed to answer only from what the asking user is permitted to see, with a local-model option so schools can keep AI inference off third-party services. These commitments are built into the live academic core and carried through every ERP release.
How it compares
Others vs us, feature by feature
"Others" below means typical school-management software as commonly sold today, described fairly. EdSeer is live on its academic core, with the wider ERP releasing on a published plan - so every "we" row is explicit about whether it is available today or a design commitment on that plan.
| Feature | Others - typical tools | We - EdSeer |
|---|---|---|
| Tenancy & isolation | Every school in one shared database, separated by a tenant column and hope. | One isolated database and subdomain per organisation - cross-tenant queries impossible by construction, proven by a provisioning test. Available today. |
| Scope | Academics only; finance, HR, stores and transport are other vendors' problems, stitched together by the office. | 39 modules on one spine - academics, people, money, assets, logistics and communication. Academic core available today; the rest in build on a published plan. |
| Licensing | One licence tier - a small school pays for the payroll module it never opens. | Per-tenant module entitlements: switch on only what the school needs; a disabled module keeps its data and disappears from the UI. Available today. |
| Upgrades | Big-bang upgrades: every school down together, and a failed migration is everyone's outage. | Ring-based per-tenant rollouts with expand/contract migrations - a failed migration pauses one tenant behind a maintenance page while every other school is untouched. Available today. |
| Audit | An activity log written after the fact, if at all - and never for reads. | Audit written in the same transaction as the change - old and new values, actor, IP - including permission denials and reads of sensitive data. Available today. |
| Permissions | A handful of hard-coded roles; "class teacher sees their class" is a training instruction. | Role permissions carry data scopes (school, grade, assigned class, own children, own), enforced by query-level guards - an architecture test fails the build if a scoped entity is queried unscoped. Available today. |
| Sessions & sign-in | Long-lived tokens that cannot be revoked; SSO auto-creates mystery accounts. | Server-side sessions with instant revocation, TOTP two-factor, phone+OTP as a first factor, and strict SSO account linking with no auto-provisioning. Available today. |
| AI | A chatbot with database access and a prayer. | Ask Seer (planned) executes every answer as the asking user through the same permission pipeline as the REST API, with a local-model option - designed in, stated honestly as not yet built. |
| Multi-branch groups | One install per branch; consolidation happens in Excel at month-end. | Branches are first-class inside one tenant: branch-scoped roles, per-branch branding, group dashboards and audited transfers. The Org module is already live as the ERP track's opener. |
| India readiness | A localisation patch on software designed elsewhere. | India-first by decision: boards and NEP-2020 assessment, statutory payroll, DPDP Act, UPI-first payments and regional languages in the PRD - with a country-pack seam for international schools. Design commitment on the plan. |
Tenancy & isolation
Others: Every school in one shared database, separated by a tenant column and hope.
We: One isolated database and subdomain per organisation - cross-tenant queries impossible by construction, proven by a provisioning test. Available today.
Scope
Others: Academics only; finance, HR, stores and transport are other vendors' problems, stitched together by the office.
We: 39 modules on one spine - academics, people, money, assets, logistics and communication. Academic core available today; the rest in build on a published plan.
Licensing
Others: One licence tier - a small school pays for the payroll module it never opens.
We: Per-tenant module entitlements: switch on only what the school needs; a disabled module keeps its data and disappears from the UI. Available today.
Upgrades
Others: Big-bang upgrades: every school down together, and a failed migration is everyone's outage.
We: Ring-based per-tenant rollouts with expand/contract migrations - a failed migration pauses one tenant behind a maintenance page while every other school is untouched. Available today.
Audit
Others: An activity log written after the fact, if at all - and never for reads.
We: Audit written in the same transaction as the change - old and new values, actor, IP - including permission denials and reads of sensitive data. Available today.
Permissions
Others: A handful of hard-coded roles; "class teacher sees their class" is a training instruction.
We: Role permissions carry data scopes (school, grade, assigned class, own children, own), enforced by query-level guards - an architecture test fails the build if a scoped entity is queried unscoped. Available today.
Sessions & sign-in
Others: Long-lived tokens that cannot be revoked; SSO auto-creates mystery accounts.
We: Server-side sessions with instant revocation, TOTP two-factor, phone+OTP as a first factor, and strict SSO account linking with no auto-provisioning. Available today.
AI
Others: A chatbot with database access and a prayer.
We: Ask Seer (planned) executes every answer as the asking user through the same permission pipeline as the REST API, with a local-model option - designed in, stated honestly as not yet built.
Multi-branch groups
Others: One install per branch; consolidation happens in Excel at month-end.
We: Branches are first-class inside one tenant: branch-scoped roles, per-branch branding, group dashboards and audited transfers. The Org module is already live as the ERP track's opener.
India readiness
Others: A localisation patch on software designed elsewhere.
We: India-first by decision: boards and NEP-2020 assessment, statutory payroll, DPDP Act, UPI-first payments and regional languages in the PRD - with a country-pack seam for international schools. Design commitment on the plan.
Getting started
Implementation & pricing
Implementation timeline
Live and onboarding, in the open about its stage: the academic-core platform is complete (August 2026) - 52 work packages covering the multi-tenant foundation, students and guardians, teachers, attendance, communication, dashboards, a 40-report catalogue, audit and imports, with 197 automated suites green. The wider ERP track is under way: the multi-branch Org module landed first, with HR and payroll, finance and fees, admissions, exams and timetables, campus operations and mobile apps following in a published, sequenced release plan. Onboarding is guided: your academic structure, calendars and records are set up with you, with CSV import bringing existing data across - weeks, not months.
Pricing
Offered as a managed subscription (SaaS). Module entitlements are per-tenant by design, so plans are sized to the school - a small school runs just the academic core while a group switches on everything as it releases. No public price list yet; pilot institutions get pilot terms and help shape the commercial model - talk to us.
FAQ
Frequently asked questions
See it working against your own use cases
Talk to our team about your processes and we will show you how the platform fits.