{{ a.kind }}
{{ a.mins }}
{{ a.t }}
{{ a.d }}
In preparation
One platform for every campus you run.
The education ERP for universities, colleges and even schools. One governed record carries admissions, academics, research, fees, people and compliance across every level you teach, from K-12 through undergraduate, postgraduate, doctoral and post-doctoral. Sixteen interface languages, each institution’s data kept strictly its own.
9
Module groups
34
Functional domains
16
Interface languages
DSc → K-12
Every level covered
The product
The whole institution on one console.
Enrolment, collection, attendance and open cases on the same screen, drawn from the same record. What you see is what the registrar, the accounts office and the principal see.
ISO 9001:2015 · TÜV SÜD
DPDP 2023 ready
WCAG 2.2 AA
Four processes, one record
Institutions don’t stumble at software. They fail at handoffs.
Four processes carry an institution’s year. Every enquiry, mark, receipt and approval lands in the same register, so nothing is re-keyed on the way from one to the next.
{{ p.k }}
{{ p.n }}
{{ p.d }}
The platform
Nine module groups. One record of truth.
Turn on what you need this year and add the rest without a migration. Every module writes to the same student, staff and finance objects.
{{ m.code }}
{{ m.n }}
{{ m.d }}
Who it is for
Built for a university. Sized for a single college or school.
{{ s.n }}
{{ s.d }}
One identity, every role
The registrar, the professors, students and parents see the same record.
A student's golden identity carries their roles, source systems and relationships. Change an address once and the fee receipt, transport roster and guardian portal all agree.
01Role-scoped access, so a class teacher never sees another section's marks.
02Duplicate detection at the point of admission, not at audit time.
03Every merge and every override recorded with who, when and why.
One record, many claims on it
SISEnrolment, section and programme of record
FINDemand, concessions and every receipt issued
LIBLoans, fines and hostel residency
GOVConsent, notices and the audit trail
Four systems of entry, one golden identity. Change an address once and all four agree.
Bring us your term dates and your fee policy.We’ll show you your own institution running.
A consultant walks the workflow with your registrar and accounts team, in your language, on your data model. No slide deck.
Platform
Thirty-four functional domains, printed in registration.
Nine module groups across 140+ screens, covering every level an institution teaches: school, undergraduate, postgraduate, doctoral, post-doctoral and higher doctorates such as the DSc. Each module reads and writes the same student, staff, fee and policy objects, so a change in one place is a change everywhere.
{{ m.code }}
{{ m.n }}
{{ m.meta }}
{{ m.d }}
01 Admit · the critical module
A seat is allotted once, and the reason is still there in November.
Admissions carries the largest volume, the shortest deadlines and the most scrutiny of anything a university runs. Xshala treats it as a governed pipeline: policy is configuration, every rank is traceable, and a counselling round can be re-run to the same result.
- 01Enquiry and CRM
Prospects, campaigns and agent sources, with marketing consent honoured per channel.
- 02Application
Versioned form schemas per cycle, conditional fields, correction windows and fee rules.
- 03Merit and rank
Entrance scores, board marks and weightings resolved into a ranked pool with tie-breaks.
- 04Counselling round
Seat pools, category quotas, choice filling, upgrades and vacancy carry-forward.
- 05Offer and deposit
Firm, conditional and waitlist offers with expiry, deposit capture and an appeal route.
- 06Enrolled student
One student number, cohort, accounts and opening fee demand. The applicant record stays attached.
Reproducible allocation
Run the round again from the same inputs and get the same result. Every offer stores the rule version, evaluated rank, category and tie-break used.
Reservation as policy, not code
Seat pools, category quotas, supernumerary seats and carry-forward follow a versioned policy document an auditor can read alongside the result.
Evidence before offer
Document verification, equivalency review for international qualifications and fraud flags that gate progression, against an immutable snapshot taken at submission.
Exactly-once conversion
Admit to student runs idempotently. Re-running the batch never creates a second student; failures land in an exception queue instead of a duplicate record.
Beyond the back office
Portals, apps and an assistant that cites its source.
Student and guardian portals
Fees, attendance, timetable, results and circulars, with consent and notice history visible to the family.
Staff mobile
Attendance, marks entry and approvals sized for a phone, with the same permissions as the desktop console.
Governed AI assistant
Answers policy and deadline questions against your own regulations and quotes the clause it used. It recommends; a human decides.
Sixteen interface languages
Eight Indian and eight international languages, including right-to-left Arabic. Records stay in the language they were captured in.
Integrations
It connects to what you already run.
An ERP sits at the centre of a campus, not alone on it. These are the seams Xshala is built to hold.
Payment gateways
Online collection with gateway reconciliation built into the fee ledger, so the bank statement and the receipt register agree without a spreadsheet between them.
Biometric and campus devices
Attendance captured at the device lands in the same registers staff and families see, under the same role-scoped permissions.
Your LMS
Teaching stays in the LMS; the record of truth stays here. Rosters flow out, outcomes flow back, and neither system pretends to be the other.
Where the seam belongs →Messaging channels
Circulars, alerts and fee reminders reach families over email and SMS, with consent honoured per channel and the notice history kept on the record.
The integration inventory is confirmed against your environment during evaluation. Ask for the current brief.
Solutions
Three shapes of institution. One platform underneath.
The same modules, configured to how each kind of institution actually runs its year, from a multi-campus research university to a single school.
{{ s.code }}
{{ s.n }}
{{ s.d }}
Typically starts with
{{ s.start }}
What it covers
Implementation
Fee collection first. Cutover in writing.
Every deployment follows the same sequence, proved in parallel with your existing trackers before anything is retired. It starts where families notice and trust is won: collection.
{{ p.i }}
{{ p.n }}
{{ p.d }}
What your team does
Names an owner for every register, decides which sheet wins where two disagree, and signs off each phase before the next begins.
What ours does
Configuration, migration runs and reconciliation reports, training for two staff cohorts, and the first collection day with both teams present.
Plans follow your shape, not a student count band.
Tell us the modules and the number of institutions and we quote against that. No per-seat surprises at renewal.
{{ p.tag }}
{{ i.t }}
{{ p.n }}
{{ p.d }}
Why Xshala
Most ERPs digitise the paperwork. This one governs the decision.
Six differences that show up in the second year, not the demo.
{{ d.i }}
{{ d.n }}
{{ d.d }}
Against a typical legacy deployment
| Dimension | Typical legacy ERP | Xshala |
|---|---|---|
| {{ c.k }} | {{ c.a }} | {{ c.b }} |
Comparison describes patterns common to on-premise and first-generation cloud deployments. It is not a claim about any named product.
Security and compliance
A student's record is not marketing data.
Xshala is built for institutions that answer to a board, a regulator and a parent. Here is what that means in the product.
ISO 9001:2015 with Design · TÜV SÜD
DPDP Act 2023 ready
WCAG 2.2 AA
{{ s.kicker }}
{{ s.n }}
{{ s.d }}
Regulatory readiness
The returns season, off the critical path.
Regulators ask for records the institution should already hold. Xshala keeps them governed as a by-product of daily operation, so a return is a report, not a project.
NAAC and NBA evidence
An accreditation cycle asks for enrolment, outcomes, finance and governance data over five years, with evidence attached. The record keeps that shape from day one, so the self-study draws from the register instead of a spreadsheet built the month before the visit.
Read the accreditation guide →NEP 2020 academic structures
Credit frameworks, electives with capacity rules and programme structures from certificate to doctorate are configuration, not custom work. When policy moves, the academic record moves with it.
UGC, AICTE and statutory returns
Statutory reporting runs from governed report definitions, so the number filed is the number the register holds. Two people asking the same question get the same answer.
DPDP Act 2023
Consent register, notice history, purpose limitation and retention schedule are product surfaces. A data-principal request is answered from the record, not reconstructed for it.
Read the DPDP explainer →Examination custody
Marks move through entry, verification, moderation and publication with an immutable trail. When a result is challenged, the register answers with who, when and under which policy version.
Read the custody explainer →WCAG 2.2 AA
High-contrast modes, reading spacing, text scaling, full keyboard operation and reduced motion ship in the product, for staff and for the families who use the portals.
Ask for the security brief
Data-processing terms, sub-processor list, retention schedule and the accessibility conformance statement are available to institutions under evaluation.
Resources
Field notes for people who run the office, not the demo.
Implementation guides and policy explainers written for registrars, principals and accounts teams. First pieces publish from August 2026.
The evaluation kit
Running a selection? Start with these three.
The RFP checklist
The questions procurement forgets to ask any vendor, ours included: migration, training cohorts, integration ownership and what happens at renewal.
Read before you shortlist →The migration sequence
A week-by-week reference plan for moving off spreadsheets without losing a term, starting with fee collection.
Read the plan →The security brief
Data-processing terms, sub-processor list, retention schedule and the accessibility conformance statement, for institutions under evaluation.
Request the documents →Get them when they publish
One email per guide. Nothing else, and no sharing with anyone.
About
Built by Axxonet. Integrity first, since 2000.
Axxonet has spent more than twenty years building systems: enterprise data platforms, medical devices, neuro research instrumentation and homeland-security software. Xshala applies that learning and discipline to the institutional record.
The group is certified to ISO 9001:2015 with Design by TÜV SÜD and operates from India, the United Kingdom, Finland and the United States.
Engineered by
2000
Founded
4
Countries of operation
5
Engineering divisions
The group behind the platform
{{ d.n }}
{{ d.d }}
{{ e.n }}
{{ e.c }}
Contact
Talk to an education-solutions consultant.
Tell us how your institution is shaped and which processes hurt. We will come back with a walkthrough against your own term dates and fee policy.
Request received
A consultant will reply to {{ sentTo }} within one working day. If it is urgent, call +91 80 41508919.
Common questions in evaluation
How long does a first go-live take?
It depends on your modules and your data, so we commit to a sequence rather than a slogan: fee collection first, proved in parallel against your existing tracker, then identity, academics and a cutover date fixed in writing. A week-by-week reference plan for a single institution is published in the migration guide.
Can we start with a few modules?
Yes. Turn on what you need this year and add the rest without a migration. Every module writes to the same student, staff and finance objects, so later modules inherit the record instead of importing it.
We are a trust with several institutions. One system or several?
One platform, one isolated tenant per institution. A branch user cannot cross the boundary; a group console reads across it for trustees, so you can compare without merging and report without exporting.
We are an affiliated college, not autonomous. Does assessment fit?
Yes. Assessment configures to the affiliating university’s calendars and returns, with sealed internal marks, or runs the full examination suite for autonomous institutions: scheduling, moderation, revaluation and transcripts.
Who owns the data?
The institution does. Each tenant’s data is strictly its own, retention follows a schedule you can read, and the data-processing terms, including return and deletion, are available to institutions under evaluation.
Which languages does the interface support?
Sixteen: eight Indian and eight international, including right-to-left Arabic. The interface switches per user; records remain in the language they were captured in, so nothing is lost in translation at audit.