Origo OS manages infastructure running virtualized workloads and services. Origo OS supports management through a web client, declarative configuration and automation through the API or the CLI.

Origo OS’s code-name during development was “Stabile”, which is inspired by the use of the word in Ursula K. Le Guin’s writings.

Origo OS is all about open infrastructure

If you have no desire to tinker with hardware, and mainly want to write your code, containerize your application and deploy it to some pre-configured Kubernetes environment, you should probably just look to some of the great cloud offerings out there.

Origo OS tries to fill a gap in the market we feel there is for those who, for whatever reason, prefer to manage their own basic infrastructure on “bare iron”.

What Origo OS is and can do

Origo OS provides you with:

  • A managed and scalable environment for deploying and running VM’s from virtual images using KVM.
  • A model for assembling collections of pre-configured virtual images, compute, storage and networking ressources into declarative configurations packages which together describe how an application is deployed. We call these packages “Stacks”.
  • A set of pre-built stacks for quickly running and easily managing standard Linux servers, including a Kubernetes stack, which will set up an auto-scalable Kubernetes environment in seconds.
  • A PXE-boot environment for easy joining of hardware nodes
  • Automated management of storage ressources using ZFS
  • Automated management of network routing and network access to your VM’s using iptables, dnsmasq, proxyarp, Linux bridging, etc.
  • Automated backup using ZFS storage snapshots
  • Basic monitoring and reporting
  • Simple metering suited for billing purposes

What Origo OS is not and cannot do

  • Origo OS is not a container orchestration platform. We may provide the ability to run containers directly on Origo OS hardware nodes sometime in the not-too-distant future, but for now, Kubernetes and containers run inside VM’s on Origo OS.
  • Origo OS is currently in beta, and should only be installed and used for production environments in close cooperation with Origo Systems.


If you have read this far, we suggest you strap in, and go ahead with reading about the main components of Origo OS.

The Web Client and the API are organized around the ressources that Origo OS manages and orchestrates. They are:

  • Engines and Nodes: The hardware that a Origo OS installation runs on
  • Stacks: Packaged applications that run on a Origo OS infrastructure
  • Servers: The VM’s that run on Origo OS nodes
  • Images: The virtual images the VM’s boot from and use for storage
  • Networking: Your VM’s connections to each other and the outside world
  • Users: User accounts and their privileges