Docs

Saka Panel Docs

A guide to using Saka Panel to manage your own servers: from installing the agent, WordPress and PHP sites, OpenClaw, multi-location databases, and load balancers, to connecting your AI agent.

The app is in Indonesian for now

The Saka Panel app at app.saka.work currently uses Indonesian. In these docs, button and menu names are written exactly as they appear in the app, followed by an English translation in parentheses, so you can find them easily.

What is Saka Panel

Saka Panel is an AI assistant for your servers. You have a VPS with any provider (DigitalOcean, AWS, a local provider, and others), install one small agent on it, and then manage it from one place: the web panel at app.saka.work, or your own AI agent (Claude, ChatGPT, or an agent you built) connected to the Saka MCP.

What you can manage with Saka Panel today:

Saka Panel is not a cloud company

Saka Panel does not sell servers and does not store your data. Your servers stay yours, with the provider you choose. Website files, database contents, AI keys, and the assistant's chat history all stay on your server. Saka only stores management data (metadata) such as server names and task history. The details are in Security & privacy.

Saka Panel is a personal project and is not owned by any hosting company. Cloud providers are mentioned only as places where you might run your servers.

Free, with Enterprise if you need it

How it works

  1. An agent on your server. One small program (saka-agent) is installed with a single command. It runs as a systemd service.
  2. The agent connects outward. The agent opens an outbound connection (secure WebSocket) to Saka Panel and sends a heartbeat every 15 seconds. No control port is opened on your server, so even servers behind a provider firewall can still be managed.
  3. You give instructions from the panel, the API, or MCP. Saka Panel passes them to the agent as tasks. The agent only knows a fixed set of commands (for example "create swap" or "install OpenClaw"), not arbitrary shell commands.
  4. Results are logged. Every task that changes a server is recorded in the history, together with its result and who requested it (panel, API, or MCP).
If Saka Panel goes down, your servers keep running

If Saka Panel cannot be reached, your servers and apps keep running. You just cannot manage them from the panel for a while.

Docs map