KITPro Server 0.1.0-alpha.13: A broader trusted catalog with bounded networking
KITPro Server v0.1.0-alpha.13 was published on September 26, 2026 as a public alpha. It expands the trusted application catalog to 20 entries, adds typed configuration and bounded network services, strengthens recovery, and qualifies Ubuntu 26.04 LTS as a Supported platform.
Release record
KITPro Server 0.1.0-alpha.13 · Public alpha prerelease
Original release: . Retrospective release coverage. This article was published on . Created .
KITPro Server v0.1.0-alpha.13 was published on September 26, 2026 as a public alpha. It expands the trusted application catalog to 20 entries, adds typed configuration and bounded network services, strengthens recovery, and qualifies Ubuntu 26.04 LTS as a Supported platform. This is retrospective coverage of the public release, not a recommendation to replace current software with a historical alpha.
KITPro Server manages trusted self-hosted applications through a browser on a Linux host. It is a separate layer from the KITPro Linux Server distribution. Alpha.13 is meaningful for homelab administrators who want a wider catalog while keeping storage, network exposure, and recovery rules visible.
Five additions with specific operating limits
Forgejo adds a managed /data directory and HTTP access without exposing Git over SSH. Plex uses managed configuration and read-only media, CPU-only operation, and no automatic remote access. Nextcloud is an Experimental SQLite profile intended for small instances.
Pi-hole enters as an Experimental DNS-only Network Service. Its trusted bindings use TCP and UDP port 53, while administration remains on a loopback endpoint. Syncthing is an Experimental manual-peer TCP-only profile with a loopback GUI and fixed TCP port 22000. It does not enable discovery, relays, NAT traversal, QUIC, or UDP publication.
Those limits are part of the release contract. A familiar application name does not imply that every upstream deployment topology is supported. Syncthing qualification covered manual pairing, explicit TCP addresses, bidirectional transfers verified by SHA-256, configuration restore, and preserved device, peer, and folder state. External /sync content remains outside KITPro-managed backup.
Networks and runtime generations remain separate
Schema-v8 application networking supports multiple bindings, TCP and UDP, trusted fixed ports, and transport-aware conflict checks. Each application generation keeps its own bridge network. KITPro does not combine those networks or shorten retained-generation guarantees to save address space.
Supported hosts require an operator-selected Docker default address pool that does not overlap existing routes or networks. KITPro checks routes, Docker networks, and available child networks. It does not edit Docker's daemon configuration or choose a universal network range for every installation.
Runtime removal preserves the installation identity, managed data, external-storage choices, and generated secrets. Reconciliation checks runtime and image identity, mounts, bindings, and candidate cleanup before advancing a committed generation. Failed installation retries retain the original installation and its storage choices rather than silently starting over.
Backups and package transitions
Application backup format version 1 protects declared managed files, detected SQLite databases, and generated secrets for restore into the same existing installation. Imported storage is excluded and untouched. Backups are local, root-owned archives with restrictive permissions; KITPro does not encrypt them. Generated application secrets remain root-bound plaintext in helper state and those restrictive backups.
The supported Debian alpha.12-to-alpha.13 transition verifies the incoming package, both databases, and a paired backup set before unpacking and migration. It migrates schema 13 to 14. Arch uses a package-bound upgrade wrapper and pre-transaction hook that checks the incoming package and AppArmor profile before pacman changes files. Follow the tagged upgrade instructions and preserve an independent backup before changing an existing system.
Platforms and release status
Debian 13 amd64, Ubuntu 26.04 LTS amd64, and fully updated Arch Linux x86_64 with linux-lts are Supported. Supported hosts use rootful Docker, systemd, and enforcing AppArmor. Rocky Linux 10 and Podman remain Experimental. Rocky application installation is unavailable in this release because its adapter does not implement the required staged-generation lifecycle; the API fails before creating runtime or network state.
The published GitHub release is a prerelease. Its copied release-note body retains preparation language saying publication is a separate action; that frozen text does not change the observed public release date. Alpha.13 does not include a reverse proxy, ACME management, Cloudflare Tunnel integration, automatic public access, host-to-host restore, imported-storage backup, or destructive application-data deletion. Verify downloads against the release checksum manifest and review the full limitations before installation.
Resources
Official alpha.13 release, packages, and checksums
Product screenshots
