Skip to main content

EdTech software development company for schools and coaching centres

We are an EdTech software development company that builds school management systems, parent apps, online exams and learning platforms for schools, coaching centres and EdTech teams. It all runs in your own accounts, your staff run it day to day without us, and you keep the code. One exam platform we built has run for a coaching institute since June 2026, and a teacher approves every grade it drafts.

Projects from US$4,000. Developers at US$12-40 an hour, or from US$2,000 a month full time.

Talk through your learning platform(opens in a new tab)See our education work
  • Admissions to report cards
  • Exams marked on submission
  • Runs in your own accounts

2017

Shipping software since

Same owners, same team

Web + app

Staff workspace and parent app

Android and iOS, built by the same team

100%

IP ownership

Your repository and accounts from the first commit

1 day

Reply time

One working day, every enquiry

Proof

Education work you can read about

What we have built in this sector, where each piece stands today, and the full account of it.

Live with a client

A computer-delivered exam platform

Running for IELTS Builder Canada since June 2026. 4,584 submissions in a thirty-day window, with nothing waiting to be marked.

A coaching institute’s own mock exams, sat on screen in the format students now face. Reading and Listening are marked the moment a student submits. For Writing and Speaking the model drafts a band and feedback, and a teacher approves or edits every one before the student sees it. Spoken answers are transcribed on the institute’s own server, and their staff add new mocks themselves, without us.

Read the case study →The self-hosted speech to text behind it →

4,584

module submissions in a thirty-day window

Running since
June 2026
Mocks moved off paper
200+
Who publishes a grade
A teacher, every time
Recordings sent to an AI vendor
None
Live with a client

How its speech pipeline keeps recordings

The same platform, written up for engineers: why the transcription runs on the institute’s own server and what that costs.

Read the write-up →
Built and ready for a school

Our own school management product

Built in-house with a parent app for Android and iOS. Finished, and ready to run in a school’s own accounts.

What slows schools down

Where education software usually fails

A school, a coaching centre and an EdTech team have different budgets and the same four problems. None of them is about the software being old. They are about the records not agreeing, the families not hearing, and someone else holding the data.

The office runs on registers and spreadsheets

Attendance in one book, fees in a ledger, timetables in a spreadsheet and notices in a chat group. None of them agree, and someone spends the end of every month making them.

Parents hear last

Homework, leave, fee reminders and holiday notices reach families through five channels, or not at all. Often the first a parent hears of a problem is the report card.

Practice is rationed by marking

Every mock marked by hand means realistic practice happens when a teacher has time, not when a student needs it. And many exams now run on a computer, so paper practice no longer matches the real thing. One coaching institute moved 200 mocks off paper when theirs did.

Off-the-shelf software owns your data

A per-student licence, the vendor’s hosting and the vendor’s roadmap. A report in your own format waits for their next release, and student records and recordings sit on servers you cannot inspect.

What we build

Education software, built in your accounts

Four kinds of build for schools, coaching centres and EdTech teams. Where we have done it before, the paragraph links to the proof.

01

School management system development

Our school management system development starts with the record: students, guardians and staff, classes and timetables, attendance and leave, fees and notices, kept in one record instead of five. Built as a web application in your own accounts, for a single school or for several branches under one head office. Moving off an older system first? That is a modernisation job and we plan the data move before anything else.

Tech Stack:

  • Node.js
  • TypeScript
  • React
  • MongoDB
  • AWS

Key Features:

  • One record per student, from admission to exit
  • Timetables that catch teacher and room clashes
  • Attendance and leave in the same place
  • Fee structures, instalments and balances
  • Notices by school, class or student
  • Access scoped by branch, class and role
02

Parent and student apps

The part families actually use: one login per family, switch between children, and see the timetable, homework, notices and fee position from a phone. Built as mobile apps for Android and iOS, usually by Flutter developers or React Native developers working alongside the web team, so the app and the office system share one set of data.

Tech Stack:

  • Flutter
  • React Native
  • Firebase
  • Node.js

Key Features:

  • One family login, several children
  • Homework and notices per child
  • Leave applied for from the phone
  • Light and dark appearance
  • Push notices where the device allows
  • Published to both app stores in your name
03

Online exams and mock tests

Exams sat on screen in the format students will face, built on your own question bank. Objective sections are marked the moment a student submits, and written or spoken answers get feedback a teacher approves first. We run one for a coaching institute: 4,584 submissions in thirty days with nothing waiting to be marked.

Tech Stack:

  • Node.js
  • React
  • MongoDB
  • Redis

Key Features:

  • Your own questions, not a vendor’s bank
  • Timed sections in the real exam format
  • Objective answers marked on submit
  • Teacher review before any grade is shown
  • A whole class sits by exam code
  • Every attempt kept for comparison
04

Learning platforms and apps

Courses, lessons, video and reading material organised by subject, with progress per student. For younger learners it is often an app first: we built Kokozi, an IoT learning platform, and BrightNest, a painting app for children. Student dashboards are their own design problem and we treat them as one.

Tech Stack:

  • Next.js
  • Node.js
  • Flutter
  • AWS

Key Features:

  • Courses organised by subject and topic
  • Video and reading material together
  • Progress per student and per class
  • Designed for the age using it
  • Works on the devices a school has
  • Content your staff can update
Where AI sits

The model drafts. A teacher decides.

AI where it saves a teacher time, with a person between the model and the student every time.

A grade is not a thing to be confidently wrong about.

So the model never publishes one. It drafts feedback on written and spoken work, a teacher reads it, and where they disagree they correct it or replace it. The teacher reads a draft instead of starting from a blank page, which is where the time is saved, and the judgement stays with the person qualified to make it. It is the same rule we use anywhere a model does something that cannot be taken back: let it draft, never let it send.

Where students are recorded, the speech models can run on your own server, so a recording is never handed to an AI vendor. How that pipeline is built, and what it costs, is written up in full, and it is running today on a coaching institute’s exam platform.

  • Drafted feedback, published by a teacher

    The model drafts feedback on written and spoken work. A teacher reads it, corrects it, and only then does a student see it.

  • Speech on your own server

    Transcription and a practice voice can run on your own machine, so a student’s recording is never handed to an AI vendor.

  • Practice without booking a person

    Spoken practice a student can do on a Tuesday evening, with a teacher reviewing the result the next morning.

  • A provider you can change

    Which model does the work is a setting, not a rebuild. One that gets worse or dearer is swapped the same afternoon.

Illustration. Names and scores are invented.

How we work

Yours to run, and ours to be honest about

Four things that are true of every engagement here, each of which you can check by asking.

It runs in your accounts

The system runs on your hosting, with your content and your students, and your staff run it day to day without us. A school whose records live inside a vendor’s product has swapped one dependency for another. You keep the source code.

Student data stays where you put it

"Where do the recordings go?" should be answerable in one sentence by anyone holding them, and often it is not. Records sit in your own storage under your own access rules, and we follow the data protection law that applies where you operate.

Usable on the hardware students have

Built against WCAG 2.1 AA for keyboard and screen-reader use, and tested on the low-end machines and older phones a school and its families actually use.

Learning standards built to the published spec

LTI 1.3, SCORM and xAPI with a Learning Record Store each follow a published specification. We build to it, test against the reference test suites where they exist, and document the setup at handover. AI proctoring, where a school wants it, only flags, and a person reviews every flag before anything happens to a student.

The stack

What it is built with

The technologies we build education software with, from the exam platform to the parent app.

  • Node.js
  • TypeScript
  • React
  • Next.js
  • MongoDB
  • Flutter
  • React Native
  • AWS
  • Whisper (self-hosted)
What it costs

Published, not quoted on the call

In USD. Hourly and monthly rates move with the stack and the seniority, from a junior on routine work to a senior on complex builds. Nothing is quoted outside them, and if the number does not work for you, you have saved yourself a meeting.

An education build starts at
US$4,000
Scoped once, with the lines shown.
Short pieces of work
US$12-40 an hour
By seniority and the work.
A developer by the month
From US$2,000 a month
Month to month, a month’s notice either way.
Agency sprint
US$2,000 per two-week sprint
Under your brand, invoiced after you see the work.

Every price on one page →

Bring in the team

Hire developers for your education project

Whether it is a school management build, a parent app or an exam platform, you can take the whole project or hire the people and run it yourself. They work in your tools, under your management, at the rate published on this site.

US$12-40 an hour depending on the stack, or from US$2,000 a month for a dedicated developer. Shortlisted profiles within two working days, and whoever you pick starts within one to two weeks.

Before you call

What schools ask an EdTech software development company

What schools, coaching centres and EdTech teams ask before they commission education software from us.

One system for students and guardians, staff, classes and timetables, attendance and leave, fees and notices, with a parent app for Android and iOS. We have built our own school management product in-house, so the hard parts, such as timetable clashes, leave that updates attendance, and parents with children at different branches, are already worked out rather than discovered on your project.

Not answered here?

Work we’ve delivered

Case studyIELTS Builder Canada: 200 mocks off paper, onto the format students now sitRead the case studyProjectKokozi Smart IoT Learning Platformfor KokoziMQTT · React · NestJS · TypeScriptView the projectProjectBrightNest-Learning & PaintingFlutter · Dart · Firebase · Android appView the projectDesign projectNorth Spring School Student Dashboard UI DesignFigmaView the project

Running a school or a coaching centre?

Twenty minutes with the person who would build it. You will get a straight answer on what is running today, what is built and ready for a school, and what would be a new build.

Talk through your learning platform(opens in a new tab)Send your EdTech brief