Framework's 10G Ethernet Expansion Card Brings Multi-Gigabit Networking to Its Modular Laptop Line

Framework has announced a 10G Ethernet Expansion Card for its modular laptop lineup, delivering 10 Gb/s multi-gigabit wired networking via the company's standard Expansion Card slot system, with plug-and-play support out of the box (frame.work/nextgen).
The card slots into any of the Expansion Card bays that define Framework's modular design, converting one of those ports into a full 10GbE interface. No driver installation dance, no firmware provisioning ritual — it works on insertion. For engineers and power users who have spent years watching laptop makers treat wired networking as an afterthought, this is a direct answer to a specific and persistent complaint.
10GbE on a laptop matters more now than it would have a few years ago. NAS enclosures with 10G uplinks have moved into prosumer price territory. High-density Wi-Fi 6E and 7 access points are common in offices, but wired throughput still wins for sustained large-file transfers, low-jitter audio workstations, and local AI inference pipelines pulling multi-gigabyte model weights off network-attached storage. Wireless headroom has outpaced the 1GbE copper that most docked laptops still rely on. A 10G interface closes that gap without requiring a Thunderbolt dock that may or may not negotiate its NIC controller cleanly with a given kernel or firmware stack.
Framework's Expansion Card architecture is the enabling factor here. Because every card is a self-contained module terminating into USB4/Thunderbolt, adding a 10G NIC is essentially an electrical and mechanical integration problem rather than a system-design compromise. The laptop's mainboard does not need a dedicated 10GbE PHY baked onto it — a design choice that keeps the base platform cost down while letting users who actually need the bandwidth slot it in. Users who do not need it pay nothing for it, in BOM terms or in heat budget.
The plug-and-play framing is worth taking seriously rather than treating as marketing language. Cross-platform driver support for 10GbE controllers has historically been uneven. Aquantia/Marvell AQtion adapters — the chipset family that underpins most consumer and prosumer 10G adapters — had patchy Linux kernel support for years before mainlining improved. If Framework has done the work to ensure the card enumerates cleanly across Windows, macOS (on any Intel-based Framework variant), and Linux without manual intervention, that is a genuine UX achievement for a niche that has long required some tolerance for terminal troubleshooting.
Looking at what this means for Framework's broader product positioning: the company has consistently built its value proposition around repairability and configurability, and each Expansion Card release either deepens that story or tests its limits. A 10G card is squarely in the "deepens" column. It targets a segment — developers, data engineers, on-site AV professionals, network administrators — that buys premium hardware and has specific, articulable reasons to want both the portability of a laptop and the throughput of a workstation NIC. That overlap is smaller than the mainstream consumer market, but it is also the segment least likely to tolerate compromises.
The Expansion Card slot does impose a physical constraint worth naming: 10GbE typically runs over RJ-45, and RJ-45 connectors are thicker than the slim profile most modern laptops target. Whether Framework has accommodated this with a slightly protruding card design — as it has done with its HDMI and DisplayPort cards — or with a different connector approach is not specified in the current announcement detail. That mechanical answer will matter to users who routinely work docked versus those who only occasionally plug into 10G infrastructure.
Framework has been methodical about expanding the Expansion Card ecosystem over time, adding storage, display output, and charging options across successive generations. The 10G Ethernet card extends that logic into professional networking territory. For the subset of Framework users already running their machines as primary workstations, it removes one of the last hardware arguments for keeping a dedicated desktop or tower in the loop.