KIDUART school ERP

Do not compare school ERP demos. Compare the answers vendors give under pressure.

Take these 9 questions into every school ERP call. Each one exposes a place where ownership, security, privacy, lock-in or roadmap claims usually become unclear.

Buyer's due-diligence checklist

Ask the same list to us and every vendor you shortlist

A vendor-written comparison table will always end with that vendor winning. This page gives your school one consistent test instead. Tick the questions that matter, compare the answers, and follow the evidence links rather than accepting adjectives.

  1. What usually happens

    Some vendors collect fees into their own payment account and settle to the school later. Your money sits with them, and your reconciliation depends on a statement they prepare.

    How KIDUART answers it

    You connect your own Razorpay or Stripe account, so parent payments settle into the school's account and never pass through ours. Your gateway keys are encrypted before they are stored.

    See payment integrations
  2. What usually happens

    Cheaper systems keep every school in one shared set of tables and separate them with a school ID on each query. One forgotten filter is all it takes for another school to read your data.

    How KIDUART answers it

    KIDUART is multi-tenant by design: the tenant is resolved before any query runs, so the boundary is structural rather than a condition a developer has to remember.

    Read the isolation layer
  3. What usually happens

    Export is where lock-in hides. Some contracts allow only PDFs, some charge a migration fee, and some simply stop responding once you give notice.

    How KIDUART answers it

    Student records, fee ledgers, attendance and academic data export in CSV, Excel and PDF whenever you ask including on the way out and we remove your data after the agreed wind-down window.

    Read the data terms
  4. What usually happens

    Student data is valuable and rarely discussed in the sales meeting. Coaching tie-ups, book vendors and ad platforms are all buyers, and a vague privacy policy leaves the door open.

    How KIDUART answers it

    We do not sell school, student or parent data, and we do not use student records to train models. The predictive features run on your own records inside your own instance.

    Read the privacy policy
  5. What usually happens

    Many school systems ship one all-powerful admin login that the whole office ends up sharing, so salary and exam data are one click away from anyone at the front desk.

    How KIDUART answers it

    Access is decided by role, not by trust. Permissions are explicit per role, can only be delegated downward, and each role gets its own panel an accountant never lands on exam marks.

    See the role panels
  6. What usually happens

    Shared staff passwords and no second factor are the norm, and most systems will happily accept that login from anywhere in the world.

    How KIDUART answers it

    Passwords are hashed with bcrypt, failed attempts lock the account, staff can add an authenticator app with backup codes, and schools that want it can fence admin access by IP or location.

    See the login controls
  7. What usually happens

    Without a real audit trail, a disputed mark or a written-off fee becomes one person's word against another's and logs that can be edited prove nothing.

    How KIDUART answers it

    Logins, permission changes and financial events are written to an audit log, and audit records are chained to the record before them so tampering is detectable rather than silent.

    See the audit layer
  8. What usually happens

    Demos are often stitched from screens that only exist for the demo. The gap shows up months later, renamed as customisation and quoted separately.

    How KIDUART answers it

    What you see on the Features pages is what ships. Anything still being built is labelled in development on the page itself and is not billed.

    Browse the module areas
  9. What usually happens

    Software built for another market forces your school to fit its shape no session-wise structure, no fee concessions, no transfer certificate, and parent updates on channels families do not use.

    How KIDUART answers it

    Academic sessions, classes and sections, fee heads with concessions, transfer certificates, transport routes, hostel and library all ship as first-class modules, and parents hear from the school over WhatsApp, SMS and email.

    See the academic modules

Tick the questions that matter to your school

Ask them to us on the call and ask the same list to every other vendor you shortlist.

Put us through it
Live demo

Put KIDUART through the same checklist

Bring your principal, accountant or IT reviewer. We will answer each question on screen and say plainly where a control is optional, guided or still on the roadmap.

  • 30-minute walkthrough

    Booked around your school hours

  • Run on your own data

    Your fee heads, classes and staff roles

  • No card, no lock-in

    Nothing is charged to see the product