What is SubakoOS?

SubakoOS is a self-hosted server-management platform with a focused web interface. It is not a Linux distribution. You install it on a supported Fedora or Arch Linux host, and it gives you one place to operate storage, containers, networking, backups, updates, users, and home services.

The basic model

SubakoOS runs as a native systemd service on your server. The browser interface talks to a FastAPI backend on that same host. Normal application work runs under a dedicated, non-root subakoos account, while narrowly defined host operations pass through a root-owned helper and an allowlisted sudo policy.

Browser
  -> TLS reverse proxy
    -> SubakoOS FastAPI service
      -> application services
        -> allowlisted privileged helper
          -> Fedora or Arch Linux host

This native model matters. Host management needs an accurate view of PAM users, systemd, block devices, networking, and the filesystem. A conventional Docker deployment would hide or distort those boundaries, so it is not currently supported.

Who it is for

• Homelab operators who want a coherent alternative to scattered scripts and dashboards.
• Families who want shared lists, calendars, announcements, and home-status tools alongside server administration.
• Users seeking Private AI capabilities, with optional, locally-hosted Ollama and Hermes Agent integrations that keep data and processing entirely on their own hardware.
• Developers building trusted plugins or automating their own SubakoOS instance.

Design priorities

Host control without permanent root

The web service is deliberately unprivileged. Sensitive actions are constrained to specific commands, validated inputs, recent-authentication checks, and route-level authorization.

Local ownership

Your instance, credentials, database, backups, and integrations remain on infrastructure you control. SubakoOS does not require a hosted control plane.

One operational surface

Storage, containers, health, networking, backups, users, notifications, and home tools share a common navigation and permissions model.

Where to go next

Start with Installation to prepare a supported host. For the security boundary and system layout, read Architecture. Developers can begin with the API guide or Plugin SDK.