Sovereign · Secure · Smart

The AI-native OS that's actually yours.

The system disk is read-only and cryptographically verified. Updates are signed with post-quantum cryptography. And the built-in AI can't do anything without your say-so. Your machine answers to you, not to a data centre.

Runs live from a USB stick · Installs in minutes · Your files and AI prompts stay on your machine

Why Orynr exists

You shouldn't have to choose between safe and usable.

Most “AI PCs” bolt a chatbot onto an old stack and send your life to somebody else's servers. Most hardened systems ask you to give up everything that makes a computer pleasant to use. We didn't want to accept either trade, so we built Orynr.

01

Sovereign

The AI runs locally. Your data and the system's diagnostics live in separate planes. Owner control is tied to your credentials and written to an audit log, so there's no hidden way in.

02

Secure

The system disk can't be modified, and it's verified every time you boot. Underneath sits a kernel we harden and compile ourselves, with defences that reach into the kernel itself.

03

Smart

The assistant does real work on the machine. It also can't take a single privileged action until you approve it. That's a property of the design, not a promise we're asking you to trust.

The operator plane

An AI with root, and a leash you hold.

Ora can actually drive the machine. It reads files, runs scans, changes settings, digs into problems. Before it does any of that, a consent card appears and waits for you to approve or refuse. Every action it takes goes into an audit trail.

Powerful, and provably contained

  • Consent broker. Ora only reaches the system through a gate you control. There is no route around it.
  • Runs on your hardware. Point it at whatever model server you already run (llama.cpp, vLLM, LM Studio, Ollama) or at an Orynr engine. No API key, nothing leaving the box.
  • Scoped access. Give it a container, your home folder, the whole OS, or one directory you pick. You set how far it can see.
  • Interruptible. Stop a long answer halfway through. Watch it reason while it works.
The Orynr Assistant window, showing that it can drive the machine but every action needs consent and is logged
Why we built it this way An assistant powerful enough to fix your machine is only safe if it can't act behind your back. You can't get there with a policy document. It has to be true of the architecture, so that's where we put it.

Defence in depth

Security you can check for yourself.

Six layers, starting close to the hardware. You'll never notice most of them, which is rather the idea.

01

Verified & measured boot Shipping

The system disk is read-only and cryptographically verified. Tamper with it and it won't boot. If it booted, it's the OS we shipped, provably.

02

A kernel we build ourselves Shipping

Mainline Linux LTS plus the hardened patch set and our own configuration, all compiled from source. The source is available, so you can read it rather than take our word for it.

03

The kernel-aware firewall New

Antivirus watches files. A network firewall watches packets. This one watches the kernel. It sees every program that starts, and it can refuse the ones launching from the temp folders where malware likes to sit.

04

Mandatory access control Shipping

SELinux enforcing, kernel lockdown, sandboxing and capability limits. A compromised process stays one compromised process instead of becoming your whole machine.

05

Files judged by content Shipping

Orynr identifies a file by its actual bytes, not its name. A program wearing a document's name is flagged and refused, defusing a decades-old attack every other desktop still ships.

06

Post-quantum by design Architected

“Harvest now, decrypt later” is happening today. Orynr's cryptography is chosen to survive quantum attack, built in from the start, not retrofitted later.

Under the hood

Built from source, tuned for speed.

Hardened doesn't have to mean slow. Orynr is compiled with whole-kernel link-time optimisation, modern memory reclaim, and a GUI that comes up straight from boot.

Our own hardened kernel

Linux LTS + the hardened patch set + our configuration, reproducibly built. A local patch queue means we can fix things upstream can't reach.

Fast by default

ThinLTO across the whole kernel, multi-generational LRU reclaim, transparent hugepages, and an adaptive scheduler on the way.

Immutable by construction

A compressed, verified read-only root with a separate writable area for your data. Updates either apply or they do not, so you never end up half-patched.

Open where it counts

Our kernel changes are published under the GPL. Nobody should have to take a security claim on faith, so the parts doing the protecting are there to inspect.

Switching

Bring your Windows apps, and your domain.

The usual reason people cannot leave Windows is not the operating system. It is one application they need and one login their company controls. We are building for both.

Windows applications In build

A compatibility layer translates Windows API calls into Linux ones. No Windows virtual machine, no Microsoft code, no second licence to buy. Each app is sandboxed, so a Windows program gets no more of your machine than anything else. Titles with kernel-level anti-cheat or their own drivers are the known exceptions.

Active Directory domain join In build

Kerberos for authentication, SSSD for identity, SMB for shares. Staff sign in with their domain account and their drives are where they expect. It stays off unless you turn it on, because joining a domain means trusting a controller and exposing extra auth services. Right for a managed laptop, wrong as a default, and not offered at all in the hardened profile.

Where this actually stands Both are designed and under construction, not in the current build. We would rather tell you that than let you install Orynr expecting your accounting package to open on day one.

Try it without installing anything.

Write Orynr to a USB stick and boot it. Everything works live, so poke around, break things change your mind. Install only when you're convinced.

Orynr_OS is in active development. Features are labelled Shipping New Architected so you always know what's real today.