An ecosystem of self-hosted, privacy-first, open-source software projects designed for individuals and organizations that value ownership, simplicity, independence, and long-term maintainability.
An ecosystem of self-hosted, privacy-first, open-source software projects designed for individuals and organizations that value ownership, simplicity, independence, and long-term maintainability.
From these principles naturally follows the engineering philosophy:
A response to the increasing complexity of modern software stacks, cloud dependency, vendor lock-in, subscriptions, telemetry, and unnecessary frameworks.
Every NX9 application must run on infrastructure owned and controlled by its users. Cloud services may complement—but must never be required for—the software to function.
Users own their data, configuration, backups, deployment, upgrade path, and operational future. Software must never create dependency on a vendor.
Privacy is the default—not an optional feature. NX9 software includes absolutely no telemetry, tracking, analytics, surveillance, profiling, or mandatory accounts.
Every NX9 project is permanently Free and Open Source Software (MIT or Apache-2.0). Users must always be free to study, modify, redistribute, and fork the software.
NX9 embraces Unix philosophy and Linux conventions. Applications should integrate naturally with systemd, POSIX, shell scripting, standard filesystem hierarchies, and journald.
Every feature, dependency, and abstraction must justify its existence. We prefer fewer components, smaller binaries, readable code, and understandable architecture.
Every capability should be available from the command line. Graphical interfaces enhance usability but must never replace automation or scripting.
NX9 favors mature, well-documented, vendor-neutral technologies over proprietary ecosystems. We avoid unnecessary proprietary protocols, formats, and lock-in.
Built for decades—not development cycles. Software should survive changing trends, disappearing companies, and evolving ecosystems. Technology changes; good engineering endures.
Prefer standards over frameworks. Avoid requiring Node.js or Python at runtime. Minimize unnecessary dependencies and operational complexity.
We avoid these to reduce dependency trees, bloat, and runtime overheads—leaving room for exceptional cases only when truly justified.
The NX9 ecosystem is planned as nine interoperable projects sharing a common philosophy, consistent documentation, and minimal dependencies.
"Software people can own, understand, and control." — The Official Motto of NX9.