Framework-class laptop
Modular, upgradeable hardware as the practical baseline for a computer meant to last.
Open Personal Computing
Public direction · evolving in the openOwn the machine. Keep the future.
The destination is personal computing you can repair, understand, move between devices, and increasingly build from open parts. We do not need a secret product calendar to be clear about the direction.
Direction over secrecyPublish where we are going even when dates are unknown.
Compatibility over churnKeep useful parts working across generations whenever practical.
Ownership over lock-inYour data, tools, identity, memory, and machines should remain yours.
Working systems firstPrototype with available hardware instead of waiting for perfect openness.
Now
Use the best practical pieces.
Open Personal Computing starts with real machines people can use today. Framework is a practical laptop benchmark because the platform is modular and repairable. Repairable Android phones such as Fairphone are a useful phone benchmark. Linux, 3DVR Portal, 3DVR OS, servers, and RISC-V development boards let us build the software and operating model before every hardware layer is open.
Repairable phone
Android compatibility, replaceable parts, long support, and a path toward more user control.
Linux + 3DVR
Portal, 3DVR OS, personal AI, local tools, and server-first services form the owner-controlled layer now.
Reference platforms, not dependencies. We should be able to move between vendors as better repairable or more open hardware appears.
Next
Make the owner-controlled layer coherent.
The next milestone is less about inventing a processor and more about making the whole personal system portable: one identity, one knowledge layer, durable personal AI, documented interfaces, replaceable hardware modules, open repair information, and software that works without requiring a proprietary cloud.
3DVR Laptop
A long-lived shell with replaceable compute, storage, I/O, battery, display, and input wherever practical.
Open modules
Publish physical and software interfaces so parts can be substituted instead of forcing full-device replacement.
User-owned agent layer
Memory, permissions, automation, and model routing should survive changes in device or AI provider.
Later
Open the stack downward.
Once the surrounding system works, replace opaque pieces deliberately. RISC-V and FPGA prototypes provide a path toward compute we can inspect. Reproducible boards, open accelerators, documented firmware, repairable enclosures, and transparent sourcing move the project from “open software on good hardware” toward genuinely open personal computers.
RISC-V + FPGA
Prove small open systems before taking on custom silicon.
Reproducible hardware
Schematics, CAD, BOMs, test fixtures, firmware, and assembly knowledge that others can actually use.
Fewer black boxes
Trace materials and components, document closed dependencies, and steadily develop alternatives.
Long-term
A computing commons.
Laptop, phone, desktop, wearable, server, vehicle, and future interfaces become different forms of the same user-owned computing system. Hardware generations can change without erasing the person's software, knowledge, relationships, or ability to work. The goal is not one perfect 3DVR device. It is an ecosystem people can understand, repair, improve, and fork.
What we can promise now
Commitments, not vaporware.
Exact products will change. These principles should be harder to change than a product name or processor choice.
Publish the interfaces
Document APIs, protocols, mechanical assumptions, repair paths, and compatibility boundaries wherever licensing permits.
Preserve compatibility
Prefer adapters and upgrade paths over needless breakage. A new generation should not automatically make the last one trash.
Keep Linux first-class
Favor upstream-friendly drivers, ordinary tooling, documented boot paths, and systems users can administer themselves.
Let people leave
Data, memory, identity, and workflows should be exportable. Open Personal Computing should not become another lock-in strategy.
Repair before replace
Use replaceable batteries, storage, I/O, input, compute, and displays wherever the design can reasonably support them.
Show the direction
Keep this roadmap public and update it as experiments succeed, fail, or reveal a better route.
Build in public
The roadmap is part of the product.
People should be able to see what exists, what comes next, and what the project is ultimately trying to make possible.