Bring Bell to your school.
Run your school on Bell, or start alongside the system you already use. Either way, the school stays in charge of its data and its rules.
Choose how Bell fits.
Your school, on Bell.
Your own Bell at yourschool.bell4schools.com, hosted in the EU, with the office, teachers, students and families in one place.
- Bell’s own sign-in, with passkeys
- Manage school for years, scales, classes, people and the timetable
- The iPhone, iPad, Mac and Watch app for students
- Push notifications and an email digest
Keep what you have.
Start with the student app next to your current system, and move further only when you are ready.
- The Bell Companion reads timetable, homework and grades from ASIMS today
- Read-only unless the school allows hand-ins through Bell
- Librus and Vulcan are not connected; keep your official register during the pilot
- Authorised imports are checked together before use
From first call to first term.
A pilot follows these steps, at the school’s pace.
Talk
A walkthrough with your own timetable and questions.
Agree
The pilot’s scope, the data processing agreement, and export and exit arrangements before it starts.
Import
People, classes, enrolments and weekly timetables from spreadsheets.
Invite
Staff, students and verified families get an email invitation.
Pilot
A named contact answers within two school days, with a weekly report through the first term.
Import from the spreadsheets you already have.
CSV, checked row by row.
Paste or upload comma, semicolon or tab separated sheets for people, classes, students in classes, teachers in classes and weekly timetables.
- Up to 500 rows at a time
- A verdict for every row before anything changes
- Importing the same sheet again updates instead of duplicating
Shaped like the standard.
Bell’s school data follows the OneRoster model of years, terms, classes, enrolments and people, so exports from other school systems map onto it.
- School years, terms and grading periods
- Grading scales: numbers, percentages or the school’s own codes
- Teachers with explicit permissions per class
Build the week once.
A weekly slot generates every dated lesson, with single lessons and cancellations on top.
- Overlapping lessons are refused
- A timetable builder plans from teachers, rooms and groups
- Check a draft for a better arrangement, on EU servers
Set the policy once, on every school iPad.
Bell reads the school’s settings from device management. Where two settings disagree, the stricter one wins.
Works with your MDM.
Jamf Pro, Microsoft Intune, Mosyle, Kandji and Jamf School deliver Bell’s managed configuration.
aiPolicy
Off, on-device only, students’ own keys, or the school’s own AI service with aiEndpoint and aiModel.
Hand-ins, sync and the guide.
asimsWrites for hand-ins, allowPersonalCloudSync for iCloud study sync, and schoolGuide for who students should contact.
Your data stays the school’s.
In the EU.
Bell runs in Frankfurt, with nightly encrypted backups and an off-site copy.
Export on request.
A school can request an export of its records at any time; people can download what is theirs.
Before real data.
A data processing agreement, a list of subprocessors, and an independent security review before any real school data.
Questions about integration
Do we need our own servers?
No. Bell hosts each school in the EU. The school manages people, classes and settings from the browser.
Can we use our own AI service?
Yes. With aiPolicy set to school, students use the school’s own OpenAI-compatible service, named by aiEndpoint and aiModel. Or turn the tutor off entirely.
Can Bell import from our current register?
From spreadsheets, yes: people, classes, enrolments and timetables. A direct connection to Librus or Vulcan is not part of the pilot.
What about bespoke integrations?
Standard onboarding is included in the licence. Bespoke migration or integrations need a separate agreed quote.
Start with a conversation.
Tell us what your school uses today, and we will show how Bell would fit around it.
What Bell does for teachers