State drifts
KITPro Server's recorded state can differ from what the container runtime shows.
PRODUCT / SERVER RELEASE / ALPHA.15 STATUS / PUBLIC ALPHA
Manage the Linux host. Operate its applications.
One open-source platform for native Linux administration and trusted application management, with scoped operations, audit evidence, and recovery.
Active alpha software. Breaking changes and incomplete workflows may occur. Review the current limitations before using KITPro Server with important data.
KITPro Server v0.1.0-alpha.15Published GitHub prerelease
Open SourceSource, releases, and architecture on GitHub
No required cloudCore operation stays on the Linux host
Native Host Administration
Understand the host before changing it.
Alpha.15 adds native Linux visibility and narrowly controlled administration without turning the API into a generic root shell.
Unified Dashboard and System HealthA shared view of CPU, memory, load, storage, networking, service state, protection boundaries, and actionable health explanations.
Services and journald LogsCompact systemd service and journal views with search, filters, pagination, curated actions, scoped authorization, and audit history.
Storage AdministrationInventory, capacity, protection state, controlled mount operations, and recoverable persistent mounts for explicitly approved resources.
Network AdministrationInterfaces, addresses, routes, DNS, diagnostics, and transactional systemd-networkd changes with independent rollback for approved resources.
Scoped securityHost inspection, logs, service, storage, network, audit, and security administration remain separately authorized and helper-revalidated.
Operation historyAccepted, rejected, completed, failed, timed-out, rolled-back, and uncertain outcomes remain inspectable instead of being inferred from silence.
Installation is only the beginning.
Self-hosting gives you ownership. Keeping that ownership usable over time means coordinating runtime state, persistent storage, updates, backups, failure recovery, and destructive actions across several system tools.
Failures interrupt transitions
A lost response or host restart can leave the outcome unknown.
Data outlives machinery
Containers are replaceable. Installation identity and user data are not.
Ownership should remain workable after install day.
Operating an application should not require you to manually coordinate every runtime generation, storage path, migration, backup, recovery action, and destructive transition.
KITPro Server moves that coordination into one consistent lifecycle. It keeps uncertainty visible and leaves the standard Linux and container foundations available for inspection.
Coordinate the lifecycle. Keep the evidence.
Alpha.15 applies these principles through durable operations, runtime generations, managed-storage identity, reconciliation, and bounded repair.
Verify before changingKITPro Server checks recorded identity, current runtime evidence, and the requested transition before privileged work begins.
Preserve before replacingUpdates prepare a candidate runtime generation while the last proven generation and persistent storage remain available for recovery.
Represent uncertainty honestlyA lost response, unavailable runtime, or mixed restore state becomes an operation to inspect. KITPro does not infer success from silence.
Keep durable state separateInstallation identity and managed data survive replacement of disposable containers and runtime configuration.
What works todayApplication Management
Operate the applications that make the server useful.
The trusted application lifecycle remains alongside Host Administration: deployment, runtime state, ingress, HTTPS, storage, readiness, diagnostics, backup, and recovery use the same accountable operation model.
Read the alpha.15 release record01Trusted, digest-pinned application catalog and declared configuration.
02Docker application deployment, lifecycle, readiness, and diagnostics.
03Managed ingress, HTTPS certificates, and explicit application exposure.
04Persistent application storage across disposable runtime generations.
05Application and host-state backup within documented recovery boundaries.
06Durable operation history, update outcomes, and release provenance.
Alpha means important boundaries remain.
- Service management is limited to curated units and action-specific policy; unknown and protected services remain denied.
- Storage mutations require exact approved resources and destinations; disk formatting, partitioning, RAID, LVM, and ZFS mutation are excluded.
- Persistent mounts require explicit policy, stable filesystem identity, atomic configuration, and independent recovery.
- Transactional network mutation is narrowly scoped to approved systemd-networkd resources; primary management interfaces remain protected.
- Journal access is disabled by default and still depends on the host feature gate and operating-system permissions.
- Rocky Linux 10 remains Experimental, and host capabilities vary with the active Linux backend and security policy.
- KITPro Linux production repository availability depends on its separately signed immutable dependency generation.
Supported platforms
A narrow public baseline.
Support reflects the published package contract and capability matrix. Installed Host Administration qualification covers Ubuntu 26.04 and KITPro Linux; backend-specific privileged capabilities can differ by platform.
Installed-service qualified: Ubuntu 26.04 LTSInstalled-service qualified: KITPro LinuxSupported package contract: Debian 13Supported capability matrix: Arch-family LinuxExperimental: Rocky Linux 10 with Podman
Experimental
Outside the Supported alpha.15 baselineRocky Linux 10 and Podman
The experimental path uses Podman, Quadlet, systemd, and SELinux. Package, policy, host checks, and reboot recovery passed, but the existing staged-generation lifecycle limitation remains. Rocky is not a Supported platform.
Review the experimental Rocky pathReady to evaluate the current alpha?
Start with the limits, then choose the supported install path.
KITPro Server is active alpha software. Breaking changes and incomplete workflows may occur. Review the current limitations and keep an independent backup of important data.