Release a server

Saka Panel is free with no lock-in, and you can leave cleanly at any time.

No lock-in

Your servers stay yours. If Saka Panel cannot be reached, or the Saka agent is removed from a server, your apps and databases keep running as usual. Saka never stops or breaks anything as a penalty. Only the management stops: monitoring, notifications, and managing through the panel or AI.

Release a server: the clean way to leave

Open the server details, go to the Zona berbahaya (Danger zone) section, and press Lepas server (Release server). Before you agree, a dialog shows exactly what will be removed from that server. Type the server name to continue.

What gets removed

• Apps installed by Saka, with their data (conversations, memory, settings, backups) and their images.
• Database clusters and proxies on that server, the WireGuard network, and its fencing rules.
• Swap that was created by Saka.
• A firewall that was turned on by Saka is turned off, so ports on the server are no longer closed.
• Docker, if it was installed by Saka, but it is left in place if you have other containers of your own.
• Saka's data and settings; the agent then removes itself last.

Saka marks everything it creates at the time it creates it (in /var/lib/sakapanel/tanda/), so anything that existed before Saka is not touched. The server stays on and stays yours. After it is released, monitoring, notifications, and management through the panel or AI stop.

Keep a backup first (optional)

Tick Simpan cadangan data aplikasi di server dulu (Save a backup of app data on the server first). The app data is packed into:

/root/sakapanel-cadangan-YYYYMMDD-HHMMSS.tar.gz

This file is owned by root and can only be opened over SSH. If the backup cannot be created (for example the disk is full), nothing is removed.

A server that is disconnected

Saka cannot clean up a server that is not connected. Your options:

1. Better: turn the server on until it reconnects, then release it from the panel.
2. Or just remove it from the panel list, then run this command on the server over SSH so everything Saka installed is removed too:

sudo saka-agent lepas

Through the API

Get the plan first, show it to the user, then send the confirmation with the server name:

curl -s https://app.saka.work/api/v1/server/<id-server>/lepas \
  -H "Authorization: Bearer $SAKA_TOKEN"

curl -s -X DELETE https://app.saka.work/api/v1/server/<id-server> \
  -H "Authorization: Bearer $SAKA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"konfirmasi": "nama-server", "simpan_cadangan": true}'

For a disconnected server, add "hapus_saja": true, then run sudo saka-agent lepas on the server. Releasing a server is not available through MCP.