Looking after a server

Overview

Overview on a server shows how it is doing without typing anything: processor, memory, disks and services, updating live. All servers (the start screen) checks every server at once and tells you which one needs attention. Nothing needs to be installed on the server for this.

Services

The list shows what is running. Each service has Start, Stop, Restart and Logs (live). The user you log in as needs permission to run these (sudo without a password for systemctl); the error message tells you if not.

Docker and Compose

If the server uses Docker you see its containers with their load, live logs, and buttons to start, stop and restart. Shell opens a terminal inside a container. Compose stacks (a group of containers described in one file) can be pulled, started, restarted, stopped and edited. When you edit, the app checks the file first and keeps the old one as .kr-bak, so a typo cannot take the service down.

Podman and Kubernetes (k3s) work in the same way.

Saved commands

Do you type the same steps on every server? Save them once under Commands. A command is a list of steps; write {{name}} in a step to ask for a value when you run it. Press Run, pick one server or a whole group, fill in the values, and watch the output arrive per server. Every run is recorded.

From template gives you ready-made ones (server health, collecting logs, updating a Compose stack).

Library and Knowledge

• Library is your own notebook of commands, SQL queries and notes. Every code block has Copy and Send to terminal. Sending only pastes the text; you read it and press Enter yourself.
• Knowledge is a built-in set of guides for Linux, Docker, Compose, web servers and running a project, in English and Croatian, available offline.

Notes

Every client and server has its own notes (contacts, agreements, quirks). They are searchable from the top bar.

Backing up services

If a service on your server has its own backup script, the app can run it, pull the result to your computer, check that the file arrived intact, and restore it later. You configure this once per server.

Letting Claude help (optional)

If you use Claude Code, you can allow it to run commands or move files on your servers through Kultivat Remote. It never sees your passwords; everything is off by default and you switch on only what you want in Settings → Security.