Web
Saphira Linux webDragon
A Saphira feature that turns a normal installation into a managed web platform: Nginx, PHP-FPM 8.5 and Node.js, with TLS you do not have to babysit. You own the machine; webDragon removes the repetitive systems administration.

What webDragon is
webDragon is a Saphira feature set for running a modern web server on Saphira Linux. It starts from a normal Saphira installation and assembles the web stack — Nginx, PHP-FPM 8.5 and Node.js — using ordinary Saphira packages, then gives you a simple way to describe a site and have that intention turned into correct, readable configuration.
It exists because the interesting part of running a website is the site, not the virtual-host boilerplate, the PHP pool, the proxy stanza or the certificate renewal. webDragon takes responsibility for that machinery so the administrator does not have to hand-build it for every domain.
The core idea
The machine can live at home, in an office, in a datacentre, or eventually in a public cloud. It is yours: AKADATA may manage that server for you as a service, but AKADATA does not need to host it. This is host-it-yourself infrastructure, not another SaaS product.
Not a control panel
webDragon is deliberately not a hosting control panel and should not become one. There is no large dashboard, no SaaS management layer and no proprietary hosted control plane. It is a Saphira feature that removes repetitive systems administration while leaving the server understandable and under the owner's control.
Built on Saphira packages
Everything webDragon uses is already a Saphira package: Nginx, PHP-FPM 8.5, Node.js and Certbot. The feature is delivered by a small tool, saphira-site, shipped in the saphira-tools package and installed at /usr/sbin/saphira-site. It builds on the operating system and its package manager instead of becoming a separate appliance or distribution.
Part of a family of Dragons
webDragon is one member of a family of Saphira feature sets. mailDragon handles self-hosted mail; databaseDragon will simplify database operation; and an application-specific feature such as wordpressDragon could eventually compose the web and database capabilities. Those later Dragons are separate efforts and do not expand the present webDragon scope.