A cloud school system needs internet to use, but a school's own outage does not touch its data: records stay on the provider's servers and staff can carry on from a phone on mobile data. EDUBase keeps each school in its own database with regular off-server backups.
What stops working when the school's internet goes down?
A cloud-hosted school management system runs on the provider's servers, not on a computer in your office. When the school's own connection drops, the computers on that network simply cannot reach the portal until the connection returns, or until someone switches to another connection.
Nothing is stored only on the office PC, so there is nothing at the school to corrupt or lose. Anything already saved before the outage is safe on the servers. The only work at risk is a form that was open and not yet saved, which should be checked and re-entered once you are back online.
- Records saved before the outage: safe on the servers
- An unsaved form at the moment the line dropped: re-enter it
- Data on school PCs: none to lose, because the records are not kept there
How can the office keep working during an outage?
Because EDUBase is reached over the internet rather than over the school's own network, any working connection will do. Many schools keep a mobile-data hotspot or a second connection as a fallback for the fee counter and front desk.
Much of the daily work also happens on phones, which use their own mobile data. Teachers use the EDUBase Teachers App, owners and principals use the EDUBase Owners App, and parents use the EDUBase Parents App on their own connections.
- Switch the office PC to a phone hotspot or a backup connection
- Teachers mark attendance and write the diary from the Teachers App
- The owner checks today's P&L, collections and defaulters in the Owners App
- At the gate, face attendance recognises people on the tablet itself, so a slow internet connection does not hold up the queue
Can parents still pay fees when the school is offline?
Yes, if the school uses bank fee collection. Each challan prints a consumer number that parents can pay at a bank branch, ATM, banking app or 1Bill/1LINK channel. The bank calls EDUBase directly, so the school's own internet plays no part in that payment.
EDUBase supports HBL, Bank Alfalah, Meezan Bank, PayPro and KuickPay. The payment appears in Paid Challans and Payment History straight away, and a challan already paid answers as paid to any later inquiry, so a family cannot be charged twice. When the office is back online, the payments are visible in Day Wise Paid Challans like any other.
Where is our data, and is it kept apart from other schools?
Every school on EDUBase has its own separate database on EDUBase's servers, so your records are never mixed with another school's. This is known as database-per-tenant isolation: rather than many schools sharing one set of tables separated by a school ID, each school's records sit in a database of their own.
Staff sign in with the school's institute code, a username and a password, and sessions expire. Parents log in with a rotating one-time code sent to their registered mobile, so there are no shared passwords.
How is the data backed up and protected?
EDUBase Cloud is hosted and maintained by the EDUBase team. Regular database backups are kept off the application servers, so a problem on one server does not take the backup with it. The servers, the resolver and the messaging gateway are monitored externally with automatic alerts.
All portal and app traffic runs over HTTPS. Attendance tablets and phones hold their own revocable credentials, so a lost device can be cut off without changing anyone's password. Inside the school, User Logging shows who created, changed or deleted any record.
- One database per school
- Regular backups kept off the application servers
- External monitoring with alerting
- HTTPS for the portal, apps and integrations
- Revocable device tokens for tablets and phones
How does this compare with software on a school PC?
With desktop software, the school's records usually live on one computer in the office. A failed hard disk, a theft, a virus or a fire can take years of fee and student history with it unless someone has been taking and testing backups. With a cloud platform, the office computer is only a window onto the data, and backups are the provider's job.
The trade-off is that cloud software needs an internet connection to use. For most schools, a mobile-data fallback is a much smaller risk to manage than the safety of a single office PC.
Cloud-hosted school software versus software installed on a school PC
| Situation | Cloud-hosted (EDUBase) | Software on one school PC |
|---|---|---|
| School internet is down | Use the portal on another connection, such as a phone hotspot; staff and owner apps work on mobile data | Office PC keeps working, but only on that machine |
| Office PC fails or is stolen | No school data lost; log in from another device | Data lost unless a recent, working backup exists |
| Fire, flood or virus at the school | Records are on EDUBase's servers with backups kept off the application servers | Records and any backups kept on site may both be lost |
| Parents paying fees | Bank payments post to EDUBase directly, whatever the school's connection | Payments recorded by hand when the office is open |
| Owner checking figures from home | Owners App shows today's P&L, collections and defaulters | Usually requires being at the office PC |
| Who runs backups | The EDUBase team | The school, usually one staff member |
| Separation from other schools | Each school has its own database | Single school on a local machine |
| Software updates | Shipped regularly to every school with nothing to install | Installed manually on each PC |
Related
- Cloud & Infrastructure Services — Managed hosting, one database per school, backups, monitoring and secure networking for education workloads.
- Legacy System Transformation — Move from Excel registers, desktop software or an old portal to a modern cloud platform without losing history.
- Data Migration & Onboarding — Students, families, fee plans, old dues, past payments and staff moved from Excel or any system, verified before go-live.
- Training & Support — Live Google Meet training, module video playlists, in-app docs and an AI assistant, with WhatsApp and phone support in working hours.
- Hosting security on edubaseems.com
- Users privileges security on edubaseems.com
- Bank fee collection on edubaseems.com
- Face attendance on edubaseems.com
- Owner dashboard reports on edubaseems.com