schoolOS doesn't replace your stack. It connects to it. Sign-in, device management, knowledge, and rostering all draw on the systems your district already trusts.
Every integration is one click. Scoped OAuth consent, read-only by default, and no API keys to manage.
Nobody in a district needs another password. Staff and students sign in to schoolOS with the account they already use for everything else, which means adoption on day one and no credential for the help desk to reset at 7:40 in the morning. Identity stays where you already manage it.
Sign in with a district Google account.
Sign in with a district Microsoft or Azure AD account.
One-click sign-in from a district's ClassLink LaunchPad.
Most districts run more than one MDM: Jamf for the Macs, Google for the Chromebooks, Intune for whatever Windows is left. None of them agree on what a device is, and none of them know who's holding it. schoolOS connects to each one, pulls every device into a single asset record, and pushes your changes back out. Lock, wipe, or deprovision from the asset record instead of from three consoles.
Apple device management for computers and mobile devices, syncing both ways.
Chromebooks and other Google-managed devices from the Admin console.
Windows, iOS and Android devices managed through Intune.
Apple device management for districts on Mosyle Manager or Business.
An AI agent is only as good as what it knows, and what your district knows is scattered. The answer to “how do I request a sub” is in a Zendesk article. The device damage policy is a PDF in a shared Drive folder. The board's acceptable use policy is a page on the website nobody has opened since 2019. schoolOS indexes all of it, keeps it in sync as it changes, and cites the source on every answer, so people get your district's answer instead of the internet's.
Your district's own websites as a knowledge source.
Help Center articles as a knowledge source.
Freshdesk solution articles as a knowledge source.
Shared folders and documents pulled into the knowledge base.
Files and folders from OneDrive and SharePoint.
Rostering is what turns an asset record into something you can act on. A device stops being a serial number and becomes the Chromebook assigned to a fourth grader at Lincoln, in Ms. Alvarez's homeroom, whose guardian should get the damage notice. Every ticket, every assignment, every workflow leans on knowing who's who. So schoolOS takes the roster however your district can give it, from a CSV someone drags into a browser to a live API, and keeps it current overnight without anyone thinking about it again.
One screen for every way a roster can reach schoolOS, from a hand-uploaded CSV to a live API.
Rosters through ClassLink's proxy, which normalizes whatever SIS sits behind it.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only.
If you can click through an OAuth consent screen, you can finish the integration. No middleware, no CSV exports, no consultant. And because every connection is scoped, your data stays in your control.
Each integration requests only the scopes it actually uses, and you see exactly which ones before you approve.
Connections start read-only. Write access is enabled per connection, and only when you turn it on.
Credentials are never stored in plaintext, and you can revoke access from your own admin console at any time.
Student records stay in encrypted, tenant-isolated storage, from the data layer up.
What was pulled, when, and by which connection. Every sync leaves an audit trail you can inspect.
Delegated Google Admin flows and app-only Intune credentials, the same patterns your existing vendors use. No shared service accounts.
We build new connections with design partner districts, in weeks, not quarters.
Tell us what you run
Operational intelligence for K‑12. One front door, one connected picture, so your team spends less time coordinating and more time understanding.
.png){kind=icon}