Project Fallen
A custom ecosystem designed to bridge Arch Linux and Android through seamless connectivity, authentication, and developer-focused tools.
Origin
It all began with a simple question. I had Kali Linux installed alongside Windows, yet I rarely used it. That led me to ask: Why not?
The answer was surprisingly simple. I was comfortable with Windows. Every time I switched to Linux, small tasks felt unfamiliar. File management behaved differently, permissions required more thought, and many workflows I had taken for granted suddenly demanded a deeper understanding of the system.
Instead of returning to what was familiar, I decided to step outside my comfort zone and build an environment I would genuinely enjoy using every day. That decision became the foundation of FallenOS.
Arch Linux was chosen as the base because it provided complete control and encouraged learning from the ground up. I deliberately avoided preconfigured themes and ready-made configurations. The goal was never to recreate someone else's setup, it was to build a system tailored to my own workflow, preferences, and ideas.
Over time, FallenOS grew into something larger. What started as a personalized Linux environment evolved into a broader vision: an ecosystem of tools and services designed to work together. This expansion led to projects such as FallenCore, FallenKey, and FallenLink, each exploring different technologies, programming languages, and approaches to software development.
Today, Fallen is more than a Linux setup. It is an ongoing journey of learning, experimentation, and building the tools I wish existed.
As for the name, "Fallen" was inspired by the idea of a knight serving their kingdom with unwavering loyalty and dedication. Not for recognition or reward, but because it is their duty to protect, support, and remain dependable no matter the challenge.
That philosophy became a guiding principle for the project itself. Fallen is intended to be an ecosystem that quietly does its job well—reliable, dependable, and always working in the background to support its user. Just as a knight serves their kingdom, Fallen is designed to serve its user, being their loyal knight.
Vision
Existing solutions often rely on proprietary ecosystems, cloud dependencies, or fragmented tooling. Fallen aims to provide an alternative focused on openness, user control, privacy, and deep integration between Linux and Android.
Currently in Progress
Ecosystem Foundation
Architecture and project direction established.
Authentication
WinKey completed, FallenKey rewrite underway.
Desktop Integration
FallenCore currently in development.
Mobile Integration
Planned through FallenLink.
Ecosystem Components
FallenOS
Arch Linux • Hyprland • Pipewire • Waybar • Thunar • Linux-Zen • Pipewire
Customized Linux environment focused on productivity, performance, and workflow optimization.
FallenCore
C++ • Qt6 • Rust
Central desktop control center responsible for ecosystem management and device integration.
FallenLink
Rust • Android (Yet to be implemented)
Cross-device communication layer enabling file transfer, clipboard sync, and device interaction.
FallenKey
Tauri • Rust • TypeScript
Secure authenticator focused on privacy, reliability, and ecosystem integration.