Independent OS core
Frames owns its kernel direction, process and syscall model, hardware interfaces, services and native executable path instead of inheriting a Linux kernel underneath.
FRAMES // INDEPENDENT COMPUTING PLATFORM
A new perspective on computing.
Frames is an independent operating system and developer platform being built from the kernel upward around Nexus. The goal is a coherent computing platform where the kernel, native applications, recovery, storage, security, development tools and intelligent interaction are designed to work together instead of being bolted on later.
Independent coreNexus-nativeEvidence-firstPrivacy-minded
0.9.62authoritative certified GUI baseline
12 / 12integrated desktop phases
1280×800actual QEMU framebuffer capture
70 / 70inherited core runtime markers
WHAT FRAMES IS
More than a desktop. A coordinated computing stack.
Frames is being developed as its own operating-system platform rather than as a Linux distribution or a themed layer over another OS.
Nexus-native development
Nexus is the systems language and toolchain developed alongside Frames. Nexus SDK 6.10.0 now provides standalone build, package, signing, diagnostics and native Frames development workflows.
Recovery as infrastructure
HelixFS is planned around snapshots, rollback, integrity and application capsules so updates, development and experimentation can become safer and easier to reverse.
Intelligent interaction
Frames Voice and Frames Identity are planned as permission-controlled platform services for speech, biometric authentication and secure system interaction—not unrestricted AI control.
APPLICATION EXPERIENCEDesktop · Native Apps · Voice · Identity · Developer Center
PLATFORM SERVICESFEX · Updates · Security · Networking · HelixFS
CORENexus · Frames Kernel · Drivers · Hardware
ACTUAL FRAMES GUI RUNTIME
The desktop is now running under Frames in QEMU/OVMF.
Frames 0.9.62 v72-r1 passed the final external integrated GUI aggregate under v72-r1-integrated-gui-r6. The desktop reached Phase 12, the kernel reached ready state, and the accepted 1280×800 framebuffer became the current authoritative runtime proof.
ACTUAL QEMU/OVMF RUNTIME CAPTURE · FRAMES 0.9.62
Integrated Frames Desktop
This image is runtime evidence, not concept artwork. The next validation step is a controlled physical-hardware GUI boot, initially using removable/external test media while Frames 1.0 remains unpromoted.
GRAPHICAL PRODUCT DIRECTION
Where the certified runtime is headed next.
The runtime capture above shows what Frames actually renders today. The larger concept screens below remain design targets for the polished consumer desktop, Identity and future integrated system experience.
CONCEPT · FUTURE GRAPHICAL DESKTOP
Frames Desktop
A calm, information-rich workspace with native system health, HelixFS recovery, Frames Voice, Nexus development tools and a focused dock—designed to make the operating system itself feel like one integrated product.
CONCEPT · FRAMES IDENTITY
Voice + biometric unlock
A future lock screen where voiceprint, face, fingerprint and step-up authentication can work through the Frames Identity service while keeping sensitive authentication policy local to the machine.
DEVELOPMENT POSITION
Integrated GUI certified. Physical desktop boot is next.
The current public status separates the externally proven QEMU/OVMF desktop from the still-unpromoted Frames 1.0 consumer release.
CERTIFIED BASELINEFrames 0.9.62 v72-r1
Desktop Polish, Accessibility & Integrated GUI Regression; final external certification PASS and authoritative baseline promotion.
NEXT VALIDATIONPhysical GUI boot
Controlled UEFI boot on real hardware from dedicated removable/external test media.
PUBLIC RELEASEFrames 1.0
Not promoted. Hardware breadth, persistence, recovery and release hardening still remain.
Core runtime + safety foundation70/70 runtime markers, 8/8 stress categories, Gates 1–8 and 2–96 CPU SMP history retained
COMPLETENative application platformFEX launch, deterministic FAPP packaging and native packaged-application loading proven
COMPLETEHelixFS read-only integrationPhases 1–3 include block-backed reads, nested traversal and multi-block file proof
COMPLETEFrames graphical desktop trainGraphics, windows, input, shell, GUI FAPP, themes/fonts/icons, Files, Settings, notifications, session shell and accessibility integrated through Phase 12
CERTIFIEDPhysical GUI validationNext: boot the same Frames graphical stack on a sacrificial laptop/external SSD test configuration
NEXT1.0 product hardeningPersistent system experience, broader hardware/driver coverage, installer/recovery/update maturity and consumer polish
ROADMAPEvidence-first rule: concept artwork remains labeled separately from actual runtime captures, and Frames 1.0 is not promoted simply because the GUI now boots successfully in certified virtualization.
ROAD TO 1.0 · CONSUMER FIRST
Make Frames a computer people can actually use.
The 1.0 roadmap now treats the default first-party software suite, native hardware/input coverage and a free personal/home preview as core engineering work. Developer tooling continues in parallel, but home users should not receive an empty desktop built only for developers.
Complete first-party suite
Browser, Files, Edit, Writer, Paint, Calculator, Photos, Media, Document Viewer, Terminal, Settings, Monitor, Capture, Archive, Apps and Help are now part of the 1.0 product target.
Free Frames Home Preview
Personal/home preview use is planned to be free, expanding the number and variety of real machines that can help harden Frames before broader release.
Opt-in compatibility evidence
Users choose Off, Basic or Extended diagnostics. Compatibility reports focus on hardware, crashes and performance—not personal documents or browsing history.
BUILT DIFFERENT
Six technologies. One coordinated platform.
The long-term value of Frames comes from multiple layers being designed together rather than assembled from unrelated products.
Nexus
Native systems language and Nexus SDK 6.10.0 toolchain for the kernel, FEX/FAPP applications, signing, interop and developer workflows.
HelixFS
Native 64-bit filesystem roadmap focused on integrity, snapshots, rollback, recovery and modern storage.
Frames Voice
Local-first speech, conversational assistance and capability-mediated commands.
Frames Identity
Multimodal biometric authentication, liveness checks and secure step-up authorization.
Compatibility
Future isolated Windows and Linux compatibility environments at the platform edge.
Frames Lab
Future sandboxes, snapshots, debugging, profiling and reproducible test environments.
WHY FRAMES
Hard technology first. Product experience next.
Frames began with boot, kernel, userspace, storage and certification rather than presenting a polished desktop before the underlying system existed. The next step is converting that technical foundation into an everyday home-user experience while the developer ecosystem continues to mature in parallel.
01Independent stack
Kernel, Nexus toolchain, FEX applications and future native storage evolve together.
02Consumer + developer flywheel
A free usable Home Preview can expand compatibility evidence and the installed base that gives Nexus/FAPP developers a reason to build.
03Evidence culture
Claims are gated by reproducible builds, runtime evidence and fail-closed certification.