Commitment
Privacy by default
No screen contents, no window titles, no keystrokes, no identifiers, no biometrics, no mic, no cam, no third-party piggybacks. Settings exist to be set, not to be coaxed.
An open desktop OS
A desktop operating system, made in the open. Users share the value.
NovaOS is memory-safe, on-device AI, and gaming-ready, on a single auditable codebase. Opt into the data program and a defined share of the revenue your usage creates comes back to you.
Win10 guide
Switching from Windows 10 to NovaOS in 30 minutes
Microsoft ended free Win10 updates — here’s a calm, private alternative in 30 min.
Gaming guide
Ironstake for gaming — performance, drivers, anti-cheat
NovaOS is not a daily-driver build today. Here’s the honest gaming posture: a memory-safe kernel, an OSS driver model, and anti-cheat that never reads your screen.
What NovaOS is
A desktop OS — kernel, drivers, desktop environment, and on-device AI, on a single auditable codebase.
- Memory-safe by default — whole classes of exploits removed.
- On-device AI — no data-center round trip, no telemetry piggyback.
- Gaming-ready — built-in, not bolted on after the fact.
Public build · later in 2026
What is NovaOS
Four architecture commitments, in plain language.
The codebase is the security claim. The decisions that shape this OS are written down, and shipped in the open — that's the contract.
Commitment
Memory-safe security
The kernel, drivers, and core services are written in languages that do not ship memory-corruption bugs by default. Whole exploit classes disappear with the code, not with patching.
Commitment
Gaming as a first-class workload
Modern graphics and compatibility are built in from the first boot. Your library runs; nothing is bolted on after the fact.
Commitment
On-device AI
Models run next to the window they serve. No data-center round trip, no telemetry tied to the inference, and no opt-in dialog before a feature works.
How it works
Four steps. The hard part is the boring, public part.
NovaOS is built for users who want a stake in the value their usage creates — not a polished enterprise play competing on conventional support revenue.
- step 01
Install the system
A single signed image, on bare metal or alongside your existing OS. Nothing leaves the machine at first boot.
- step 02
Pick how you participate
Today the only choice that matters is the data-program toggle. Say yes, say no, switch later — opting in and opting out are both reversible from the same setting.
- step 03
Use the system
Opted-in means aggregate, anonymized signals at the OS-feature level. No screen contents, no window titles, no keystrokes, nothing that resolves to you.
- step 04
A share of revenue comes back
A defined percentage of revenue attributable to opted-in participants is paid out — pro rata, on a public schedule. The percentage and the formula are in the open.
Capabilities
What NovaOS does — and on the same codebase as what it does not.
The headline commitments above are promises. Below is the rest of the architecture — the parts that make those promises honest.
Capability
Single auditable codebase
Kernel, drivers, desktop environment, and AI runtime on the same repo. No vendor SDK forks, no closed blobs in the boot path. The repo IS the security claim.
Capability
Opt-in, reversible data program
A defined share of attributable revenue, paid back pro rata to opted-in participants on a public schedule. Opting out does not produce a second-tier product.
Capability
On-device AI by default
Inference happens next to the window it serves. No round-trip to a vendor cloud, no telemetry piggyback on the prompt, no opt-in dialog blocking the feature.
Capability
No third-party SDKs
The OS and its bundled apps ship without ad-tech, tracking pixels, analytics SDKs, or build-time data recipients. Our code is the only code that runs.
Capability
Public build, public process
Decisions that shape the OS are documented, the codebase is open, and the revenue-share percentage and formula are published.
Privacy perimeter
What NovaOS will never do — written down, in the open.
The other side of the capability grid. Where the capabilities list says what the OS can do, this one says what it will not — and never will.
What NovaOS never collects
Nothing that resolves to what you are doing, looking at, or saying.
- No screen contents, no window titles, no keystrokes.
- No identifiers that resolve to a single user or device.
- No biometrics, no microphone content, no camera content.
- No contents of files you open.
What NovaOS never depends on
No vendor SDKs, no third-party pipelines, no closed blobs in the boot path.
- No third-party telemetry SDKs, no ad-tech, no analytics piggybacks.
- No prompt-redirected inference, no "accept cookies to use the OS."
- No closed-source blobs in the boot path.
FAQ
The questions people ask before they sign up.
Still curious? Write to novaos-10@polsia.app — the inbox is read by a human and answered in kind.
Ask a direct questionJoin the waitlist
Join the waitlist. We will email you when the public build is ready.
No marketing, no drip campaign. One email the moment you sign up, one email when the build ships, and that is the contract.