AI? Yes. 100%

Did we use AI to build LeivOS? Yes. 100%.

Look, we’ve seen the internet. Right now, "AI-generated operating system" is basically a synonym for low-effort slop—a hastily prompted kernel with no underlying architecture, built by someone who learned to code yesterday just to farm stars on GitHub and karma on Reddit. If you're skeptical of LeivOS because of how it was built, we don't blame you. Skepticism is healthy. When we say 100% AI-assisted, we mean it’s deeply blended: at this point, the workflow is so integrated that we can't easily separate what was hand-typed from what was generated. So we own it.

LeivOS didn't start in a vacuum. It runs on the Uusi kernel, and both are written in Tape, a language that evolved from a game development effort streamed live on Twitch nearly 10 years ago. Tape began as an in-game scripting language, grew into the language used to build the game itself, and is now used inside Puida for internal tools, cross-platform CI runners, user interfaces, testing frameworks—and this operating system. Tape has its own AI disclaimer, and it says the same thing this one does.

LeivOS wasn’t dreamed up by an LLM. It’s built by Puida Oy, and it was preceded by an earlier version of the Uusi kernel written in C: its boot flow, its drivers and its network stack showed what worked on real hardware, and LeivOS was ported from it by understanding, not by copying.

We didn’t just type "write an operating system" and paste the output. We used AI intensively as a high-velocity force multiplier—generating boilerplate, writing test suites, exploring designs, and drafting repetitive driver and protocol code at breakneck speed. We use AI across all our products, logos, and designs. An LLM can write a driver, but it doesn't understand the core problem we are trying to solve: a desktop computer that is small, calm, and honest about what it does. The vision, the constraints, and the architectural responsibility are 100% human-driven.

AI gave us the velocity to build LeivOS in a fraction of the time it would normally take. But the design, the intent, and the execution belong to engineers who actually understand how kernels work under the hood.

Don't judge LeivOS by the tooling we used to build it. Judge it by what it does on a real machine, the architecture, and whether it solves a real problem. If it breaks or falls short, that's entirely on us.

Puida Oy