Spawn of Saphira

Hatched is where the new generation becomes a distributable Saphira image. Spawn of Saphira is what comes next.

Spawn is the self-hosting stage: the point where Saphira has the complete package base, build tooling and distribution machinery required to create another Saphira system from Saphira itself.

That work is still in progress. It may take months. There is no finished installer, installation ISO or general-purpose image creator yet, and this page does not pretend otherwise.

The current Saphira Beta and Saphira-D images are already fully functional systems. Spawn does not replace their package universe.

They share the same underlying Saphira package layout and package repository. The work being done toward Spawn extends that base with the machinery needed to reproduce, install and create Saphira itself.

That matters, because otherwise a reader may hear "future self-hosted version" and assume the current images are prototypes that become obsolete. They are not.

Every one of these systems already serves real content. This website itself is Saphira hosting Saphira.

Hatched produces something that can be distributed.

Spawn produces the machinery that can produce the distribution.

That is the cleanest distinction on this page: Hatched is a milestone image; Spawn is the system that can make the next one.

The Dragons belong to Saphira, not to one particular image. webDragon, mailDragon, databaseDragon, vpnDragon, dnsDragon and aiDragon are intended to run across the common Saphira package base, whether the host began as Saphira Beta, Saphira-D or a future Spawn-created installation.

OpenRC or systemd changes how services are started. It does not change what the Dragon is.

             Saphira package base
                    |
        +-----------+-----------+
        |                       |
    Saphira Beta            Saphira-D
      OpenRC                  systemd
        |                       |
        +-----------+-----------+
                    |
              the Dragons
        web / mail / database
        vpn / dns / ai
                    |
                    v
          Spawn of Saphira
        Saphira builds Saphira

The Dragons are designed against the shared Saphira package base, not against one particular image or init system.

• webDragon
• mailDragon
• databaseDragon
• vpnDragon
• dnsDragon
• aiDragon

The objective has never been another Linux image for the sake of having another Linux image.

The objective is ownership.

Freedom to host your own web services. Freedom to run your own mail. Freedom to operate your own databases, DNS, VPN and AI services. Freedom from a SaaS provider deciding that something cannot be done, should not be done, or is "not sustainable".

Saphira started from the opposite premise: own the machine, own the service, own the data, and prove that simple local infrastructure still works.

Egg is building. Hatchling is being tested. Hatched is becoming a distributable image.

Spawn is the point where the circle closes: Saphira builds Saphira.

That is when the Dragon no longer needs the forge that first created it.

Return to Hatched, or the package repository.