A hardened OS, built for you

Software you built yourself, and can prove it.

kaji builds a hardened OS: the software, the system images and the container images from source, on your own infrastructure. Everything is signed with your key and kept in your own repository and registry. Nothing is downloaded from someone else as a finished program.

Free to look around: a guided walk-through builds a web server container image for you in about five minutes of clicking.
A smith at an anvil, forging: the kaji logo

Who kaji is for

You want to know exactly what runs on your machines and where it came from. kaji is for three kinds of teams.

Fleets

You run a fleet of machines

Compiling on every node wastes hours and leaves each machine slightly different. Build once, in parallel on your cluster, into one signed package repository. Every machine then installs the same prebuilt packages in seconds.

  • One build, the same versions on every node
  • Your own package repository, on your own storage
  • Reuse packages someone already built, compile only what is missing
  • System images and install media from the same packages

IoT and embedded

You ship devices you must keep trustworthy

Devices are small, many and far away. Build a system image that holds only what you list, with your own configuration, for the architectures you ship. Devices install only packages signed with your key.

  • Minimal system images, nothing you did not ask for
  • amd64 and arm64 builds
  • Your configuration, kept with the build
  • A package that is not signed by your key is refused

Secure containers

You want images you can account for

Most images are a pile of someone else's binaries. A kaji image is built from source from a package list you control, so it holds the program and what it needs to run. No shell, no package manager, no leftovers.

  • Built from source, from a list you can read
  • Signed packages, your key
  • Scanned against published security advisories
  • Pushed to your own registry, with a login made for you

What you get

Four things, built on the same signed foundation.

Subscription

Hardened container image streams

Subscribe to a stream of hardened container images that are rebuilt from source and kept up to date, so you pull the next safe image instead of patching the last one.

IoT

OS images with OTA updates

Operating system images for your devices, with over-the-air updates, so a fleet in the field moves to the next signed version without anyone visiting it.

Registries

OCI registries

A container registry of your own for the images you build, with a login made for you.

Registries

Binary package registries

A repository of your own for the packages you build, signed with your key, which your machines install from.

How it works

You say what you want. kaji does the work on your own machines and keeps the result for you.

Name the packages

Choose the software you need, for example the nginx web server, and how it should be built.

The cluster builds

kaji works out what each one needs and compiles it, many parts at the same time. What already exists is skipped.

Everything is signed

Your key signs each package before it is kept. Machines check the signature and trust only yours.

Use the result

Install from your own repository, build a system image, or turn it into a container image in your registry.

Why kaji

Every package is described down to how it is built. kaji turns that into a build service you own.

You hold the key

The signing key is yours. The machines that compile never see it, and nothing is kept without your signature.

You can read what is in it

An image is the software you listed and what it needs to run, and nothing else: no shell, no package manager, no leftovers.

You find out about vulnerabilities

Every build is checked against published security advisories, and a vulnerable package is flagged.

You keep the data

Your packages and images live on your own storage. A registry gets a login that is made for you and kept safe.

It uses what you have

kaji runs on the cluster you already have and needs nothing else: no build farm, no separate CI system.

You can watch it work

Live build logs, a plan that shows what depends on what, and a retry for a build that failed.

Who it is not for

kaji is the right size for a team that cares where its software comes from. It is probably not what you want if:

  • you need an operating system that comes ready-made. With kaji you choose what goes into it;
  • you only need to run a container someone else built, and you are happy to trust it as it is;
  • you have no cluster to build on.

Pricing

Every plan includes source builds, signed binary repositories, OS and container images, CVE scans with email alerts, and organization roles.

PlanFreeTeamsEnterprise
Price Free 28 € / month On request
Public trees, repositories, and configsIncludedIncludedIncluded
Hardened amd64 server profiles (glibc, musl, SELinux/systemd)View onlyView and buildView and build
Private overlays and trees in builds—IncludedIncluded
Automatic image publishing to clouds and VMware—IncludedIncluded
Premium container streams—Add-onAdd-on
API and Terraform access—IncludedIncluded
Quotas
Package builds442Unlimited
Binary repositories12Unlimited
Storage per repository1 GB10 GBUnlimited
Container registries110Unlimited
Private Portage trees—1Unlimited
Signing keys per user14Unlimited
Users per organization110Unlimited
Parallel jobs per build24Unlimited
Managed Kubernetes nodes110Custom

Build something you can account for

Sign in and follow the walk-through. It takes you from a signing key to a running container, and explains each step on the way.