What shipped, and what it does not do yet

Self-hosted AI assistant for staff questions

Staff can ask questions about how to do something in the platform and get an answer drawn from the product documentation. The model runs on infrastructure the school or its operator controls, so questions and school data do not leave that boundary for a third-party AI provider.

Limit: It answers questions about using the platform. It does not answer questions about a specific student, invoice, or result, and it is not a substitute for support.

Telr gateway for Gulf currency collection

Schools billing in AED, SAR, and other Gulf currencies can take card payments through Telr, which settles locally. Previously that meant routing a regional collection through a gateway priced and settled for another market.

Limit: Merchant onboarding with Telr is the school’s own account and has its own lead time. Budget for it in the phase that includes fees, not the week before go-live.

Stripe gateway for card and wallet payments

Schools with a Stripe account can collect fees through it, with the payment recorded against the student ledger and a receipt issued automatically on confirmation rather than after a manual match.

Custom domain for the school website and portals

The public site and the family portal can be served from the school’s own domain, so parents sign in somewhere that looks like their school rather than somewhere that looks like a vendor.

Limit: DNS and certificate setup is an operator task at the hosting layer, not a self-service toggle inside the product.

Bulk Excel import and export across core records

Students, guardians, staff, and timetables can be loaded and extracted as spreadsheets, with validation reporting which rows failed and why rather than rejecting the whole file. This is the path most migrations actually use.

Limit: Import validates structure and duplicates. It does not decide which of two near-identical guardian records is the right one; that judgement stays with the school.

Transport trip location tracking

Trip progress is recorded against route stops, so the office can answer a parent asking where the bus is without phoning the driver, and a late run is visible while it is still happening rather than after the first complaint arrives.

Limit: Progress is recorded against stops on the route. This is not continuous vehicle telemetry, and it depends on the trip being operated through the platform.

Notification delivery queue with retry

Outbound notifications are queued and retried rather than attempted once and dropped, so a transient mail failure no longer means a fee reminder silently never arrived.

Limit: Delivery is retried; receipt is not guaranteed. A parent whose mailbox rejects the message still has to be chased another way.

Dead-letter handling for payment webhooks

A gateway webhook that cannot be processed is captured rather than lost, so a payment that succeeded at the gateway but failed to record in the ledger becomes a visible item to resolve instead of a reconciliation mystery at month end.

Error reporting for platform operators

Server-side failures are reported with enough context for whoever runs the deployment to act on them, which shortens the gap between a school noticing something and someone being able to see what happened.

Activity log export for external monitoring

Platform activity can be exported in a form a school’s own security tooling can ingest, so audit evidence lives somewhere the vendor does not control.

Limit: This is an export, not a live streaming integration. It is scheduled or pulled, not pushed continuously.

Statutory payroll exports

Payroll produces the statutory return formats a school is obliged to file, rather than a generic report that someone then reformats by hand every month before the filing deadline.

Magic-link sign-in for families

Guardians can sign in from an emailed link instead of maintaining another password. Portal adoption is usually lost at the password reset step, and this removes it.

Limit: This is passwordless email sign-in, not single sign-on against an identity provider. Staff SSO is not available.

Exam schedule calendar feeds

Exam schedules publish as a subscribable calendar feed, so a student or parent sees the timetable in the calendar app they already check rather than a PDF they have to remember to reopen.

Limit: Feeds are read-only. Changes flow out of the platform, never back into it.

Automatic collection and structured dunning

Recurring fee collection runs on schedule, and overdue balances follow a defined reminder sequence instead of depending on someone in the office remembering which families were chased last week.

Limit: Reminder sequences go out over email. There is no automated SMS or WhatsApp channel; those are sent by a staff member.

Razorpay gateway for Indian fee collection

Schools collecting in INR can take card, UPI, and netbanking payments, with confirmation recorded against the student ledger and a receipt issued without a manual step.

Timetable import from spreadsheet

A timetable built in a spreadsheet, which is how most schools actually build one, can be loaded directly instead of retyped period by period into a form. Retyping is where the transcription errors that surface in registers come from.

Excel output across reporting

Reports export as Excel rather than only as PDF, so the numbers can be worked on rather than only read. Every report a school can see, it can also take away.

Academic calendar as the source of working days

Holidays, closures, and working days come from one academic calendar, and attendance percentages, fee schedules, and timetables all read from it. Before this, each area could disagree about whether a day counted.