Debian & Ubuntu
.deb package, systemd service.
sudo apt install ./kubuno-core_*_amd64.debInstallation
Install Kubuno
Four ways to install, one single destination: a server that starts with the machine and greets you with its setup wizard. Choose the one that matches your environment — each is documented from end to end.
Fastest · Linux
Docker, in one command
The script installs Docker if it is missing, deploys Kubuno and its database, generates the secrets and sets up a daily automatic update. Twenty-one modules are already in the image: nothing else to install.
curl -fsSL https://raw.githubusercontent.com/kubuno/docker/main/install.sh | sudo bashYour instance then answers at http://<server-ip>:8080. Add --domain and --email for a domain name and an HTTPS certificate that renews on its own.
Without Docker
A package for your system
The server is packaged for every platform: it installs like any other system software and registers itself as a service. The artefacts are published on the core's Releases page, built by continuous integration at every version.
Fedora, RHEL & openSUSE
.rpm package, systemd service.
sudo dnf install ./kubuno-core-*.x86_64.rpmWindows
.exe installer that registers a Windows service. Windows 10/11 and Server, 64-bit.
Windows guidemacOS
.pkg package that registers a launchd daemon. Apple Silicon.
macOS guideThese packages do not bundle a database. Plan for a reachable PostgreSQL 16 — on the same machine or elsewhere. Only the Docker method provides one for you.
No default password. After the installation, open the server in a browser: the wizard has you choose the database and the administrator account, then writes the configuration itself.
Next
Adding the applications
The server on its own brings neither files, nor calendar, nor mail: those are modules, and you install only the ones you need. On a Linux installation, the administration console installs them in one click — the server downloads the package, checks its fingerprint and starts the module without restarting the instance. With Docker, they are already there.
From the console
Administration → Marketplace, then “Install”. No access to the server needed.
From a package
Each module publishes its own packages, on its own repository.
Unsure which method to pick?
The administration manual compares them side by side: what you need, what you get, how to update and how to uninstall.