This website uses a number of technical terms and certain product names. Below, we provide definitions or explain what we mean by each of them.
Please note: the term “hypervisor” is used somewhat broadly throughout the site to support general understanding and marketing purposes.
Cidoka combines "CI" and "Jidoka" — a Toyota principle where machines or people halt production when defects are found. Applied to our work, it ensures immediate issue detection, preventing faulty code from progressing and maintaining quality. We offer consulting, hands-on testing framework implementation, and contract engineering based on this approach.
Ctrl OS stands for “Cyberus Technology Resilient Linux (OS)”. It provides the manufacturers of Embedded Systems with a platform to build their systems on. The basis of this platform is our long-term supported declarative operating system based on NixOS 24.05. This LTS runs up to 5 years and ensures the customer to be ready for the coming EU Cyber Resilience Act, due to its SBOM creation capabilities, secure-by-design layout and CVE management. Additionally, it is possible to run the Cyberus Hypervisor and also KronoCore on top of the platform. Doing so, the customer can equip their system with security (Cyberus Hypervisor) and also legacy capabilities (KronoCore).
Our knowledge, expertise, and services around Cloud Hypervisor. We aim to upstream all patches for feature-parity with upstream. Not a hard fork.
An API is a set of rules and tools that allows different software systems to communicate and interact with each other.
A lightweight and security-focused VMM written in Rust, also utilising KVM on Linux. It is optimised for modern cloud-native workloads and deliberately omits legacy hardware emulation to reduce complexity, improve boot performance, and minimise the attack surface.
The Cyber Resilience Act is an EU regulation that sets cybersecurity requirements for digital products to ensure their safety and resilience throughout their lifecycle. It comes with three main requirements: The product is secure by design; Vulnerabilities are monitored and fixed throughout its lifetime; A Software Bill of Materials (SBOM) documents what’s inside.
Another term for VMM.
Privileged software component running in kernel-space managing the resources of VMs including strong isolation, as well as leveraging CPU hardware-extensions for performant virtualisation.
KVM is a hypervisor and directly integrated into the Linux kernel.
Transfer of VM state from one location to another while the VM keeps running.
LTS refers to software releases that receive updates, including security fixes and maintenance, for an extended period – in our NixOS LTS / Ctrl OS case this is for five years – making them ideal for stable, long-term use.
QA is the process of systematically monitoring and testing software to ensure it meets defined quality standards and functions correctly.
A versatile VMM that leverages KVM on Linux to run virtual machines. It supports a broad range of guest operating systems and devices, making it well-suited for general-purpose workloads, including desktop-style environments with graphical interfaces.
Set of software components required to effectively create, run, and manage virtual machines. It includes the hypervisor and VMM, and may also encompass management tools like libvirt for orchestration and device emulation backends - depending on the specific scenario.
Unprivileged software component (a regular user-application) managing the overall VM, including the virtual hardware, by utilising the hypervisor.
A VM is a software-based emulation of a physical computer that runs an operating system and applications independently, allowing multiple systems to run on the same hardware.