A cleaner desktop for people who still care about computers.
Rukh OS is a Linux-based desktop experience designed to feel familiar, stay fast, reduce bloat, and give users more control without making them live in a terminal.
Control center
Clean defaults
Files
Local first
Settings
Clear controls
Terminal
Power ready
Updates
Readable notes
Because the desktop should feel intentional again.
Because most desktop software has become bloated, noisy, and hostile to normal users. Rukh OS is an attempt to make the desktop feel clean, fast, and intentional again.
Linux-based. Familiar by design. Built to stay out of your way.
Familiar workflows
Desktop patterns that feel approachable without imitating a competing OS.
Low bloat
Default apps and services selected for usefulness, clarity, and restraint.
Privacy-respecting defaults
Settings that favor user control and plain-language choices.
Security-conscious foundation
A Linux base with a careful direction for permissions, updates, and storage.
Common file support
Practical workflows for documents, media, archives, and web work first.
VM-friendly direction
Compatibility explored through virtualization, layers, and curated alternatives.
Polished visual system
A desktop that feels intentional again, from shell to settings.
Power-user escape hatches
Terminal access and advanced controls without forcing everyone into them.
Practical compatibility, not magic.
Rukh OS is designed around practical compatibility, not magic. The goal is to support common document, media, archive, and web workflows first, with Windows application support explored through compatibility layers, virtualization, and curated alternatives.
Documents & media
Common file formats, archives, and day-to-day desktop workflows are the first priority.
Web apps
Modern browser workflows matter, because much of normal computing now lives on the web.
Linux apps
Native Linux software is the natural starting point for the application ecosystem.
Windows compatibility paths
Compatibility layers may help some workflows, but they are not magic and will be tested honestly.
Virtual machines
Virtualization remains a practical path for workflows that need a different operating environment.
Cloud and sync services
File sync and web-backed productivity need clean integration without hidden background clutter.
No mystery bloat. Clear updates. Real release notes.
Sane defaults
Start from conservative behavior and make tradeoffs clear.
App permissions direction
Permission surfaces should be legible, practical, and hard to miss.
Encrypted storage direction
Storage protection is part of the roadmap, not a decorative bullet.
Clear updates
Updates need visible notes, minimal drama, and no mystery bundles.
From concept to public preview.
Phase 1
Concept prototype
Define the base product shape, shell principles, and desktop interaction model.
Phase 2
Design system
Document app surfaces, controls, panels, color, motion, and accessibility standards.
Phase 3
Installer research
Explore approachable install paths without hiding important system decisions.
Phase 4
App compatibility testing
Test common file, web, Linux app, compatibility layer, and VM workflows.
Phase 5
Beta image
Prepare an early image for qualified testers and feedback loops.
Phase 6
Public preview
Open a broader preview once quality, compatibility notes, and security docs are ready.