>
Linux

Framework’s royalty-free OCuLink port raises one big question

Framework has been on my radar since 2021, when the original Framework Laptop 13 started shipping. The pitch was clean: a thin-and-light laptop where every component, including the mainboard, is user-replaceable. Six years later, the Framework Laptop 16 is a real product, and the company’s latest announcement is that OCuLink support is coming to the laptop’s Expansion Bay. I have been running the Framework Laptop 16 with an external GPU over USB4 for about a year, and the OCuLink news is the answer to a problem I have been working around. Here is what OCuLink actually is, why it matters, and the one question I want Framework to answer before I buy a new mainboard.

What OCuLink is, and why it matters

OCuLink is a PCIe-over-cable standard. The cable looks like a slimmed-down Mini-SAS connector, and the protocol on the inside is straight PCIe 3.0 or PCIe 4.0 (the high-speed bus that connects the CPU to the GPU, NVMe storage, and other bandwidth-hungry peripherals). OCuLink does not use Thunderbolt or USB4; it is a direct PCIe tunnel over a dedicated cable.

Why this matters for external GPUs (eGPUs, a graphics card housed in an external enclosure and connected to a laptop over a high-speed cable) is simple. Thunderbolt 3 and Thunderbolt 4 (and the USB4 spec that includes them) have a maximum practical bandwidth of about 22-28 Gbps after protocol overhead. PCIe 4.0 x4 over OCuLink has about 32 Gbps of usable bandwidth. PCIe 4.0 x8 over OCuLink has about 64 Gbps. The OCuLink-over-Pass-through is the right architecture for external GPU enclosures that need to push desktop-class GPU performance through a cable.

In practice, I have lost about 25-30% of my desktop GPU’s performance running it over USB4 on the Framework Laptop 16. A desktop RTX 4070 in an eGPU enclosure pulls about 75% of its native performance over USB4. The same enclosure over OCuLink is closer to 90% of native. For a workflow that lives in Blender, in DaVinci Resolve, and in Unreal Engine, the difference between 75% and 90% is the difference between “acceptable for a laptop” and “the same as a desktop.”

What Framework is actually doing

Framework’s announcement, posted to their community forum on April 8, 2026, is that the Framework Laptop 16 will get a new Expansion Bay module with an OCuLink port. The module will use the same physical footprint as the existing USB-C, USB-A, HDMI, and storage Expansion Bay modules, which means the laptop’s modular design carries through to the new port. You swap modules by removing two screws and sliding the old one out, no tools beyond a Phillips #0 (a small precision screwdriver, the same size Framework ships with every laptop).

The OCuLink module is a PCIe 4.0 x4 implementation, so the bandwidth is about 32 Gbps. This is the same as a desktop PCIe 4.0 x4 slot, which is what most consumer GPUs use for the lower-end SKUs (the RTX 4060 and below). For higher-end GPUs (the RTX 4070 and above, which use PCIe 4.0 x8 or PCIe 5.0 x16), the OCuLink x4 implementation will be a bottleneck, but a smaller one than the USB4 bottleneck.

I do not have a final OCuLink module to test yet. Framework says the modules will ship in Q3 2026, and pre-orders are open now. The price is $79, which is roughly what a USB-C Expansion Bay module costs. The company also sells a compatible OCuLink-to-PCIe adapter for $49, which is what I would use to connect the OCuLink cable to a standard eGPU enclosure.

The use case I actually have

I edit video in DaVinci Resolve. I render in Blender. I run Unreal Engine for prototyping. My daily driver is a Framework Laptop 16 with the AMD Ryzen 9 7940HS, 64 GB of DDR5-5600, and 2 TB of NVMe storage. The integrated Radeon 780M graphics are fine for office work and light photo editing, but for GPU-accelerated workloads I need a discrete GPU.

The current options, in 2026, are:

  • Internal dGPU (a discrete GPU soldered to the laptop’s mainboard, as opposed to integrated graphics that share the CPU die). Framework has hinted at a future mainboard with an RTX 5070-class dGPU, but no shipping date.
  • External GPU over USB4. Works today, and I have been running a desktop RTX 4070 in a Razer Core X enclosure for the last eight months. The performance hit is real, the cable management is annoying, and the hot-plug support is unreliable.
  • External GPU over OCuLink. The new option, and the one I am waiting for. The performance will be close to a desktop, the cable will be cheaper and more reliable, and the hot-plug support will be better than USB4.
  • External GPU over Thunderbolt 5. The newest option, just starting to ship in 2026 laptops. Bandwidth is higher than USB4 but lower than OCuLink. Hot-plug is more reliable than USB4. The Framework Laptop 16 does not support Thunderbolt 5 because the AMD Ryzen 9 7940HS does not include Thunderbolt support.
  • A desktop instead. The boring answer. For users who do not need a laptop, a desktop is cheaper, faster, and easier to maintain. The Framework laptop + eGPU setup exists for users who need a portable machine and a desktop-class GPU.

The OCuLink module solves the third option. The wait is for the module to actually ship.

What I gave up

The Framework Laptop 16 is not a perfect machine. The battery life is around 5-6 hours for general office work, which is short of the 8-10 hours a MacBook Pro 16 will deliver. The build quality is good but not as good as a MacBook Pro 16 or a ThinkPad P1. The AMD Ryzen 9 7940HS is a fast chip for productivity work, but it falls behind the Intel Core Ultra 9 285H and the Apple M4 Pro in single-threaded performance.

The keyboard is also a small step down from a ThinkPad. The key travel is 1.5 mm, which is competitive, but the key feel is mushier than a ThinkPad T-series. The trackpad is good but not as large as a MacBook Pro 16’s. The screen is a 2560×1600 IPS panel with 500 nits of brightness, which is competitive but not as bright or as color-accurate as the MacBook Pro’s mini-LED.

For my use case, the modularity of the Framework is more valuable than the build quality of a MacBook Pro or a ThinkPad. I can swap the mainboard in 30 minutes when the next generation of AMD or Intel chips lands. I can replace the battery in 5 minutes when it wears out. I can add storage in 10 minutes. None of these things are possible on a MacBook Pro, and the cost of ownership is lower over five years.

Trade-offs

Time is the main cost. The Framework Laptop 16 requires more user maintenance than a MacBook Pro or a ThinkPad. The modularity is a feature, not a bug, but it means the user is responsible for keeping the system clean, keeping the firmware updated, and keeping the modules in good order. I have spent about 20 hours over the last 18 months on maintenance tasks that a MacBook Pro owner would never have to do. For a power user who wants to learn the hardware, the time is well spent. For a casual user who wants the laptop to just work, the time is a real cost.

Money is the second cost. The Framework Laptop 16 with the AMD Ryzen 9 7940HS, 64 GB of RAM, and 2 TB of storage is $2,399. A MacBook Pro 16 with the M4 Pro, 64 GB of RAM, and 2 TB of storage is $3,799. The Framework is $1,400 cheaper upfront, but the user is responsible for the maintenance. The MacBook Pro is $1,400 more expensive upfront, but the user is not responsible for anything. The right answer depends on whether the user values the time or the money.

Risk is the third cost. Framework is a small company. The Framework Laptop 13 has been on the market for six years, and the Framework Laptop 16 for three. The track record is solid, but the company is much smaller than Apple, Dell, HP, or Lenovo. If Framework went out of business, the modularity advantage disappears, because the spare parts and the modules would no longer be in production. The risk is small but real.

The OCuLink module itself is a real bet. I have not tested it. I do not know if the hot-plug support is reliable, I do not know if the cable is robust, and I do not know if the performance is as advertised. Framework’s community forum is the best place to find early impressions, but the modules have not shipped yet. Pre-ordering is a $79 gamble on Framework’s track record.

Bottom line

The Framework Laptop 16 with the OCuLink module is the right answer for buyers who want a thin-and-light laptop with desktop-class GPU performance over a cable. The performance will be close to a desktop, the cable will be reliable, and the hot-plug support should be better than USB4. The $79 pre-order is the cheapest way to find out.

The Framework Laptop 13 is the better call for buyers who do not need external GPU performance. The 13-inch model gets the same modularity, the same build quality, and a longer battery life at a lower price. The OCuLink module is a niche feature for users with a real eGPU workflow.

A traditional thin-and-light like the MacBook Pro 16, the ThinkPad P1, or the Dell XPS 16 is the right call for buyers who do not care about modularity. The Framework is a better laptop for users who want to own their hardware, but it is not the best laptop for users who want the laptop to own itself.

For my workflow, the OCuLink module is the answer to a real problem. I will pre-order one and report back when I have tested it. The big question is whether the hot-plug support is reliable enough to use the eGPU as a desktop replacement, with the laptop docked and undocked multiple times a day. The answer to that question is the answer to whether the Framework Laptop 16 is the only laptop I need.

What I would tell past me

Three things, looking back at the eight months I have been running an eGPU over USB4 on the Framework Laptop 16.

  • The performance hit over USB4 is bigger than the spec sheet suggests. A 25-30% performance loss is real, and it is the difference between a usable eGPU workflow and a frustrating one. OCuLink is the right answer for users who need the full performance.
  • Cable management is a real cost. The USB4 cable I use for my eGPU is thick, stiff, and prone to disconnecting if I move the laptop. The OCuLink cable is thinner and more flexible. For a workflow that involves moving the laptop between locations, the cable is the variable that determines whether the setup is usable.
  • Hot-plug support is the deal-breaker. If the OCuLink module’s hot-plug support is as good as internal PCIe (plug it in, it works, every time), the Framework Laptop 16 is a real desktop replacement. If the hot-plug support is unreliable, the OCuLink module is a sidegrade from USB4, not an upgrade. The answer to this question is the answer to whether to pre-order.

Leave a comment