Framework’s Next Gen event: modular laptops and the push for machines you can actually fix

Framework ran its **Next Gen** launch on April 21, 2026, live from San Francisco and on YouTube. If you only skimmed the headlines, you might file it under “another laptop drop.” The more interesting story is the company doubling down on a pitch that has felt unfashionable for years: **computers you can open, upgrade, and keep running** instead of treating them as sealed appliances.

Ahead of the stream, Framework also opened shipping to **New Zealand, Norway, Switzerland, and Singapore**. That is a small geography list on paper, but it matters for anyone who has wanted their gear without importing through a friend in the US. The event page framed the whole thing as much about philosophy as silicon: repair, ownership, picking your OS, and pushing back on the idea that personal machines are just thin clients for someone else’s cloud.

Whether that resonates with you probably depends on how many laptops you have retired with a perfectly good screen and a battery or board you could not replace without a heat gun and prayer. The industry trend for a long time was thinner, soldered, harder to service. Framework’s bet is that a meaningful slice of buyers, including businesses, will pay for the opposite when the execution is credible.

**Modular hardware sounds simple** until you try to ship it at volume. Connectors wear, tolerances stack, thermals get weird when users mix generations of boards and batteries. Framework has already been through several product cycles with the Laptop 13, the 16, and the small desktop, so this launch is less “hello world” and more “we think we know how to run this playbook.”

For developers and anyone running Linux daily, the pre-show chatter (distro logos in teasers, community in the room) was the obvious hook. First-class Linux support still is not the default from big OEMs; it is usually a forum thread and a wiki. A vendor that treats alternative OSes as expected rather than tolerated removes a lot of friction from a fleet purchase.

Procurement people rarely get romantic about right to repair, but they do care about **asset life**, spare parts, and whether IT can swap a failed part without sending the whole unit to a depot for two weeks. Modular designs, when parts stay available, can bend those curves. The catch is always parts availability and firmware policy two years out, not the day-one review.

Sticker price versus **total cost** is the argument modular vendors need to win. A machine that costs more upfront but skips a full refresh because you dropped in RAM, storage, or a new mainboard can win on spreadsheets. The same math breaks if modules are scarce, priced like jewelry, or incompatible across generations. Buyers should ask about those specifics, not just the keynote spec sheet.

Sustainability claims follow the same rule. Replaceable parts can mean less e-waste per seat, but only if people actually repair instead of shelving dead hardware. Corporate reporting on circularity is getting sharper; “recyclable” boxes are not enough. Hardware that stays in service longer is easier to defend in an audit than a sleek brick that failed at month eighteen.

Incumbents do not have to copy Framework one for one to feel pressure. Apple’s recent repair concessions, more visible parts programs elsewhere, and louder buyer questions about longevity all pull in the same direction. The shift often starts with power users and small teams, then shows up in RFP language once someone proves the model at scale.

If you are evaluating gear for a team, a boring checklist beats a manifesto: MTTR, regional spare stock, BIOS/firmware update cadence, Linux QA on the distros you run, battery replacement steps, warranty text on self-service, and whether the upgrade path for storage and RAM is documented or “ask sales.” Launch streams are fun; depot tickets are where truth lives.

After the stream, the useful signal is not only what shipped but whether **reviews six weeks later** still say “I fixed this myself” without caveats. Framework’s earlier machines already have enough mileage in the wild that skepticism is healthy but not dismissive. This event is a chance to see if they extend the modular story without breaking the interfaces people already bought into.

The PC market is tired of disposable ultrabooks that age out on one component. Something has to give between supply-chain cost pressure and buyers who want a machine to last a full depreciation schedule. Framework is betting that “ownable” hardware is a product category, not a hobby. April 21 was the next chapter in that bet, not the epilogue.

Worth reading alongside the stream: Framework’s own blog and event page for times and regions, and hands-on writeups once press and community members have units. Specs and SKUs will settle quickly; the longer story is whether this generation stays supportable when the next board ships.