Resources
Package repository
Where Saphira and Saphira-D packages are published, and the systemd unit files that go with them.

Overview
This is the Saphira package repository. Saphira and Saphira-D packages are published across three streams, main, latest and hatchling, and this area also supplies the systemd unit files that Saphira-D needs but the OpenRC-based Saphira does not ship. The sections below explain where the packages live, the streams themselves, and the systemd units currently available.
Browse or search every published APK on the Packages page. The repository itself is always the source of truth; that index is a readable view of it.
The Egg hatches
Saphira's package repository is not merely a collection of APKs. Follow how the original Saphira system is being used to produce the next generation natively.
Where packages live
Moving soon: https://packages.akadata.ltd/ is being retired and the repository will move to https://packages.saphira.vm2/ shortly. You can find AKADATA LIMITED new home here https://www.akadata.co.uk/.
All Saphira packages are published at https://packages.akadata.ltd/saphira/. The repository serves several streams built from the same Saphira / Saphira-D sources.
Package streams
Three streams, differing in pace and init coverage.
main Original
The stable stream. Valid for Saphira. It can be used on Saphira-D too, but that is discouraged. Prefer hatchling there.
latest Testing
The testing stream, newer than main and the broadest in package coverage. Valid for both Saphira and Saphira-D. Prefer hatchling where it covers what you need.
hatchling Active
The latest tested packages, already including the systemd unit work. Valid for both Saphira and Saphira-D. It is the most recent stream and should be used in favour of latest where it covers your packages; latest still includes more packages overall.
Systemd and the streams
main, latest and hatchling are all built from the same Saphira / Saphira-D sources, but they differ in freshness and init coverage. hatchling is the latest and already carries the systemd unit work (the nginx and php-fpm units on this site), so it should be used in favour of latest where it covers the packages you need. latest is still useful because it includes more packages overall, and remains valid for both Saphira and Saphira-D. main is the stable stream and is valid for Saphira; it can run on Saphira-D too, but that is discouraged. hatchling is the better choice there.
Hosted on Saphira-D
packages.saphira.vm2.uk itself runs on Saphira-D, a systemd and musl-libc based system that keeps /bin, /usr/bin, /sbin and /usr/sbin deliberately separate. Our custom musl systemd package maintains this split end to end, and we have no intention of adopting merged-/usr. There is no better way to showcase an operating system than to have it serve its own content, and it underlines our commitment to move every one of our servers off Alpine Linux and Arch Linux based hosts.
Systemd units
The concrete unit files referenced above, already part of hatchling and available here now.
Saphira-D is the in-testing systemd version of Saphira. The default Saphira design uses the OpenRC init system, and a systemd-booted Saphira Linux OS can fall back to an init.d based system with init=/sbin/openrc-run. OpenRC scripts are not removed, but several systemd.service units are still missing, nginx and php-fpm being two of them. The units below are published here so a Saphira-D (systemd) install can run the services today, ahead of them landing in hatchling. Each page carries the unit file, install steps and the exact enable/disable commands.
- nginx.service Saphira webDragon nginx: terminates TLS 1.3 and proxies PHP requests to php-fpm85 over the Unix FastCGI socket.
- php-fpm85.service PHP 8.5 FastCGI Process Manager, listening on /run/php-fpm85/php-fpm.sock.
The default Saphira uses OpenRC and already ships the equivalent init.d scripts; the gap is systemd units, which hatchling is closing one service at a time. Until then, drop the unit files into /usr/lib/systemd/system/ and enable them as shown on each page.