Hybrid Cloud for K-12: How to Decide What Stays On-Premises and What Moves to the Cloud
Your student information system. Your payroll records. Your LMS. Every one of them is sitting somewhere right now.
The question is whether anyone actually decided where — or whether it just ended up there.
According to EdTech Magazine's recent look at hybrid cloud in K-12, that placement decision comes down to five specific factors, and districts that treat it as a judgment call rather than a structured evaluation tend to pay for it in cost, uptime, or exposure.
"The decision is not guesswork"
Most districts today run a hybrid cloud environment whether they planned one or not. Some data and applications live on servers in a closet or a district data center; others live with public cloud providers. The mix accumulates over years of individual purchasing decisions, and very few districts ever go back and audit the whole picture.
Amy McLaughlin, project director of the CIRCUITS committee at CoSN — the group that works with districts on making smart, future-proof decisions about IT infrastructure — puts it bluntly:
"The decision is not guesswork. It is a structured evaluation that looks at bandwidth capacity, uptime requirements, security needs, staffing and the nature of the application."
That is the whole framework in one sentence. Five factors: bandwidth capacity, uptime requirements, security needs, staffing, and the nature of the application itself. Every system in your district can be run through it.
What's actually on the table
This is not an abstract infrastructure debate, because of what these systems hold:
Student information systems — personal student data and transcripts
Learning management systems — class curricula, assignments, and testing records
HR and payroll systems — your staff's compensation data
Identity and access management — the keys to everything else
Email and collaboration systems — years of institutional communication
Get the placement wrong on any of these and you are not looking at an IT inconvenience. You are looking at a data exposure, a payroll outage, or a week where teachers cannot reach their gradebooks.
Factor one: cost, and what "cheaper" actually means
Districts increasingly use cost analysis and cost management tooling to optimize cloud spending — and the major providers, Amazon Web Services and Microsoft Azure among them, offer help analyzing those costs directly.
But the decision is not uniformly pointing one direction. Some districts are off-loading applications and processing to virtual servers. Others are pulling everything back to on-premises data centers. The determining question is whether your district needs consistent, predictable processing power and storage, or whether it can use — and trust — cloud storage and virtual CPUs and GPUs.
Software as a Service changes that math again. As McLaughlin notes:
"SaaS plays a major role because it off-loads maintenance, improves accessibility and reduces the burden on local IT teams."
That last clause is the one that matters most for districts running lean. If your IT department is a handful of people covering every building you operate, offloading patching and maintenance is not a line item — it is staffing capacity you get back.
Factor two: security is now an architecture decision
After several years of ransomware and other attacks hitting school districts hard, security has stopped being something you bolt on after choosing where a system lives. It is now the thing that decides where the system lives.
"Security is no longer only a technical issue. It is a strategic one that influences whether a system stays on-premises, moves to the cloud or becomes a managed service," says McLaughlin. "Cloud services can help because many offer enterprise-grade security, built-in redundancy and advanced threat detection. Districts still need strong data governance and clear contractual protections."
Read that last sentence twice. Moving to the cloud can buy you better security infrastructure than a district could realistically build alone — but it does not transfer responsibility. Governance and contract language stay on your side of the table.
Factor three: your network has a vote
This one is simple, and it overrides everything above.
"Cloud services only work if the network can support them and if a district has reliable internet access and capacity," McLaughlin says.
If your bandwidth cannot carry a cloud service that requires intense traffic, the cost analysis and the security comparison do not matter. The answer is on-premises until the network changes. Alongside capacity, the article names three more considerations that round out the evaluation: staffing levels and training, how critical the system is, and how much scalability and resiliency you actually need.
What this looks like on the ground
Butler Tech, a vocational high school in Ohio, worked with Nutanix to implement an on-premises cloud computing system — a deliberate move in the opposite direction from the default "everything to the cloud" assumption.
Robert Wilkinson, a systems architect there, explains the reasoning. His priority is "securing the data and trying to avoid the unintentional leaks of student and staff data."
"This is the biggest driver for me and a big reason to keep it on-premises as much as possible. It is also a known cost per year."
That closing phrase — a known cost per year — is worth sitting with. For a public institution building a defensible budget, predictability can be worth more than a lower theoretical cost that comes with variable billing attached to it.
What leaders should actually do
Ordered by how quickly you can act on them.
Inventory what you have and where it lives. You cannot evaluate placement until you can list every major system and say, in one line each, whether it is on-premises, in the cloud, or a managed service. Most districts have never written this down.
Run the five-factor test on each one. Bandwidth capacity, uptime requirements, security needs, staffing, nature of the application. Score them honestly. The systems where your current placement contradicts the evaluation are your priority list.
Get a real cost picture, not a vendor estimate. Use the cost analysis tooling the major providers offer, then compare it against what Butler Tech's Wilkinson called a known cost per year on the on-premises side. Compare like for like, including staff hours.
Pressure-test the network before you move anything. Reliable internet access and capacity is a precondition, not a detail to sort out during rollout. If the network cannot carry it, the migration fails regardless of how good the business case looked.
Put governance and contractual protections in writing. Enterprise-grade security from a cloud provider does not cover you without strong data governance and clear contract terms. This is the slowest item on the list and the one most often skipped.
As McLaughlin summarizes the current moment: the tools available to manage cloud computing are better, but "the decisions are harder. Districts need clear frameworks, strong vendor management and a long-term strategy to make cloud adoption successful."
Get this in your inbox every week
The YOSS Advantage is our weekly newsletter for K-12 leaders — a curated read on AI, EdTech, and the policy shifts actually affecting how districts operate. No filler, no jargon, and nothing you need an IT degree to follow. If this breakdown was useful, the newsletter is where it came from.
Subscribe free at https://subscribe.learnyoss.com/ and get the week's most important K-12 technology stories delivered every week.
Source & credit
This post summarizes and builds on "Hybrid Cloud for K-12: What Should Live Where?" by Joel Keller, published by EdTech Magazine on September 1, 2026. Keller spent more than a decade working in IT before becoming a full-time journalist, and has written for The New York Times, Parade, and others.
All quotations, the five-factor evaluation framework, and the Butler Tech example come from Keller's reporting and his interviews with Amy McLaughlin, project director of the CIRCUITS committee at CoSN, and Robert Wilkinson, systems architect at Butler Tech. The "what leaders should actually do" section is our own interpretation for district leaders. Our thanks to Joel Keller and EdTech Magazine for the original reporting.
