Google announces Chromebook "replacement"
Community
Google just announced something that could reshape how we think about our device fleets for the next decade: the Googlebook, a new laptop line built from the ground up around Gemini AI, running a merged Android-ChromeOS foundation instead of the ChromeOS we've been managing for years.
If you're like most of us, Chromebooks are the backbone of your 1:1 program. They've been reliable, affordable, and honestly pretty easy to manage at scale through the Admin Console. So when Google signals a platform shift this significant, it's worth pausing the refresh cycle conversation to figure out what we're actually buying into going forward.
Here's what we know so far. Google is calling these devices "Googlebooks," and the core pitch is that Gemini intelligence is baked in at the OS level, not bolted on as an app or extension, but foundational to how the device operates. The underlying software merges Android and ChromeOS, which is something Google has been quietly working toward for a while. That convergence has real implications: app compatibility, MDM workflows, and the administrative tools we've built our management processes around could all look meaningfully different on these new devices.
What we don't know yet is just as important. Pricing, education-specific SKUs, and what happens to existing Chromebook management infrastructure are all still open questions. The vendor hype around "AI-first" hardware is loud right now, and Google is clearly positioning this against what Apple and Microsoft are doing in the AI PC space. That competitive pressure is real, but it doesn't automatically mean Googlebooks are the right next step for our schools, especially if your district is mid-refresh or working with tight capital budgets.
The honest advice right now is to hold your questions and not let a vendor briefing push you into a premature commitment. Get on your Google rep's calendar, ask specifically about education pricing and ChromeOS policy continuity, and loop in your curriculum team before anyone starts talking purchase orders.
Bottom line: don't pause your current refresh plans over this announcement, but do start an internal conversation now about your device strategy timeline so you're not making a reactive decision when procurement pressure hits.
Worth watching: If Android and ChromeOS are truly merging under the Googlebook umbrella, the long-term question isn't just about hardware, it's whether our existing management and compliance infrastructure scales gracefully into whatever Google's unified platform actually becomes.
Featured Articles
Canvas owner reaches ‘agreement’ with threat actors after data breach
News & Industry · 1 min read
If you use Canvas, this one hit close to home. Instructure, Canvas's parent company, reportedly paid a ransom to ShinyHunters after the cybergang breached their systems twice in roughly a week, causing widespread disruptions across K-12 and higher ed. The FBI strongly discourages ransomware payments, and cybersecurity experts say there's simply no guarantee the stolen data was actually destroyed, regardless of what "shred logs" say. For our schools, this is a good moment to revisit your incident response plans and have an honest conversation with your LMS vendor about their security posture — because when a platform touching 275 million users gets hit twice in eight days, we're all affected.
Worth watching: As vendors become the soft underbelly of district cybersecurity, the question of contractual accountability in ed tech agreements is only going to get louder.
5 Ways K–12 IT Leaders Can Prepare for Enrollment Declines
News & Industry · 1 min read
With 40 states projected to see enrollment drops by 2031, a 5% decline nationally, tighter per-pupil funding and school consolidations are already reshaping how we plan for tech infrastructure. EdTech Magazine talked to three ed-tech leaders who laid out five practical strategies for protecting essential tools when budgets start shrinking alongside student counts. If you're having those "what do we cut first" conversations with your finance team or board, this is a solid framework to bring to the table, the advice centers on getting proactive now, before the funding gap forces your hand. Worth watching: how enrollment-driven budget pressure may accelerate the consolidation of district tech stacks in ways vendor contracts aren't currently built to accommodate.
Latest Canvas Attack Shows Schools Still Struggle With Cybersecurity
News & Industry · 1 min read
Hackers breached Instructure's Canvas platform through a "free for teacher" account, with the group ShinyHunters claiming to have stolen 275 million records from roughly 9,000 institutions worldwide, including student and teacher emails, usernames, and enrollment data. For our IT teams, this one stings because the entry point wasn't some sophisticated zero-day exploit; it was a low-barrier teacher account, the kind we hand out constantly without a second thought. Instructure says it negotiated return and destruction of the stolen data, but notably didn't disclose what that deal cost them — and this is their second breach within a year.
As districts deepen their edtech dependencies post-pandemic, vendor security practices deserve the same scrutiny we give curriculum adoptions.
CISA Adds One Known Exploited Vulnerability to Catalog
Cybersecurity · 1 min read
CISA just added CVE-2026-20182 : a Cisco Catalyst SD-WAN Controller authentication bypass vulnerability to its Known Exploited Vulnerabilities catalog, meaning attackers are actively using this one in the wild right now, not just theoretically. If your district runs Cisco SD-WAN for connecting campuses or managing network traffic, this needs to move up your priority list today. CISA has already issued Emergency Directive 26-03 with specific hunt and hardening guidance, so the remediation roadmap exists, your team just needs the runway to act on it.
SD-WAN adoption has grown fast in K12 as districts consolidated campuses post-pandemic, which means our sector's exposure to this class of vulnerability is quietly higher than most of us have audited for.
Tech Tip of the Week
Mosyle vs. Jamf — choosing the right Apple MDM for your fleet size
Fleet size matters less than your staffing model when choosing between Mosyle and Jamf.
Mosyle is built for lean teams. The interface assumes you're not a dedicated Apple admin — and that's intentional. Built-in security baselines, setup wizards, and straightforward per-device pricing keep the learning curve manageable. If you're running under 2,000 devices with limited IT staff, Mosyle is likely your answer.
Jamf Pro makes sense when you have dedicated Apple admins who need granular policy scoping, complex automation, or deep integrations with tools like ServiceNow or Azure AD. Expect real onboarding time -- budget six to eight weeks minimum.
Before any vendor demo, track your actual weekly hours spent on device management. That number tells you more than any feature matrix.
One thing to watch: Apple has been quietly adding MDM-like capabilities directly into Apple Business Manager. The gap between platforms is narrowing. Whatever you choose today, stay close to Apple's release notes -- the landscape is shifting faster than most renewal cycles.
Pass This Along
If a colleague or coworker in K12 IT would find this useful — forward it. They can subscribe free and get their own copy every Friday.