Trust-first.
India-first.
Integrated on day one.
There are three real choices for a school trust in India today — a foreign K-12 product retrofitted for India, a stack of Indian point solutions glued together with exports, or a trust-grade Indian platform built from scratch. aCloud is the third. Here's exactly why that matters.
Trust-first vs single-school retrofitted.
The single-school retrofit
A school ERP built in 2014 for one school. In 2019 they added a "branch" flag. Today they call it "multi-school". The fee module still treats fee heads as school-local. Each school still has its own staff master. Trust consolidation is a quarterly Excel export.
Symptom: same staff member exists three times across three schools. Same student admitted twice when they moved campuses. RTE numbers are calculated school-by-school.
The aCloud approach
The trust is the unit. Students, staff, fee heads, ledgers, vendors, assets — all belong to the trust. Each school is an operational tenant inside it. Move a student between wings, the record carries forward. Move a teacher between campuses, appraisal history carries forward.
Outcome: one consolidated trust book at year end. One UDISE+ filing per school but one staff master across the trust. RTE reservation tracked per school, settlement tracked per trust.
India-first vs translated from elsewhere.
A school in India is a regulated entity. Not a CRUD database. The minute a CBSE-affiliated trust touches an admission, twelve things must happen — RTE 25% bucket, UDISE+ PEN issued, APAAR generated, parent KYC captured, DPDPA consent locked, fee structure assigned, transport allocated, house assigned, books reserved, communication template fired.
None of this is in foreign K-12 products. None of it is properly stitched in stacked Indian solutions. In aCloud, it is the default admission flow.
APAAR ID
Auto-generated, DigiLocker-pushed.
UDISE+ PEN
Assigned at admission, filed annually.
RTE 25%
Lottery, reservation, reimbursement audit.
Form 10B / 10BB
Trust audit data straight from posted books.
80G + 10BE
Donation receipts issued at source.
DLT SMS
Template-registered through approved aggregators.
DPDPA 2023
Consent ledger, principal rights, grievance SLA.
Integrated vs stacked point solutions.
The point-solution stack
A school using six vendors: ERP, fees, LMS, transport, library, communication. Each one has its own login, its own student master, its own version of the truth. Integration is a CSV export at midnight, imported the next day with errors.
A parent in this world receives an SMS about fees, then logs into a separate portal for marks, then a third app for transport, then another link for circulars.
The aCloud approach
One identity layer. One ledger. 23 modules. Twenty-three. All built by us, on one database, sharing the same student, the same staff, the same fee head, the same audit log. When a fee is paid, the report card is unlocked instantly. When attendance is marked, the SMS to parent fires from the same record.
A parent here uses one app. One login. One source of truth. One support number when something is wrong.
We're honest about where aCloud is the wrong answer.
Don't buy aCloud if…
- You run a single-section pre-school or coaching centre under 100 students.
- You operate higher education (universities, PhDs, post-grad). aCloud is Pre-KG to Class 12 only.
- You want a product to lease and re-skin yourself with no involvement from us.
- Your trust does not file Form 10B/10BB and is comfortable continuing that way.
Buy aCloud if…
- You operate one or more K-12 schools under a registered trust.
- You need consolidated trust books, multi-school RBAC, audit-ready filings.
- You want APAAR, UDISE+, RTE, DPDPA done — not promised.
- You want one platform replacing the spaghetti of vendors and Excels.
Why aCloud — questions answered.
Most school ERPs are single-school products with multi-school added as a flag. aCloud is the opposite — it is a trust-grade platform where every entity (student, staff, fee, ledger, asset) belongs to the trust, with schools as operational units underneath. This changes everything: consolidation, transfers, reporting, RBAC, audit, compliance.
Those are excellent products built for North American K-12 and IB schools. They do not implement APAAR, UDISE+, RTE 25% reservation, Form 10B/10BB, DLT-registered SMS, Indian board grading systems or Section 8 trust accounting. Retrofitting these into a foreign product is harder than building India-first.
Because they don't share identity. A student's report card depends on attendance which depends on identity which depends on admission which depends on fees. Stack five vendors and you have five identity systems, five permission systems and five places where data is one day stale.
Substantially. A serious in-house team for an academic platform — backend, frontend, mobile, infra, compliance, support — costs ₹1.5–3 crore per year and takes 18+ months to reach feature parity with what aCloud ships on day one. Most trusts do not need to be in the software business.