AI, SaaS, and EdTech Survival
Why the “SaaS Apocalypse” Isn’t the End of EdTech Software Providers
Phil Hill
April 01, 2026
Was this forwarded to you by a friend? Sign up, and get your own copy of the news that matters sent to your inbox every week. Sign up for the On EdTech newsletter. Interested in additional analysis? Upgrade to the On EdTech+ newsletter.
A longtime reader reached out recently with a request: to get my take on a HackerNoon article titled “The SaaS Apocalypse Is OpenSource’s Greatest Opportunity.” The article basically says AI is about to make most commercial SaaS irrelevant and that open source is finally poised to win big.
The implied question is how this might play out for EdTech platforms, which is a fair ask. The article (published March 16, 2026) argues that AI lowers the cost of writing code so dramatically that the economic case for proprietary SaaS collapses. Most commercial SaaS will become open source—not out of ideology, but pure economics. Maintainers who don’t embrace AI risk being forked or replicated from scratch. The piece frames this as open source’s “biggest opportunity in a generation,” while proprietary vendors face “an existential crisis.” Nearly a trillion dollars already wiped from software stocks in 2026 is cited as evidence.
I agree with large parts of the premise, but the conclusion—that easy AI coding means the value of SaaS software vendors (proprietary or hosted open source) essentially evaporates—doesn’t hold. Just as Ben Thompson recently argued in Stratechery about Microsoft and broader software survival, AI changes how code gets written, not why institutions pay for ongoing software services. Let’s break it down, starting with where the HackerNoon article gets it right.
Where I Agree: AI Is Reshaping Code—and Open Source in EdTech Needs to Wake Up
The core Thompson insight is spot-on in my opinion: AI (Claude Code, OpenAI Codex, GitHub Copilot, etc.) turns software development into a near-perfect match of probabilistic inputs and deterministic outputs.
The beauty of AI writing code is that it is a nearly perfect match of probabilistic inputs and deterministic outputs: the code needs to actually run, and that running code can be tested and debugged. Given this match I do think it is only a matter of time before the vast majority of software is written by AI…
This trajectory is real. Experienced engineers already admit (after the obligatory complaints about hype) that AI lets them ship features or entire apps they never would have tackled otherwise.
In the EdTech world, this should be a wake-up call for open-source communities—especially the ones that have grown complacent. Projects like Moodle, Sakai, and even Open edX have long relied on volunteer or grant-funded development cycles that move at academic speed. If a motivated developer (or a university IT team) can now use AI to spin up a custom learning environment or replicate core LMS functionality in weeks instead of years, the “we’ll get there eventually” mindset is no longer viable.
The HackerNoon piece is correct in that open-source maintainers who refuse to embrace AI risk being forked or simply outpaced. EdTech open source has a genuine opportunity here—if communities rethink funding models, governance, and contribution processes to move at AI speed. New economic models (sponsorships, enterprise support contracts, AI-assisted contribution bounties) could finally make sustainable maintenance realistic. I’m not dismissing that. In fact, I hope it happens.
But Here’s the Rebuttal: Coding Is Not the Same as Providing Software-as-a-Service
Where the article overreaches is the leap from AI makes initial coding cheap/fast to therefore SaaS vendors have no future. This ignores what software companies actually sell.
Thompson dismantles this exact bear case for software companies in general:
That, then, raises the most obvious bear case for any software company: why pay for software when you can just ask AI to write your own application, perfectly suited to your needs? Is software going to be a total commodity and a non-viable business model in the future?
I’m skeptical, for a number of reasons. First, companies—particularly American ones—are very good at focusing on their core competency, and for most companies in the world, that isn’t software. There is a reason most companies pay other companies for software, and the most fundamental reason to do so won’t change with AI.
Second, writing the original app is just the beginning: there is maintenance, there are security patches, there are new features, there are changing standards—writing an app is a commitment to a never-ending journey [snip]
Third, selling software isn’t just about selling code. There is support, there is compliance, there are integrations with other software…
Exactly. Most organizations (including universities) are not in the software business. They are in the education business. They do not want to become full-time AI prompt engineers, code maintainers, security patchers, compliance auditors (FERPA, accessibility standards, data privacy), integration managers, or model-updaters.
An LMS is not a one-and-done app, nor are other mission-critical EdTech platforms. The LMS is the digital front door to the institution: the place where courses are organized, grades are recorded, accessibility is enforced, data flows to the SIS/ERP, and thousands of faculty and students log in every day. AI can help generate features faster, but it does not eliminate the need for a reliable, supported, continually updated service.
This is the same logic Glenda Morgan and I used last December in “The Report of the LMS’s Death Is an Exaggeration.” We pushed back on Al Essa’s claim that the LMS category was dying because AI and new tools would replace it. Our counterpoint centered on two points.
In short, we believe the LMS is not dead or even dying; it is as crucial as ever, even if the product category needs to improve and better serve colleges and universities. [snip]
where we disagree is less about whether learning happens in an LMS and more about what it means to support learning at institutional scale.
In other words, the need being addressed by the modern LMS is not fundamentally coded features; rather, it is a service to enable institutional-scale learning to occur. AI lowers the barrier to entry for building an LMS-like tool; it does not lower the ongoing cost of running one at enterprise scale for a university.
What This Means for EdTech SaaS Providers (and Open Source)
The SaaS landscape in EdTech will change. Growth will come from fighting for adjacencies and expanding surface area rather than endlessly expanding the pie. In EdTech terms, expect more pressure on vendors (whether based on proprietary or open source software models) to integrate AI agents, expand into adjacent tools (assessment, analytics, content), and prove ongoing value.
But the value does not vanish. Universities will still pay for:
Security, uptime, and compliance that a DIY AI-generated fork cannot guarantee.
Support, training, and ecosystem integrations that keep the “never-ending journey” from becoming a nightmare.
Continuous updates as AI models evolve, standards change, and pedagogical needs shift.
Open-source communities can (and should) compete here by offering excellent hosted services or enterprise support layers. That is not a contradiction; it is the evolution that the HackerNoon article in part calls for. The winners will be those—whether proprietary or open-source—who treat software as a product and service, not just code.
Bottom Line
The HackerNoon article is right that AI is a seismic shift and that the EdTech open source community needs to rethink its assumptions and move faster. But it is wrong to declare SaaS dead. Most institutions will keep paying for the full service, because their core competency is teaching and learning and credentialing, not running an EdTech platform.
AI changes the economics of creation. It does not eliminate the economics of operation, support, or trust at institutional scale.
The main On EdTech newsletter is free to share in part or in whole. All we ask is attribution.
Thanks for being a subscriber.