One operating system for your entire school.

Admissions, student records, academics, fees, attendance, staff, parent communication and school operations run on one connected platform — not six that have to be reconciled.

Book a demo Explore SchoolOS

Built for private schools, international schools, preschools and multi-campus groups. 36 modules are available today, and this site labels the ones that are not.

SchoolOS — administrator dashboard

The shape of the product

Numbers about the software, not about our sales.

We are a young product and will not pretend otherwise. What we can tell you is exactly what is built, and you can check every figure here on a call.

36
Modules available today: 1
Database behind all of them: 11
Roles out of the box: 100%
Of queries scoped to one school

One platform

Everything your school needs. Connected.

Schools usually buy an SIS, an accounting package and a messaging tool, then spend the year reconciling them. SchoolOS is one system on one database: the student record admissions created is the record fees invoices, the register marks and the report card is built from.

How the pieces fit together

What reads the same record

Admissions: An enquiry becomes this record without being retyped.
Students: The record itself: who they are, and every year they have been here.
Academics: Class, section, subjects and the timetable they sit in.
Attendance: Marked against the class, stored against the student.
Examinations: Marks, results and the report card computed from them.
Finance: The invoice, what has been paid, and what is outstanding.
Communication: Notices and messages addressed from these contact details.
Transport: The route and stop, and the bus the child is on this afternoon.

Nothing above is synchronised overnight. There is one row, and these are eight views of it.

Three products, one system

SIS, CRM and ERP — sold together because they are built together.

Most schools buy these separately and then pay, in staff time, for the gap between them. Inside SchoolOS they are three views of the same data rather than three databases with an import between them.

CRMBefore they join

Admissions & enrolment

Enquiries land on the system rather than in a counsellor’s notebook, and an admitted child becomes a student record without being typed a second time.

Read about admissions

Working today

Enquiries recorded against the family
New enquiries on the administrator’s dashboard
Enrolment straight into student records
Guardians created with the student, in one step

Next, and not available yet

Stages from enquiry to enrolled · Follow-ups with an owner and a date · Conversion reporting by source · Online application forms

SISWhile they are here

Student Information System

One record per student, holding what the school knows about them — and the record every other module reads rather than keeping its own copy of.

Read about student records

Working today

Admission details and guardians
Class and section history by year
Attendance, day by day and by period
Marks, results and report cards
Fees raised, paid and outstanding
Leave and absence on the same timeline
Transport route and stop
Messages exchanged with the family

Next, and not available yet

Document vault · Bulk import and year-end promotion · Certificates

ERPAround them

School operations

The office side: fees defined once and collected at the counter, staff and leave, transport with live tracking, and a dashboard that reads today’s figures.

Read about school operations

Working today

Fee structures, invoices and receipts
Outstanding by class and by family
Payments ledger with who took each one
Staff records, attendance and leave
Transport routes, buses and live tracking
Notices and messages to a class or the school
Roles, permissions and an audit trail
The school’s own domain and branding

Next, and not available yet

Library and inventory · Payroll · Report builder

Reporting

Six months of your school on one screen.

The lower half of the dashboard from the top of this page, at full size. No figure on it is typed in or carried across from a report — strength, attendance and collection are computed from the records as they stand when the page loads.

What the office does with it

SchoolOS — administrator dashboard, reporting panels

01Head count by month
Six months of enrolled strength. A class quietly shrinking is visible here long before it shows up in the fee ledger.
02Attendance against it
The line over the columns is the monthly attendance percentage, so a drift is read against the strength that produced it.
03Fee collection
Collected, pending and overdue across every invoice raised this year — one figure, not three reports that disagree.
04Today’s register
Present, absent, late and on leave as the registers come in during the morning rather than at the end of the day.

The figures shown are illustrative sample data for a school of about 1,300 students. They are not a customer’s numbers, and we will never show you another school’s.

Modules

Everything you need to run a school.

36 modules are working today, 4 are partly there, and 19 are on the roadmap. Each one below says which it is, because you will find out eventually and it may as well be now.

See the full catalogue

Classes, subjects and the timetable are the spine everything else hangs from — attendance, homework and results all resolve against them.

Classes & sections
Class and section structure per academic year, with teachers and students assigned to each.
Subjects
Subject lists per class, including electives and the teacher who takes each one.
Timetable
Period-by-period timetable per section, visible to teachers, students and parents.
Homework
Homework set per subject with due dates, visible to parents the same evening.
Classwork
A record of what was covered in each period, so a returning student can catch up.
Academic calendar
Terms, holidays and examination windows in one calendar the whole school reads.

Admissions

Every enquiry on the system from the first phone call.

Admissions is where schools lose the most information and notice it the least — a name on a notepad, a follow-up nobody owned, a family who visited twice and was never called back. SchoolOS records the enquiry today; the pipeline that works it through to enrolment is the release we are building now.

Read about admissions

What works today

The enquiry is a record, not a note: A parent who calls or walks in is recorded against the family, with the child, the class they are asking about and where the enquiry came from.
New enquiries are on the dashboard: The administrator’s first screen lists the newest enquiries, so nothing sits unseen in a counsellor’s notebook until somebody asks.
Admission creates the student: When a child joins, the student record, the enrolment and the guardians are written in one step — and the fee structure for that class applies from the same moment.

The pipeline we are building

In build

01Enquiry
02Visit
03Application
04Offer
05Enrolled

Drawn from the specification, not from the product. Stage-by-stage tracking, follow-ups with an owner and a date, counsellor assignment and conversion reporting by source are in build — we will tell you the same thing on a call, and show you the enquiry capture that does work.

Why one database matters

Aarav is entered once, in February.

Everything after that is the same record: his class list, his register, his fee invoice, his bus stop, his report card. Nobody re-types his name, and no two systems disagree about which class he is in.

1Admission
The record is created once
Admissions, February
Aarav Sharma
DIS/2026/0184
2Academics
He appears on the class list
Class 7-A · 38 students
Class 7 · A
Roll 12
Enrolled
3Attendance
His teacher marks the register
This week
MPTPWATPFL
Absent on Wednesday. His parents were told that morning.
4Fees
His invoice knows his class
Term 2 · due 15 September
Tuition — Class 7₹24,000
Transport — Route 2₹6,000
Balance₹30,000
5Transport
The bus knows his stop
Route 2 · picks up 07:25
Green Park Market
Stop 3 · BUS-02 · Vikram Singh
6Examinations
His report card writes itself
Mid-term, Class 7-A
Mathematics86A
Science79B+
English91A+

When he leaves in Class 12, the same record holds six years of attendance, results, fees and documents — without anyone having assembled it.

A Monday morning

By 9:15 you know who is missing and what is owed.

Teachers mark their registers on a phone in the classroom. The office sees the total as it fills in, not at the end of the day when someone types it up.

Fees behave the same way. A payment collected at the counter changes the outstanding figure immediately, and the receipt is already numbered.

How the office runs on it

Transport

The bus is where the school says it is.

Drivers start a trip on a phone. The office sees the fleet move, and a parent sees only their own child’s bus — with the driver’s name and number, and an arrival estimate for their stop.

The map is drawn from your own coordinates rather than a tile provider, so where your pupils stand each morning is not sent to a third party on every pan.

Routes and stops: Ordered, timed, with fares
Boarding: Marked per child, per trip
Documents: Insurance and fitness expiry
Signal loss: Flagged, not hidden

How transport works

CoveredRemainingStop done

Parents and teachers

The office stops answering the same three questions.

Was she marked present. What is the homework. How much is left to pay. Parents can see their own children and nothing else — enforced in the data layer, not by hiding a menu.

Attendance, day by day
Homework and classwork
Fee balance and receipts
Results and report cards
Notices from the school
Their child's bus, live

Teachers work from the same records, on whatever they have in hand

Registers are marked in the classroom on a phone, homework is set from the same screen, and marks are entered against their own classes and nobody else’s. Nothing is collected on paper first and typed in later.

Monday, 11 August

Good morning, Meera

Aarav Sharma

Class 7 · A

Present

Bus 02 · Route 2

Arriving Green Park Market

in about 6 minutes

Fees

Term 2 balance₹30,000

Due 15 September

Homework

Mathematics — exercise 7.2

Due tomorrow

Integrations

Connected to the things a school already uses.

Messaging and payments run through your own accounts rather than ours, so the sender is your school and the money lands in your bank. Below is what is live, what is connected during setup, and what is not built.

Integration details

Reaching parents

Every message is addressed from the records that hold the numbers, so a changed phone number is changed once.

EmailAvailable
Transactional and bulk email from the school’s own address and domain.
SMSConnected at setup
Template-based SMS through the school’s gateway account, metered per school.
WhatsAppConnected at setup
Template messages through a WhatsApp Business account the school owns.
Mobile notificationsConnected at setup
Push notifications to the parent and teacher experience on the phone.

Money

Payments reconcile against the invoice they were raised from, so collection and outstanding never disagree.

Payment gatewayConnected at setup
Online fee payment with server-created orders and signature-verified callbacks.
TallyPlanned
Export of collection and ledger data into Tally.

On campus

Hardware and location data land on the same records the office already works from.

Vehicle trackingAvailable
Live bus position on a map, per route, from the device on the vehicle.
Biometric attendancePlanned
Device-driven attendance for staff and students.
ID card & barcodePlanned
Card printing and barcode identification for library and attendance.

Identity & platform

How your school’s own systems and domain meet SchoolOS.

Custom domainAvailable
The application and the school website on a domain the school owns.
Google Workspace / Microsoft 365 sign-inPlanned
Staff signing in with the account the school already issues them.
API accessConnected at setup
A versioned HTTP API for reading and writing school data.

Available

Running in production today.

Connected at setup

Built and metered inside SchoolOS. We connect your own vendor account during implementation.

Planned

On the roadmap. Not available today, and we will say so on a call.

Solutions

Built for every type of school.

The platform is the same; what changes is which parts of it you switch on and how the year is shaped. Choose the one that describes you.

Private & K-12 schools

One campus, a long day, and an office that is asked for the same six numbers every week.

Fee structures per class, with instalments and concessions
Attendance marked by the teacher who took the period
CBSE-style examination sequence through to report cards
Notices and messages reaching a class or the whole school

Private & K-12 schools in detail

Private & K-12 schools

One campus, a long day, and an office that is asked for the same six numbers every week.

Fee structures per class, with instalments and concessions
Attendance marked by the teacher who took the period
CBSE-style examination sequence through to report cards
Notices and messages reaching a class or the whole school

Private & K-12 schools in detail

International schools

Families in several countries, a fee cycle in more than one currency, and parents who expect to look things up themselves.

Parent sign-in with their own view of each child
Documents and admission history held against the record
Communication in writing, on the record, rather than by phone
Reporting a board or trustee meeting can be given directly

International schools in detail

Preschools

Small teams, young children, and parents who want to know about the day rather than the term.

Short enrolment path from enquiry to admission
Daily attendance and pickup information for guardians
Fees on a simple structure without an examination cycle
Photographs and notices going out the same afternoon

Preschools in detail

Multi-campus groups

Several schools under one trust, each with its own staff, and a group office that needs to compare them.

Each campus separate — no staff member sees another campus by accident
The same fee heads and grading schemes rolled out across campuses
Group-level strength, attendance and collection reporting
One domain per campus, or one for the group

Multi-campus groups in detail

Why SchoolOS

What is actually different about it.

Not a list of adjectives. Each of these is a decision in the software that you can ask us to demonstrate, or that your IT team can check for themselves.

01
One database, not an integration
A fee, an absence and a result all read the same student row. There is no nightly sync between an SIS and an ERP, because there are not two systems.
02
Built for schools, not adapted from business software
Academic years, sections, terms and guardians are first-class in the data model. Nothing is a repurposed customer or invoice record.
03
Separation enforced in the data layer
Every query carries the school it belongs to. It is enforced below the screens and covered by tests that fail the build if a query could cross the boundary.
04
Permissions by role, per school
Six built-in roles and custom ones, permission by permission. A parent reaches their own children; a teacher marks their own classes.
05
Reporting from live figures
Strength, attendance, collection and outstanding are read from the records as they stand, not from an export taken last night.
06
Ready for several campuses
Each campus is its own separate system with its own staff and its own data, with group-level reporting reading across them.
07
The school’s own domain and branding
The application, its documents and the school website carry the school’s name, logo and colours on a domain the school owns.
08
An audit trail on what matters
Fee collection, result publication and permission changes are written down with the person and the time.

Security

Your school’s data deserves more than a badge on a website.

Schools hold children’s addresses, medical notes, photographs and transport stops. That is the reason for the architecture below, and the reason we are specific about it rather than reassuring.

The full security architecture

Separation between schools

Every query carries the school it belongs to, enforced in the data layer below the screens. Reading another school’s record by guessing its key returns nothing; passing another school’s id in a filter is overwritten with your own. Tests cover each of those cases and fail the build.

Sessions that can actually be revoked

Opaque session tokens with 256 bits of entropy, stored only as hashes. Not tokens that stay valid until they expire — signing a device out, or changing a password, ends those sessions immediately.

Passwords stored as bcrypt hashes

Hashed with bcrypt at cost 12, with a length-first policy. Nobody at SchoolOS can read a password, and support will never ask for one.

Brute force made expensive

Eight failed attempts lock an account for fifteen minutes, and rate limits apply per account and per address, so neither one account nor a spray across many gets far. Every attempt is recorded with its address.

Access follows the role

Permissions are checked in the service layer rather than by hiding a menu item. A parent reaches their own children; a teacher marks their own classes; the API refuses what the screen would have refused.

An audit trail on what matters

Fee collection, result publication, permission changes and administrative overrides are written down with the person and the time.

What we do not have

We hold no security certifications — no ISO 27001, no SOC 2 — and we will not imply otherwise.
Optional Postgres row-level security ships in the repository but is off by default, because switching it on without the surrounding plumbing would break queries rather than protect them.
We are happy to walk your IT team through the architecture, the isolation tests and the audit log directly.

Customer stories

What changes in the first term.

Written as problem, what we did, and what it changed — the three things a director actually wants from a case study. Schools are described rather than named until they have agreed to be.

All customer stories

A CBSE day school

Sample layout

Western India · Around 1,400 students

The problem: Fees were collected on a desktop accounting package, attendance on paper registers, and results in spreadsheets. Reconciling the three at the end of a term took the office most of a week.
What we did: Fee structures were rebuilt per class inside SchoolOS, two years of student history was migrated, and counter collection moved over at the start of a term.
What changed: Outstanding fees are now a screen rather than an exercise. This is the shape a written-up implementation takes — replace it with a real one before launch.

An international school

Sample layout

South India · Around 900 students

The problem: Parents from several countries asked for the same information by email, and the office answered each one by hand.
What we did: Parent sign-in was rolled out alongside attendance and homework, so the answer was already on the record when the question arrived.
What changed: Routine enquiries to the front office fell. Sample layout — a real figure goes here, sourced from the school.

A multi-campus group

Sample layout

Three campuses · Around 3,200 students across the group

The problem: Each campus ran its own software, so the group office could not see strength or collection without asking three people.
What we did: Each campus kept its own separate system inside SchoolOS, with group-level reporting reading across all three.
What changed: The group office reads one report. Sample layout, pending a named group’s approval.

Marked stories are layout, not history: the structure a written-up implementation will take once a school has approved theirs. We would rather show you an obvious template than an invented customer.

In their words

What we expect to hear, and will replace with what we do.

No carousel and no stock portraits. When a school approves a quotation it goes here with their name and their role, and this note disappears.

“The change we felt first was not a feature. It was that nobody had to ask the office for a number that the system already knew.”

Awaiting approvalPrincipalSample layout

“Fee collection and outstanding used to be two different answers depending on who you asked. Now there is one, and it is current.”

Awaiting approvalHead of accountsSample layout

“Marking attendance takes the first minute of the period, and the parents who need to know have been told before the second one.”

Awaiting approvalClass teacherSample layout

Implementation

Getting started with SchoolOS is a term’s work, not a year’s.

A single-campus school of a thousand students is usually live in about four weeks. Migration is the part that takes the time, and we reconcile the totals with your office before anybody signs in.

Implementation and support

Week 1
01Discovery
We go through how your school runs today — what is on paper, what is in spreadsheets, what your current software does badly. Half a day, usually with the principal and the head of accounts.
Weeks 1–2
02Configuration
Classes, sections, subjects, fee heads, grading schemes, roles and branding are set up as your school actually uses them, not as a default template.
Weeks 2–3
03Data migration
Student records, guardians, fee history and staff are brought across from whatever holds them now. We reconcile the totals with your office before anyone signs in.
Weeks 3–4
04Training
Separate sessions for the office, for teachers and for whoever will administer the system. Short, on your own data, and recorded so a new joiner can watch them.
Week 4
05Launch
Attendance and fees go live at a term boundary wherever possible. Parent sign-in is opened once the office is comfortable, not on the same day.
Ongoing
06Support
A named contact for the first term, then ongoing support. Every release is applied for you; there is nothing for your IT team to install.

Next step

Ready to run your school on one platform?

Tell us how your school runs today — what is on paper, what is in spreadsheets, what your current software does badly. The demonstration follows that rather than a script, and we will be straightforward about the modules that are not built yet.

Book a demo Talk to our team

What a demonstration involves

Thirty to forty minutes, on a call, with your screen or ours
Roughly how many students and staff you have
What you use today for fees and attendance
Whether you run one campus or several

No obligation, and no pricing pressure on the first call. If SchoolOS is the wrong fit for your school we would rather say so then.

One operating system for your entire school.

Numbers about the software, not about our sales.

Everything your school needs. Connected.

SIS, CRM and ERP — sold together because they are built together.

Admissions & enrolment

Student Information System

School operations

Six months of your school on one screen.

Everything you need to run a school.

Classes & sections

Subjects

Timetable

Homework

Classwork

Academic calendar

Every enquiry on the system from the first phone call.

Aarav is entered once, in February.

The record is created once

He appears on the class list

His teacher marks the register

His invoice knows his class

The bus knows his stop

His report card writes itself

By 9:15 you know who is missing and what is owed.

The bus is where the school says it is.

The office stops answering the same three questions.

Teachers work from the same records, on whatever they have in hand

Connected to the things a school already uses.

Reaching parents

Money

On campus

Identity & platform

Built for every type of school.

Private & K-12 schools

Private & K-12 schools

International schools

Preschools

Multi-campus groups

What is actually different about it.

One database, not an integration

Built for schools, not adapted from business software

Separation enforced in the data layer

Permissions by role, per school

Reporting from live figures

Ready for several campuses

The school’s own domain and branding

An audit trail on what matters

Your school’s data deserves more than a badge on a website.

Separation between schools

Sessions that can actually be revoked

Passwords stored as bcrypt hashes

Brute force made expensive

Access follows the role

An audit trail on what matters

What we do not have

What changes in the first term.

A CBSE day school

An international school

A multi-campus group

What we expect to hear, and will replace with what we do.

Getting started with SchoolOS is a term’s work, not a year’s.

01Discovery

02Configuration

03Data migration

04Training

05Launch

06Support

Ready to run your school on one platform?

What a demonstration involves