Library / SDK
unikraft/unikraft avatar
unikraft/unikraft

unikraft's page separates itself from Unikraft Cloud

A next-generation cloud native kernel designed to unlock best-in-class performance, security primitives and efficiency savings.

3,935 stars1,532 forksCNOASSERTION

At a glance

What is it?
A modular unikernel whose page opens by saying it is not the commercial product of the same name, where the only performance figure is tens of seconds against milliseconds with nothing measured, the build system descends from two other projects and re-runs make twice for workarounds, and the recommended getting-started path avoids the makefile this repository actually is.
Who is it for?
unikraft is worth evaluating if you want a single-application virtual machine rather than a shared kernel, and including only the components an application needs is the whole design rather than a feature bolted on afterwards. Two things to know first.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 10 days ago.
What is it written in?
Mainly C, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • unikraft/unikraft3,935 ★ · +71
Star history
Repository2026-09-242026-11-15
unikraft/unikraft3.9k3.9k

71 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The first note tells you this is not the commercial product

Before the feature list there is a note whose only job is disambiguation.

code
This repository is the Unikraft unikernel project. It is not Unikraft Cloud.
Unikraft Cloud is a separate platform that runs microVMs, with its own CLI and commands.

So the two things share a name, and the note exists because search results mix them. It matters beyond branding: the quick start opens by routing anyone who wants to deploy to that platform's command line client and documentation, then covers everything else here. Which leaves two clients with nearly identical names, the companion client this page teaches, and the one it sends you elsewhere for. The distinction is also architectural in a small way, since the commercial platform runs micro virtual machines while this project builds single-purpose ones.

Two figures on the page, and neither has a source

The boot claim is the only performance statement anywhere.

code
While Linux-based systems might take tens of seconds to boot, Unikraft will be up in milliseconds.

Two quantities, neither of them measured: tens of seconds for an unspecified Linux system, and milliseconds for an unspecified Unikraft. No hardware, no kernel configuration, no workload, no date. The claim is certainly directionally right for a unikernel, and the ratio as written is somewhere between one and two orders of magnitude. The other figure is the community, described as over a hundred developers fostering collaboration from industry and academia, with no link or date attached. Both are the kind of number that reads as a measurement on a page and is really a position.

The default branch is staging, and the releases are named after species

A clone gives you a branch called `staging`, which is not what most projects do and is worth knowing before you file anything. The releases follow a naming convention that is harder to script around: every tag carries a number and a camel-case taxonomic epithet, so the three most recent are v0.21.0 Ijiraq, v0.20.0 Kiviuq and v0.19.1 Pan. That makes the tags memorable and means any automation that parses them has to strip the suffix rather than assume a semver string. The cadence underneath is roughly eight months between the two minors, with the newest tag in May 2026 and the last commit to the default branch three days before this writing. The architecture line has a similar convention in miniature: x86 and ARM are supported, and RISC-V appears in parentheses inside the features list as coming soon, which is an unusual place for a roadmap item and the only place on the page where a supported platform is not actually supported yet.

The build descends from two other projects, and the licence metadata does not follow

The first lines of the makefile are a provenance chain.

code
# Copyright (C) 1999-2005 by Erik Andersen <[email protected]>
# Copyright (C) 2006-2014 by the Buildroot developers <[email protected]>
# Copyright (C) 2016-2017 by NEC Europe Ltd. <[email protected]>

So the build machinery descends from one container's original build system and then from an embedded Linux distribution's, with a later contribution from a corporate lab. That history explains the make-centric shape of the tree, which holds architecture, drivers, libraries, platform and support directories alongside a configuration fragment with a kernel-style extension, a version makefile include, a patch-style checking configuration and a static analysis configuration. In other words the project borrows the surrounding discipline of kernel development wholesale, down to the tooling that reviews patches. It also creates a small inconsistency worth naming: the makefile says the code is under the GNU General Public License version two or later, the repository's licence metadata records no recognised value, and the licence text itself is a Markdown file rather than the plain text file such a header usually points at.

The makefile re-runs make twice, once for a version check that admits it breaks

Two separate places in the build invoke make recursively, and neither is for parallelism.

code
# Check for minimal make version (note: this check will break at make 10.x)
MIN_MAKE_VERSION = 4.1

The first is a minimum version check implemented by re-running make through an indirection target, with a comment saying plainly that the check will stop working when make reaches version ten, because the comparison it performs is the sort that stops parsing two-digit numbers. The second is a file mode trick: the build compares the current umask against a fixed value and, if they differ, wraps every requested goal in a target that re-runs make with the umask set. Both are workarounds for make's own behaviour rather than for the kernel, and both are the kind of thing that is fine on the make versions they were written against and quietly wrong on newer ones.

The same install block appears twice, and one route is a pipe into a shell

The companion client is installed by fetching a script over HTTPS and handing it to a shell, and that block is printed twice on the page, word for word, once in the quick start and once in the toolchain section.

shell
# Install on macOS, Linux, and Windows:
curl -sSfL https://get.kraftkit.sh | sh

The alternative on macOS is a Homebrew tap rather than a pipe.

shell
brew install unikraft/cli/kraftkit

Other systems are told to use the interactive installer or find further instructions. Two details sit alongside. The script claims macOS, Linux and Windows from one URL, which is a lot of platform coverage for a single shell installer. And on a Mac the build itself needs GNU sed rather than the system one, which the makefile handles by switching a variable when it detects Darwin, so a Mac developer ends up installing a second sed anyway.

The development container pins a platform and floats the base image

There is a container route for trying the project in emulation mode, and the command shows both the reason it exists and its weakness.

shell
docker run --platform linux/x86_64 -it --rm -v $(pwd):/workspace --entrypoint bash kraftkit.sh/base:latest

The explicit platform flag is what lets this run on an ARM machine, by emulating the other architecture, which is the point of the prebuilt environment. The base image is pinned to a floating tag rather than a digest or a version, so two developers starting the same week can get different environments. Your working directory is mounted at a fixed path and you are dropped into a shell, and the page tells you to type exit or a control sequence to leave. It is a reasonable convenience and a reasonable thing to pin before relying on it.

The recommended path avoids the build system in this repository

The getting started section offers two ways in and marks one of them recommended.

code
1. (**Recommended**) Using the companion command-line tool [`kraft`][kraft] (covered below).
2. Using the GNU Make-based system.  For this, see our [advanced usage guide][unikraft-guides-advanced].

The second one is the make-based build, and this repository *is* the make-based build: the makefile, the kernel-style configuration fragment, the version makefile include and the five source directories are all here. So the project recommends a client that drives the build rather than the build itself, and pushes anyone who wants to build directly to a guide. That is a defensible choice for a project with per-target configuration. It does mean the walkthrough for building your first unikernel is the one section missing from this copy of the page, which stops after its heading and a single letter.

Editorial conclusion

unikraft is worth evaluating if you want a single-application virtual machine rather than a shared kernel, and including only the components an application needs is the whole design rather than a feature bolted on afterwards. Two things to know first. The performance claim is a ratio of tens of seconds against milliseconds with no figure, hardware or measurement behind it, so measure your own application. And the page's recommended way to start avoids the make based build that this repository actually contains, so expect to read the advanced guide before you can build anything of your own.

Frequently asked questions

What are the key differences between Unikernels and containers?

The page does not set out that comparison. It describes the project as powering containerless applications and as single-purpose virtual machines known as unikernels, where a modular design lets a developer include only the components an application needs.

unikraft vs docker

The page makes no comparison with containers. What it describes is a modular kernel you build either with a companion command line client or through a make-based system, producing a single-application virtual machine.

mirageos vs unikraft

Not something the page addresses. It names its own supported architectures as x86 and ARM, with RISC-V described in parentheses as coming soon, and does not compare itself with other unikernel systems.

How do I install the Unikraft toolchain?

With an interactive installer fetched over HTTPS and piped into a shell, or through a Homebrew tap on macOS. Other systems are pointed at further installation instructions. The same interactive command appears in two sections of the page.

How do I run my first unikernel?

Use the companion client to run a published example image, then list running instances across all of them, and list the community image catalog with the update and apps flags. The page also offers a Codespaces route and a container environment that maps your working directory into the container and drops you into a shell.

Official sources

  1. Issues
  2. Project website
  3. README
  4. Releases
  5. unikraft/unikraft on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/unikraft-unikraft.svg)](https://hysenlabs.com/projects/unikraft-unikraft)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/unikraft-unikraft.svg)](https://hysenlabs.com/projects/unikraft-unikraft)

Was this useful?