Free Hostel Management for K-12 Schools

The hostel module itself is LGPLv3 open-source — download, self-host, modify, no licensing fees per bed or per boarder. You pay only for the server you run it on (typically $10-30/month on a VPS). Honest disclosure of paid extras: advanced safeguarding analytics, SSO with Google Workspace or Microsoft Entra, premium parent-app push notifications, and white-glove migration services are optional add-ons. Core room allocation, mess attendance and billing, exeat workflow, warden roster, parent portal, and basic incident logging are fully free.

For a 100-500 bed boarding house, a $10-30/month VPS (Hetzner CX22, DigitalOcean basic droplet, Linode Nanode) handles it comfortably. Add ~$15/year for a domain, optional $5-10/month for managed daily backups, and roughly one IT-staff afternoon per quarter for OS patches and version updates. The honest line: if your school already runs any Linux server (library catalog, Moodle, file share), the marginal cost is essentially zero because the same IT person and the same backup routine cover it.

No. The module scales down without configuration penalty — a small house with 60 boarders uses the same install as a 500-bed school, just with fewer rooms in the allocation map and fewer rows in the mess report. There's no minimum-seat licence to worry about. Many small Catholic boarding schools, residential special schools, and rural K-12 boarding houses with 40-90 boarders run the stack on a single $10/month VPS. The setup work is the same regardless of size; the daily use scales naturally.

Proprietary K-12 boarding software (Reach Boarding, BoardingWare, OrahApps, ISAMS Boarding) typically charges per-boarder annual licences in the $15-40 per boarder per year range, so a 300-bed school pays $4,500-12,000/year for the licence alone, plus implementation. OpenEduCat's hostel module is free of that licence cost — you trade the licence fee for self-hosting responsibility (a VPS, occasional patches) and the loss of vendor-managed support. Honest comparison: proprietary vendors will be faster to set up and have polished mobile apps; the open-source path is materially cheaper at scale and gives you data ownership and the right to modify the code. Schools with in-house IT or a partner integrator usually prefer self-hosted; schools with no IT capacity at all often pay the proprietary licence and don't regret it.

Yes, and most schools do exactly this. Bed allocations, boarder details, and parent contacts import via CSV templates — typically a half-day of data prep for a 300-bed house. Mess plans and warden rosters get set up fresh in the system because they change termly anyway. Historic exeat records and incident notes don't usually migrate (they live in the paper book / archive) — you start the digital trail from day one of the new term. Practical guidance: pick a term break (Christmas, summer, or half-term) for cutover, run a parallel week with the paper book as a safety net, then go fully digital.

The module produces the documentation trail required by Ofsted National Minimum Standards for Boarding Schools (England) — leave records, supervision rosters, incident logs, sick-bay visits, and complaint records, all timestamped and exportable for inspection. The same trail satisfies the residential boarding sections of the ISI Commentary on the Regulatory Requirements (UK independent schools) and the CIS International Accreditation residential boarding standards. Important honest caveat: software produces the records; compliance is a process that includes trained staff, safer-recruitment checks, a designated safeguarding lead, and child-protection policies. The hostel module does not replace any of that — it just makes the documentation side defensible. Advanced safeguarding analytics (pattern detection, predictive welfare flagging) sit as a paid add-on for schools that want that layer, but baseline inspection-ready records are in the free core.