Why are we doing this
We do not build standalone products that happen to sit next to each other. We build blocks that fit together: a hypervisor, an operating system, and the tooling to test what you assemble from them. That is the direction the company has taken over the past few years, and at some point it becomes obvious that the names have not kept up.
Cyberus Hypervisor. Cyberus Linux. The relationship is now visible in the name instead of explained in a footnote.
There is more to it than tidiness. When organizations discuss digital sovereignty today, the conversation is rarely ideological and almost always practical. Who can read this code? Who patches it when something breaks? Who is liable? Where does the person sit who picks up the phone?
Our answer to those questions is a set of open, auditable building blocks that you can adopt individually or combine, built and maintained by German company, with no obligation to take the rest of the stack if you only need one part. An operating system that visibly belongs to the hypervisor makes that answer easier to give, not harder.
What is Cyberus Linux
Cyberus Linux is a NixOS-based long-term-support operating system for environments where you need to know exactly what is running and be able to prove it. Declarative configuration, reproducible builds, and a maintenance commitment measured in years rather than release cycles.
What changes
- The repositories move to a new GitHub organization. All Cyberus Linux repositories are moving to
github.com/cyberus-linux. GitHub keeps redirects in place after a transfer, so existing clones, CI jobs, and flake inputs will continue to work. However, we recommend updating your references rather than relying on redirects indefinitely. - Package, module, and channel names. There will be new URLs for the channel and the tarball package. The old names will be redirected.
- Documentation and websites. All documentation moves to the new name. Old URLs redirect. This includes the following pages:
- Contracts and invoices. Existing support and development agreements remain valid and unchanged.
What does not change
- The codebase. This is a rename, not a fork or a rebuild.
- Your existing deployments. They keep running.
- LTS commitments. A system supported until a given date is still supported until that date.
- Release cadence and versioning.
- The people you talk to.
Talk to us
If you are evaluating a Linux base for a system that has to be auditable, maintainable, and defensible for years, talk to us. We promise a technical conversation, not a sales call, about your constraints and whether Cyberus Linux is the right answer to them.
Reach us at businessdevelopment@cyberus-technology.de