Family services
Bayinah previewMultiple children, homework, results, fees, notices, reminders and collection arrangements.
One school.
Connected people.
Sufrone Education connects school operations with the daily experience of families and staff. Explore the Bayinah Academy use case, then plan an instance for your school.
Fictional demonstration records. No credentials to type.
See Bayinah in use.
Move between the school website, family services and staff operations. Preview records are separate from a client’s school deployment.
School website
Programmes, campuses, enquiries and admissions.
Parent portal
Two children, learning, fees, collection and school mail.
Staff portal
School management, department workspaces and communication.
The education package.
Teaching & academics
Bayinah previewAssigned classes, lesson planning, attendance, reviewed marks, reports, timetable and Madrasa progress.
Admissions & marketing
Bayinah previewProspective families, applications, enrolment records, campaigns and follow-up workspaces.
Finance & procurement
Bayinah previewSchool statements, accounting, purchase approvals, suppliers, stores and asset custody.
People & support
Bayinah previewEmployee self-service, leave and expenses, library, support queues and restricted welfare/health records.
Transport & school day
Bayinah previewSeparate driver and assistant duties, boarding and alighting, absence reports and parent collection.
School communication
Bayinah previewNotices, responses, reminders and private school mail with signatures. Demo mail is captured locally.
Moodle learning module
Planned · added laterCourses, learning resources, quizzes and LMS progress. Moodle will be connected later for client preview.
Bayinah is the current demonstration use case. Live Google Workspace, payment processing, traffic/GPS and background alerts require their own provider setup and acceptance. Moodle is planned and is not running in this preview.
Your school. Its own setup.
Bayinah is the first use case, not a shared database for future schools. Branding, campuses, school policies, permissions and provider accounts belong to each client’s implementation.
Discuss your school’s onboarding- Confirm campuses, programmes, roles and the modules the school needs.
- Provision an isolated school instance and configure policies, approvals and identity.
- Map and reconcile the school’s data; connect its own mail and payment providers.
- Rehearse school workflows, recovery and training before agreeing the pilot rollout.