QRX OS ONE
The Amiga-inspired operating environment built around QRXDesktop: familiar workflows, modern ambitions, multiple application worlds and a unified interface.
Amiga soul. A new kind of freedom. QRX OS One connects the spirit of AEROS with the ambition to run software across operating systems and CPU architectures—powered by ARMithlon, QRX68, QRX86 and the imagined QRX68100.
AEROS once fused the Amiga-like AROS experience with the vast Linux ecosystem. QRX OS One is its spiritual successor: one desktop, many worlds.
The dream isn't to choose between old and new. It's to make them work together—AmigaOS 3.x and AROS 68k heritage, Windows and Linux applications, future PowerPC/x64/ARM translation, local-first AI and optional cloud services.
A desktop. An execution engine. A processor architecture imagined for the next generation of Amiga-inspired computing.
The Amiga-inspired operating environment built around QRXDesktop: familiar workflows, modern ambitions, multiple application worlds and a unified interface.
The ARM-hosted experiment carrying the Armitage-of-Amiga spirit into the Apple Silicon era: virtual 68k hardware, translation engines, graphics bridges and developer tooling.
A fictional dual-core 68040-inspired processor, with a legacy single-core personality and an extended QRX mode designed around future JIT workflows.
A closer look at the parts that make QRX different. Every card marks whether the capability has a prototype today or remains a target.
Classic HUNK loading, 68040 execution paths, AmigaDOS/Exec/Intuition compatibility experiments and interactive window-event tests.
PE32 and Linux ELF32/i386 execution experiments with Windows-API bridges, interpreter work and restricted JIT prototypes.
An existing Amiga-like desktop with files, icons and double-click routing—preserved rather than replaced by another GUI.
Direct directory sharing with read-only defaults, controlled writes, persistent QRXFS storage and optional disk-image paths.
Virtual board memory, expandable guest RAM, host-aware defaults and mapped devices for storage, timers, input and graphics.
Framebuffer and GPU bridge experiments with Metal/Vulkan-facing components; a finished native AROS display driver remains open.
Two virtual 68040-like contexts, single-core legacy profile, experimental scheduler and JIT-oriented cache ideas.
A full 68040 CPU core is being connected to QRX68; real FPU, exception and cross-platform end-to-end coverage still need validation.
Additional guest architectures, runtime dispatch and OS-level compatibility layers are part of the long-term design.
Offline-capable assistance for files, legacy development, code conversion, accessibility and workflows is the local-first goal.
Opt-in synchronization, collaboration, backup and compute services—without turning the local desktop into a mandatory cloud client.
A community-minded, free-to-use software goal with voluntary Patreon support. External components retain their own licenses.
Select a layer to explore the architecture, from the AROS-compatible desktop to the emulators and the optional intelligence services.
QRXDesktop and the Amiga-like experience act as the visual home for applications across eras.
Illustrative architecture, not a verified universal compatibility claim.
A playful, interactive concept of the QRXDesktop experience. Click the icons; imagine the comfort of the Amiga with a much bigger application universe.
One click should choose the right runtime—not force you to choose the right computer. Some paths exist experimentally; others are ambitious future targets.
QRX68 combines 68k HUNK execution with an expanding AmigaOS library compatibility layer. Interactive tests exist; broad real-application support remains in development.
ALPHA / IN PROGRESSQRX86 explores x86 instruction translation, Windows API bridging and Linux userspace support. Real-world compatibility is still limited.
ALPHA / IN PROGRESSPowerPC guest execution and operating-system bridges are roadmap targets; they are not finished or broadly usable today.
ROADMAPA longer-term dream: unify additional instruction sets through translation, isolation and operating-system API layers.
ROADMAPDifferent technologies, different strengths. These are architectural comparisons—not fabricated speed benchmarks or claims that prototypes already outperform real hardware.
Local-first AI as a system companion. Cloud services when you want them, not because your desktop requires them.
The design goal: private on-device assistance for files, code, workflows and accessibility, with optional QRX OS One Cloud services for sync, collaboration and heavier workloads. These services are a product direction, not a launched offering.
HELP BUILD THIS FUTURE ↗Find my old Amiga project and prepare it for QRXDesktop.
Search local files → inspect formats → suggest a compatible runtime → keep you in control.
Transparent development matters. Here is the difference between what has been exercised in controlled tests and what is still being built.
Bootable firmware shell, HUNK loader, host-directory bridge and QRX68 library-call experiments.
Musashi integration, live 68k windows, AmigaOS HLE expansion and QRXDesktop launch path.
AROS on the virtual QRX board, drivers, virtual dual-core SMP and real end-to-end app tests.
Broader Windows/Linux support, PPC/x64/ARM translation and seamless application dispatch.
On-device AI services with optional account-based sync, compute and collaboration tools.
One coffee. One pizza. One month of making something wonderful possible.
QRX OS One is being developed with the ambition to keep the software free to use. A small monthly contribution on Patreon helps fund testing, tooling and development—and lets the community influence priorities through feedback and support. No purchase is required.
No. That is the long-term vision, not the current state. Several 68k and x86 components are experimental; PPC, x64 and wider ARM compatibility are future work.
No. It is a fictional, software-defined dual-core processor concept inspired by the Motorola 68040 and modern 68k development. It is not a commercial chip or an Apollo 68080 clone.
Their general compatibility has not been demonstrated. QRX68 provides tested subsets of AmigaOS APIs, but complex real-world applications still need further integration and testing.
They are planned product directions. Local AI integrations and cloud-connected services are not presented as launched features.
The goal is software that remains free to use. Patreon support is voluntary, helps fund development and gives the community a voice in what gets attention next.
QRX OS One builds on and draws inspiration from the independent, open-source AROS ecosystem. AROS remains a separate upstream project; QRX is not its official successor or replacement.