An independent Ubuntu-based Linux distribution exploring a modular operating-system foundation and planned AI integration through Brok.
Note
About the banner: The image above is concept artwork created to communicate the project's visual direction. It is not a screenshot of a released NX desktop, and the interface elements shown in the artwork should not be interpreted as implemented features.
Important
Development status: Experimental
NX OS is under active development. Installation has been described as VM-tested only, and the project is not ready for production use. Check the current status and test results before relying on any feature. Do not install experimental builds on a computer containing important data.
NX OS is an independent Linux distribution based on Ubuntu. Its long-term goal is to explore a more integrated computing experience, including a planned AI layer built around Brok.
The project is being developed incrementally. The repository includes operating-system and build-related components, installation and desktop-related code, compatibility resources, testing tools, documentation, and a planned AI integration area.
NX is not simply a launcher or a single desktop application: it is intended to become an installable operating-system distribution. The current state of each component must be evaluated from its implementation, documentation, and test results.
NX OS is a operating system from Nexora-Techno organization
Project principles
- Modular engineering: keep system components and supporting tools organized.
- Verifiable progress: distinguish existing code from tested behavior and future plans.
- Practical compatibility: document constraints and validate support through testing.
- Responsible experimentation: treat installation, boot, and recovery behavior as safety-critical.
- AI-oriented direction: investigate integration with Brok without claiming planned functionality is already complete.
| Area | Current understanding |
|---|---|
| Distribution foundation | Under development |
| ISO build tooling | Build workflow is present; see BUILD.md |
| Virtual-machine boot testing | Test tooling is present; see TESTING.md |
| Installation | Experimental; review the installation guide |
| Windows ISO checksum utility | Present in the repository |
| Brok integration | Planned; not to be treated as implemented without code and tests |
| Physical-hardware compatibility | Must be verified per configuration |
| Production readiness | Not established |
For authoritative details, read FEATURES.md, ROADMAP.md, and TESTING.md. Repository contents and implementation may change.
The repository separates the operating-system foundation, build and installation tooling, user-facing components, AI-related work, compatibility, and verification.
NX/
├── nx-core/ # Core system-related implementation
├── build/ # ISO build scripts and configuration
├── installer/ # Installation-related components
├── desktop/overlay/ # Desktop overlay-related components
├── software-center/ # Software-management-related development
├── code-studio/ # NX Studio Code (git submodule: Barman-Zarei/NX-Studio-Code, branch main); clone with --recurse-submodules
├── ai/ # AI-related code and planned integration
├── windows/media-tool/ # Windows ISO checksum utility
├── compatibility/ # Compatibility resources
├── tests/ # Unit and VM boot-test tooling
└── docs/ # Supporting documentation
This is a repository map, not a complete runtime dependency diagram. See ARCHITECTURE.md for implementation details.
The documented ISO build environment is Ubuntu 24.04. For the complete, current workflow, consult BUILD.md.
sudo apt update
sudo apt install \
debootstrap \
xorriso \
squashfs-tools \
grub-pc-bin \
grub-efi-amd64-bin \
mtools \
qemu-system-x86Run from the repository root:
sudo build/build-iso.shThe workflow is expected to write an ISO image and a SHA-256 checksum file under out/, using the naming convention configured by the project. Check the actual build output for filenames and errors.
After the ISO is built:
tests/vm/boot-test.sh out/*.isoThe documented test workflow can use QEMU TCG emulation when /dev/kvm is unavailable.
A successful build does not prove that the image boots. A successful VM boot does not prove that installation is safe, that all features work, or that physical hardware is supported.
Warning
Review scripts before running commands with elevated privileges. Prefer an isolated virtual machine for initial evaluation. Do not assume an experimental installer preserves existing disks, partitions, files, or operating systems.
Read docs/installation/empty-disk.md before attempting installation.
Until installation, disk-selection, and recovery behavior have been adequately validated, use an isolated virtual machine. Back up important data independently, and do not use an important daily-use computer as an experimental target.
See SECURITY.md for security guidance and known limitations.
The current documented build environment is Ubuntu 24.04. Virtual-machine testing uses QEMU, with KVM where available and TCG emulation otherwise.
The Windows companion utility targets Windows 7 and newer and uses Qt 5.15 / PySide2 with Python 3.8.
Legacy hardware is a compatibility objective, not a universal support guarantee. Compatibility can depend on firmware, CPU architecture, memory, graphics hardware, storage, and drivers. See COMPATIBILITY.md for the latest documented constraints.
NX includes a testing area for unit tests and virtual-machine boot testing. Always distinguish between:
- A test script existing.
- A test actually running.
- A test passing in a named environment.
- A feature working beyond the test's coverage.
- A system being safe and reliable for general use.
When documenting a result, record the environment, command, expected behavior, actual result, and limitations. See TESTING.md.
NX is being developed incrementally. Broad areas of work include:
- maintaining the ISO build workflow;
- improving repeatable testing and verification;
- documenting installation and hardware compatibility;
- developing the planned Brok integration;
- evolving desktop and software-management components;
- improving contribution and developer workflows.
These are development directions, not release promises. Use ROADMAP.md for the project's recorded plans and CHANGELOG.md for recorded changes.
| Document | Purpose |
|---|---|
ARCHITECTURE.md |
Architecture and component organization |
BUILD.md |
Build requirements and ISO generation |
COMPATIBILITY.md |
Compatibility constraints and environment details |
FEATURES.md |
Feature descriptions and implementation status |
FEATURE_PRESERVATION.md |
Feature-preservation planning |
ROADMAP.md |
Development direction and milestones |
TESTING.md |
Test procedures and verification |
SECURITY.md |
Security guidance |
CONTRIBUTING.md |
Contribution workflow |
CHANGELOG.md |
Recorded changes |
LICENSES.md |
Licensing information |
Installation guide |
Experimental installation instructions |
Current status |
Milestone and status details, if present in this checkout |
If a link does not resolve in the current branch, check the repository for the correct path and update the link before publishing.
Constructive contributions are welcome: reproducible bug reports, documentation improvements, tests, compatibility investigations, architecture feedback, and focused code changes.
Before opening a pull request:
- Read the relevant documentation and existing issues.
- Explain the problem and the rationale for the change.
- Keep the change focused and reviewable.
- Include reproducible test or verification steps.
- State which environments were tested and which were not.
- Document limitations and potential risks.
Changes involving boot configuration, installation, storage, or recovery require particular care. Follow CONTRIBUTING.md.
A useful bug report includes:
- the affected component;
- operating system and environment;
- commands or steps to reproduce;
- expected and actual behavior;
- relevant error messages or sanitized logs;
- whether the issue occurred in a VM or on physical hardware.
Feature requests should explain the use case, the problem being solved, and any relevant constraints. Do not publish passwords, access tokens, private keys, or other secrets.
Operating-system development can affect boot configuration, storage, installation, recovery, and system integrity. Experimental behavior should not be treated as security-verified.
- Prefer isolated VM testing.
- Review scripts before running them with elevated privileges.
- Do not assume experimental installation procedures preserve data.
- Report security concerns responsibly and avoid posting secrets publicly.
Follow SECURITY.md for the project's current reporting guidance.
A development build, a version tag, a published release, and a production-ready operating system are different things. A generated ISO or successful boot test does not, by itself, establish release readiness.
See CHANGELOG.md, ROADMAP.md, and LICENSES.md for changes, plans, and licensing terms.
NX OS is an independent project and is not an official Ubuntu product or endorsed by Canonical. Ubuntu is a trademark of Canonical Ltd.; other names and marks belong to their respective owners.
NX OS — Building the foundation for a more integrated computing experience.
Independent development · Modular engineering · Verifiable progress