Free Hostel Management for Boarding Schools

The openeducat_hostel module is part of the OpenEduCat Community Edition, released under LGPLv3. House-based allocation, exeat workflows, safeguarding logging, mess attendance, tuck-shop billing, and the parent portal are all in the free module — not paywalled behind an Enterprise tier. There is no per-boarder fee. The catch is that you self-host on your own infrastructure (a small VPS, an on-premise server, or a hosted partner). You're trading a hosting decision for a five-figure annual licence.

A 200-boarder deployment runs comfortably on a $40/month VPS or a small on-premise server in the school IT cupboard. The IT lead handles updates the same way they patch the SIMS server — quarterly maintenance windows, mostly out of term time. If your IT capacity is one part-time technician, an OpenEduCat hosting partner takes hosting off your hands for a fraction of what proprietary boarding software costs, and you keep ownership of the data and the right to leave whenever you want.

Reach Boarding and Boarders' Plus are mature and expensive — typical pricing runs £15-£40 per boarder per year on multi-year contracts. openeducat_hostel covers the same core workflows (allocation, leave, attendance, safeguarding) and integrates with the academic side — admissions, timetabling, fees, exams — in a way single-purpose products cannot, because it lives in the same database as the rest of the school MIS. Trade-off: less proprietary polish, more integration depth, no annual licence. Schools migrating from Reach typically port records via CSV in a half-day.

It supports the evidence side of the standards rather than replacing the policy framework. The UK National Minimum Standards for Boarding Schools require documented records of boarder whereabouts, leave arrangements, safeguarding incidents, and routine welfare contact — all of which openeducat_hostel produces in inspection-ready exports. The ISI Inspection Handbook for boarding and the CIS Accreditation Standards for residential life expect the same documentary trail. The module gives inspectors the records; the school still owns the safeguarding policy and DSL relationships. Schools running it typically cut inspection prep from two weeks to two days.

Houses configure independently. Each sets its own bedtime by year group, prep schedule, mess sitting times, activity rota, and weekend leave policy. Housemasters see only their own roster and exception reports; the head of boarding sees the unified view. Boarders moving house mid-year carry their full record, so the new housemaster picks up the safeguarding context from day one. School-wide rules (safeguarding categories, exeat approval chain, parent-portal access tiers) set centrally so audit consistency holds across the boarding community.

Pilot with one house and one term. Export the current boarding roll, exeat log, and safeguarding register from spreadsheets to CSV, import to openeducat_hostel, and run that house in parallel for a half-term so the housemaster builds confidence. Roll the other houses in over the following two terms. The migration that breaks schools is the all-at-once September cutover; the one that works is a quiet Lent or summer-term pilot when stakes are lower.