For MSPs serving schools

Built by an MSP that runs its own practice on real school clients.

Nexus isn't a generic platform with an education vertical bolted on. Part of the MSP practice we dogfood Nexus on serves K-12 school clients directly, which is why FERPA and COPPA aren't abstract line items on our compliance framework list.

What's actually different about a school client

Schools aren't a smaller version of a commercial client.

They're a different shape of client entirely — and a platform built only for commercial IT tends to show the gaps quickly.

Budgets are public, fixed, and scrutinized

A school's IT budget is usually set once a year and answers to a board, not a flexible line item you can renegotiate mid-year when a vendor raises prices.

The data is a minor's, and the rules are federal

Student education records and anything touching a child under 13 online fall under FERPA and COPPA specifically — not general-purpose "handle data responsibly" language.

1:1 device fleets are large relative to staff headcount

A district with a few hundred students often has a few hundred Chromebooks or iPads and a tiny IT team — device-to-technician ratios most MSPs' commercial clients never approach.

The maintenance calendar is the academic calendar

Patch windows, re-imaging, and infrastructure work happen around a school year, not a standard business week — summer is a deployment season, not a slow one.

What that means inside Nexus

Not a separate education product — the same platform, used the way we use it ourselves.

FERPA/COPPA posture tracking is one of the frameworks the compliance module tracks natively — not a request we'd have to build from scratch for a school client.
Asset & device management handles check-out/check-in at 1:1 fleet scale — the same lifecycle tracking a 200-Chromebook rollout needs, not a feature designed only for a 30-laptop office.
The client & staff portal gives non-technical school staff — often the actual day-to-day contact, not a dedicated IT director — a simple way to submit and track a ticket.
Consolidation matters even more against a fixed, board-approved budget than an unpredictable commercial one — one platform is a number you can actually defend at a budget meeting.

Honest about scope

We're not pitching an "education edition."

Nexus is one platform, not a vertical-specific fork — FERPA/COPPA is one framework among the several the compliance module tracks, alongside SOC 2, NIST CSF, HIPAA, PCI-DSS, and ISO 27001. What's genuinely different for a school client is that we built and use this platform against real K-12 workloads ourselves before ever describing it as ready for yours.

Run your school clients on the platform we run ours on.

Join the design-partner cohort — we'll talk through what a district or private-school client actually needs, not a generic pitch.