Docs / Getting started

Getting started

From creating an account to seeing your first server in the panel, usually in under five minutes.

1. Create an account

  1. Open app.saka.work/masuk/?daftar=1.
  2. Enter your email and a password (at least 10 characters).
  3. Press Buat akun (Create account).
No lock-in

Your servers stay yours. If Saka Panel cannot be reached or the agent is removed, your apps and databases keep running. To leave cleanly, see Release a server.

2. Add a server

Get a VPS from any provider. Requirements:

In the panel, open Server, press + Tambah server (Add server), give it a name, then press Lanjut: buat perintah pasang (Next: create install command). You get a one-line command like this:

Server terminal
curl -fsSL https://app.saka.work/pasang.sh | sudo sh -s -- <token-daftar>

Open a terminal on the server (with ssh root@IP-SERVER or your provider's web console), paste the command, and press Enter. The panel page updates by itself as soon as the server connects.

What the install script does, in order:

  1. Checks the OS, architecture, RAM, free disk space, and the connection to Saka Panel. If anything is missing, the script stops and explains how to fix it without changing anything.
  2. Downloads the agent and verifies its SHA-256 checksum. Corrupted or modified downloads are rejected.
  3. Registers the server to your account using the token.
  4. Installs the saka-agent systemd service and starts it.

The registration token is valid for 24 hours and can be used only once. If it expires, create a new command from the panel. The script is safe to run again: if the server is already registered, it stops without changing anything.

The agent updates itself automatically when the Saka Panel version changes: it downloads, checks the release signature and SHA-256, tests, then swaps. If any step fails, the old agent stays in use.

Supported OSes

Every OS below was fully tested on 28 Sep 2026 on a 1 vCPU / 2 GB VPS: install the agent, install OpenClaw, default security, create swap, turn on the firewall, check from outside (22 open, app port closed), then Lepas server (Release server) until clean.

FamilyVersionsNotes
Ubuntu22.04, 24.04, 26.04Firewall uses ufw.
Debian13Debian 12 could not be tested yet, so it is not on the list.
AlmaLinux8, 9, 10Firewall uses firewalld, Docker from the official Docker repository.
Rocky Linux8, 9, 10Same as AlmaLinux.
CentOS Stream9, 10Same as AlmaLinux.

3. The Readiness card

The server detail page has a Kesiapan server (Server readiness) card. The agent checks the server every 5 minutes and explains what is missing, along with how to fix it:

CheckWhat it looks at
Operating systemWhether the OS is one that has been tested.
RAMEnough for the agent only, for Hermes (1 GB), or for OpenClaw (2 GB).
DiskFree space. A warning if it is below what OpenClaw needs, an error if the disk is almost full.
SwapPresent or not. Can be fixed in one click.
FirewallActive or not. Can be fixed in one click, with a port check first.
Server clockSynced with NTP or not (important for SSL certificates and logs).
UpdatesWhether there are system updates waiting for a reboot.
DockerInstalled or not. Installed automatically when you install your first app.

Fix swap

Press Perbaiki (Fix) on the Swap row. Saka creates a 2 GB swap file (1 GB if disk space is tight) that stays active after a reboot, with low swappiness so swap only acts as a buffer. Running apps are not interrupted. Swap matters on small VMs so apps are not force-killed when RAM runs out.

Fix the firewall: ports are checked first

  1. Press Perbaiki (Fix) on the Firewall row. Saka first shows the ports currently in use on the server's public address, along with the programs using them.
  2. Tick the ports that must stay reachable from the internet. SSH is always left open so you do not lock yourself out.
  3. Press Aktifkan firewall (Turn on firewall). All other ports are closed.

Ubuntu and Debian use ufw, the RHEL family uses firewalld. After the firewall is on, the agent makes sure app containers can still reach the internet (for example Telegram or your AI provider). If they cannot, the firewall is turned off again.

A firewall turned on by Saka is recorded as created by Saka, so it is turned off again when you release the server. A firewall that existed before Saka is not touched.

4. Telegram notifications

  1. Open Pengaturan (Settings) in the panel, then press Hubungkan Telegram (Connect Telegram).
  2. Telegram opens in a new tab. Press Start on the Saka bot. The link is valid for 30 minutes.
  3. The settings page changes to Tersambung (Connected) by itself.

What gets sent to your Telegram:

Each problem is sent once, followed by one message when it recovers along with how long it lasted, so it does not become spam. The Saka bot currently only sends alerts. Commands and chatting with AI through the Saka bot will come later.

Next

Open your server and choose + Pasang aplikasi (Install app) for OpenClaw, or add a few more servers for multi-location databases and a load balancer. Have a site on cPanel or an old VPS? See Moving from cPanel and Move to another server.

Need a feature that does not exist yet? Suggest it from the Request a feature menu in the panel. Moving from AWS, Google Cloud, Azure, or other hosting and want help? Fill in the Migration help form. Details are in Feature requests & migration help.