School Techy
School Techy
Modules
AdmissionsStudent InformationFees & FinanceAttendanceExaminationsTimetableTransportHostelLibraryHR & Payroll
Solutions
Colleges Universities Coaching institutes Mobile app Integrations
Company
Pricing All features About Case studies Security Resources Blog Partners Contact Sign in
Start free trial
About us

Manage better. Teach better.

A school management system built around one belief: the software should absorb the administrative work so the people can spend their attention on the children. Everything on this page is the practical consequence of that.

Built in India, for Indian schools, boards and regulations
The School Techy dashboard
What we work on Schools Multi-campus groups Colleges Coaching institutes Residential campuses
Why

Schools do not lack software. They lack one version of the truth.

Walk into most school offices and you will find an admission register, a receipt book, a parallel Excel that reconciles the receipt book, per-teacher mark sheets, Tally, and a WhatsApp group per class. Nothing is broken. But the outstanding fee figure is a question somebody has to go and work out, the report cards take a fortnight to format, and the same child’s details have been typed in four times.

  • 01 The cost is attention, not licences An afternoon spent reconciling three numbers that should have been one is an afternoon the office did not spend on a parent or a child. That is the cost we are trying to remove.
  • 02 So we built one record, not a suite A student is entered once. Fees, attendance, marks, transport, hostel and library all read that same row. Nothing is re-keyed, so nothing can disagree.
  • 03 And a real ledger underneath Printing a receipt is easy. Producing a trial balance a year later that ties to those receipts is the hard part, and it is the part an auditor asks about — so the accounting is double-entry with periods that close.
  • 04 On the phone, because that is where people are A teacher marks a register in the classroom, not in the staff room at lunch. An absence alert at 9:35 is useful; the same alert at 4pm is a formality.
One student record read by every module
How we build

Five things we do that are not obvious from a feature list

These are the working habits that decide whether software is still trustworthy in year three. They are the reason some of our pages read like specifications rather than brochures.

We publish what we do not do
Every module page has a limits section. A school that discovers a gap in a demo forgives it; a school that discovers it in month three does not renew. Nobody else in this category does this, and it is the cheapest trust available.
Permissions in the query, not the interface
A role cannot see something because the data is not returned, not because a tab is hidden. Hiding a menu item and calling it access control is the most common serious defect in school software.
Migrations are reconciled before go-live
We import onto a copy and show you three figures — student count, total outstanding, opening ledger balance — for you to check against your own records. If they do not match, we find out why first.
History is superseded, never edited away
A wrong invoice gets a credit note. A moderated mark keeps the original. A corrected register records who changed it and why. Deleting is how an audit trail becomes worthless.
We fix at the root
A security review found three copies of one role list that had drifted apart. We consolidated them into one model rather than patching each call site — which is slower once and correct afterwards.
A person replies
Support is people who can answer a fee-structure edge case, not a queue that escalates. If you e-mail us a technical question you get a technical answer.
Boundaries

What we will not build, and why

These are not gaps in a roadmap. They are decisions, and stating them costs us some deals — which is the point of stating them. A school that needs one of these should buy from someone who will build it rather than hoping we change our minds.

  • 01 Facial recognition attendance We will not build a system that identifies children by face. Fingerprint and RFID devices integrate, and a teacher marking a register on a phone takes fifteen seconds.
  • 02 Tracking children off campus Vehicle tracking, yes. A gate pass records where a boarder said they were going. Tracking a child’s own location is not something we will make available to anybody, including a school.
  • 03 CCTV integration Not because it is hard. Because a school management login should not be a camera console, and combining the two creates a surveillance system nobody agreed to.
  • 04 Scoring parents We show defaulter ageing and payment history, which are facts. We will not compute a creditworthiness score for a family, and we would not want a school making decisions with one.
  • 05 Implying certifications we do not hold We are not ISO 27001 or SOC 2 certified. If a tender requires either we will say so in the first meeting rather than the last.
Role-based access configuration

Four commitments, in numbers

Each of these is a policy we can be held to, not an aspiration.
100%
Of your data exportable, any time, by you, without asking us — on every plan
₹0
For migration and onboarding, including on the lowest plan
0
Per-user charges. Add every teacher, clerk and parent
1
Working day to a reply from a person who can answer
The commitment that matters most

Your data is yours, and we will not use it to keep you

The standard way to retain a school in this market is to make leaving expensive: no export, or an export that is technically available and practically useless, so that switching means re-typing thirteen years of records. It works. It is also the reason schools are so reluctant to change systems in the first place, which is bad for every honest vendor including us.

So the policy is the opposite. You can export everything, at any time, yourself, in open formats, without asking us — students, guardians, fees, the full ledger, attendance, marks, documents. Not a support request. Not a paid professional-services line. Not a redacted subset. It is on every plan, including the lowest, and it works during a trial as well as during a subscription.

If you stop subscribing, access pauses and nothing is deleted. Your data is still there when you come back, and still exportable if you do not.

We would rather earn the renewal each year than hold a school’s records to get one. If the software stops being worth what it costs, we would prefer you left cleanly and told us why — that feedback is more valuable to us than a year of a subscription somebody resents.

Questions

Questions about us

Something not answered here?

How many schools use School Techy?
We do not publish a number, and we would rather explain why than print one. Every competitor page in this category carries a figure like “trusted by 125,000+ schools”, and most of those do not survive a request for three references. If you want to speak to a school actually using this, ask on the call and we will arrange it with one of a comparable size and board, without us in the room. That is a better test than any number.
Are you a large company?
No, and it affects what you should expect in both directions. You get a named person who knows the product and can answer a technical question directly, and product decisions do not go through three committees. You do not get a twenty-four-hour multilingual call centre or an ISO certificate. Judge which set of trade-offs suits your school.
What happens if you are acquired or shut down?
This is a fair question to ask any vendor and most answers are evasive. Ours: your data is exportable in open formats at any time, without our involvement, so you are never dependent on our cooperation to leave. That is the only answer that is actually worth anything, because every other reassurance depends on the company still existing to honour it.
Do you build custom features for one school?
Rarely, and we will usually say no. A feature built for one school becomes something every other school has to live with, and school software gets unusable that way. What we do instead is take the underlying requirement seriously — if three schools ask for the same thing in different words, that is a real gap and it goes into the product properly.
Why is the product priced lower than the market?
Because per-user pricing and per-module unlocks are how school software is usually made expensive, and we do not do either. Adding every teacher and every parent costs nothing extra, and your plan’s modules are all on. The price reflects included students and campuses, which is a fair proxy for the size of the school.
Do you resell or share school data?
No. Never to advertisers, never to lenders, never to other education companies. We use your data to operate the service for you and for nothing else. Given what a school holds — children’s names, addresses, medical notes, family financial circumstances — anything else would be indefensible.
Who do we talk to when something goes wrong?
A person, within one working day, who can answer the question rather than log it. For schools on higher plans there is a named contact. We would rather over-invest in this than in a support portal, because in a school year the moments that matter are the ones where something is broken on a Monday morning.
Can we see the product before giving you our details?
Yes — start a trial with an e-mail address, no card, and look around with sample data. The demo call is worth having because we load your own class list and fee structure into it, but it is not a gate you have to pass to see the software.
Next step

Ask us the question you have not asked other vendors

The one you expect an evasive answer to. That is usually the most informative twenty minutes either of us will spend.

  • No card required
  • Your data stays yours — export any time
  • Setup help included

No card required. We reply within one working day and never share your details.