yantrikos.com/download
Get it, check it, boot it.
Yantrik OS is one file: a live ISO you boot, and the desktop runs from it without touching a disk. The installer is inside the running desktop, for when you want it on one. Every command below is copied from the repository, with the file it is in.
The current image
- file
- yantrik-os-v0.1.0-1806-g75497c70.iso
- version
- v0.1.0-1806
- built
- 2026-10-19
- size
- 1.77 GiB (1902624768 bytes)
- commit
- 75497c70
- sha256
- 068dbb30e3f46f9e95cdc226a3ded5e3fb1fdba582ad342e5c270c5aa64aa6f3
- channel
- nightly — the only one with builds
- Yantrik OS ships as a Debian 13 (trixie) live ISO for x86-64. There is no ARM build and no 32-bit build.from docs/hardware-requirements.md
- Only the nightly channel has builds. Beta and stable are names the updater knows; nothing has been published to either.from docs/getting-started.md · docs/releasing.md · install.sh
- Every published image is boot-tested in QEMU.Real hardware and UEFI are untested.from docs/hardware-requirements.md
Get it
One link, always the newest nightly: yantrik-os-latest.iso. The release host points it at each build as it is published, and its checksum file names it, so three lines fetch and check it:
$ curl -fL -O https://iso.yantrikos.com/nightly/yantrik-os-latest.iso
$ curl -fL -O https://iso.yantrikos.com/nightly/yantrik-os-latest.iso.sha256
$ sha256sum -c yantrik-os-latest.iso.sha256
Or let the repository’s install.sh read it for you. With no flag it only tells you; this is what it printed when it was run for this page:
$ sh install.sh
Yantrik OS ships as a live ISO — a Debian 13 image you boot and try before you
install anything. There is no package to add to a system you already have.
Asking https://iso.yantrikos.com/nightly/latest.json …
version v0.1.0-1293 (built 2026-10-06)
file yantrik-os-v0.1.0-1293-ge8903b08.iso
size 1.64 GiB (1765054464 bytes)
sha256 83fbaa825433b2e3a9f38b45e4f20b5e0527d9d57a018fba0757d4b456559194
url https://iso.yantrikos.com/nightly/yantrik-os-v0.1.0-1293-ge8903b08.iso
This is the nightly channel, and it is the only one that has ever had a build
published to it. It is early software: things break, and the audits of what does not
work are public in the repository under design/.
To fetch it here and check it:
sh install.sh --download
or download it yourself and verify before you boot it:
curl -fL -O https://iso.yantrikos.com/nightly/yantrik-os-v0.1.0-1293-ge8903b08.iso
curl -fL -O https://iso.yantrikos.com/nightly/yantrik-os-v0.1.0-1293-ge8903b08.iso.sha256
sha256sum -c yantrik-os-v0.1.0-1293-ge8903b08.iso.sha256install.sh prints the current image’s address, size and sha256, and stops. Only with --download does it write a file, and it refuses the file if the sha256 does not match.from install.sh
$ sh install.sh
# what the current image is, and what to do with it
$ sh install.sh --download
# also fetch it into this directory and check its sha256
$ curl -fsSL https://get.yantrikos.com/install.sh | sh
# piped into a shell, it explains and does nothing elseCheck it before you boot it
The point is not that someone is attacking you. It is that a 1.3 GiB download that ends at 98% gives you an image that boots halfway and fails in a way you will spend an afternoon on. (The image has grown since that sentence was written: latest.json above has today’s size.)
$ sha256sum -c <that file>.sha256
$ shasum -a 256 <that file>
# compare with the sha256 in latest.jsonBoot it in a VM first
This is the recommended way to meet it, and what the project develops against.
$ qemu-system-x86_64 -enable-kvm -m 4096 -smp 4 \
-cdrom yantrik-os-<version>.iso -boot d \
-device virtio-vga -display gtk
| known to work · measured | the least anyone has booted · CI | |
|---|---|---|
| CPU | 4 vCPU | 4 vCPU |
| RAM | 8 GB | 4 GB |
| Disk | 32 GB | none, if you only boot live |
| GPU | none needed | none needed |
| Firmware | BIOS | BIOS |
Known to work: QEMU/KVM with 4 vCPU, 8 GB of RAM, a 32 GB disk, no GPU and BIOS firmware, the project’s own test machine. CI boots every image with 4 GB and 4 CPUs.Below 4 GB of RAM is not measured.from docs/hardware-requirements.md · deploy/yantrik-os/boottest.py
Proxmox: set vga: virtio. With Proxmox’s default the machine boots, reports a healthy session, and shows a black screen forever, because there is no /dev/dri for the compositor to find.
VirtualBox ought to work and has not been checked against a current build. The settings the repository’s own scripts give it are configured, not measured: 4 GB of RAM, EFI enabled, the VMSVGA graphics controller and 128 MB of video memory.
Or write it to a USB stick
# /dev/sdX is the DEVICE, not a partition. Getting it wrong overwrites
# the wrong disk. `lsblk` on Linux, `diskutil list` on macOS (where it is /dev/rdiskN and
# the stick must be unmounted first with `diskutil unmountDisk`).
$ sudo dd if=yantrik-os-<version>.iso of=/dev/sdX bs=4M status=progress conv=fsync
On Windows, Rufus (rufus.ie) or balenaEtcher (etcher.balena.io). All of them take the .iso exactly as downloaded; do not unpack it.
The boot menu
| entry | what it does |
|---|---|
| Install Yantrik OS | Boots live and puts first-run setup into installer mode, so it offers to write to a disk at the end |
| Try Yantrik OS (live, no install) | Boots live. Nothing offers to touch a disk |
| Install Yantrik OS (Safe Mode) | The same as the first, with nomodeset: use this if the screen stays black |
| Try Yantrik OS (verbose, serial console) | No quiet, so the kernel and systemd say what they are doing. The entry to boot when you are filing a bug |
- On the live image the user is yantrik with the password yantrik and passwordless sudo. SSH is installed and turned off.from docs/getting-started.md
- The image ships no language model and no mind. You point it at one in first-run setup.from docs/getting-started.md · docs/hardware-requirements.md
Install it to a disk
The disk installer erases the disk you give it, needs one of at least 6 GB, and has not been through the boot test the image has.from docs/getting-started.md · docs/hardware-requirements.md
Boot the “Install Yantrik OS” entry and first-run setup ends on the install screen. Or, in a terminal in the live session:
$ sudo /opt/yantrik/bin/yantrik-install
The full path is needed: sudo on Debian replaces your PATH with its own, which does not include /opt/yantrik/bin. It shows every answer and the disk together and waits for you to type yes.
Update it
$ yantrik-update check # what is installed, versus what the channel has
$ yantrik-update apply # download, verify, install, restart the session
$ yantrik-update rollback # restore the previous build
$ yantrik-update status # channel, host, current build, backups on disk
Updates verify the bundle's checksum, keep a backup, and roll back if the shell does not answer.Nightly is the only published channel; manifests are not yet signed.from design/updates-2026-09-21.md · docs/releasing.md · README.md
Hardware: what has been measured, and what has not
The OS’s own hardware page labels every number measured (someone ran the command), configured (a value in a file you can read) or not measured (nobody has checked, so no figure is given). This page keeps the labels.
| the project’s test machine | CI’s boot test, every image | |
|---|---|---|
| label | measured, 2026-09-22 | configured, boottest.py |
| platform | QEMU/KVM, Q35 + ICH9, SeaBIOS | QEMU, KVM when the runner has it |
| CPU | 4 cores | 4 |
| RAM | 7.8 GiB (provisioned 8 GB) | 4096 MB |
| GPU | none: virtio-gpu, Mesa llvmpipe | none: virtio-vga, headless |
| disk | 32 GB | none: it boots the live image |
| firmware | BIOS | BIOS |
Not measured
Not measured: real hardware of any kind, the UEFI boot path, any GPU but QEMU’s virtio-vga, Wi-Fi on real adapters, and VirtualBox.from docs/hardware-requirements.md
process RSS MB PSS MB
yantrik-ui 181.2 177.9
a11y-service 4.8 2.9
weather-service 4.4 2.5
network-service 4.0 2.1
----- -----
TOTAL 194.4 185.5The whole desktop uses about 186 MB of memory.Measured 2026-09-06 on a software renderer.from docs/footprint.md