Docs / Security & privacy

Security & privacy

The basic principle is simple: Saka only manages. Your data stays on your server.

Saka does not store your data

Saka Panel does not store or relay user data. Website files, database contents, replication streams, backups, AI keys, and the assistant's chat history and memory all live on your server. Load balancer traffic does not pass through Saka either.

What Saka stores (metadata)

Stored by Saka PanelNot stored by Saka Panel
Account (email, password hash)Database passwords
Server list, IP, OS, latest status, and the name of the network that owns the IP (e.g. VPS provider or ISP) for internal statisticsAI API keys, Telegram bot tokens, OpenClaw gateway tokens
Names and members of database clusters and load balancersApp log contents
Task history (command, a summary of inputs without secrets, result)Database contents, files, backups
Alert history, Telegram notification connectionMetrics history (kept for 30 days on your server)
API tokens (stored encrypted, only the last 4 characters are shown)WireGuard private keys

Secret inputs used when installing an app only pass through to the agent. The history only records a summary, with secret values masked (•••).

Passwords are read from the server

TLS & networking

Firewall

The firewall is turned on only when you ask, after Saka shows you the ports currently in use. SSH is always left open. Afterwards, the agent makes sure apps can still reach the internet; if they cannot, the firewall is turned off again. On load balancer target servers, the app port is opened only for the balancer IPs. Details in The Readiness card. Once on, the Firewall card on the server page lists the open ports: Open port for a new app (the firewall stays on), Close for ports no longer used, and Turn off when needed (with a confirmation). SSH, Saka site, VPN, and platform ports are marked required and cannot be closed from the panel.

Forensic audit (stage 1)

The Forensic audit card on the server page snapshots the sensitive state of the server a few minutes after the agent starts: users and sudo rights, SSH keys per account, cron, systemd units, listening ports, SUID files, Docker containers and images, key config files (sshd, hosts, resolv.conf, passwd, shadow, ld.so.preload, rc.local, PAM), and the package list. Every hour the server is compared with that baseline. Changes made by Saka tasks are folded into the baseline silently; anything else (you over SSH, an AI agent, an intruder) is listed on the card and sent to Telegram, for example "SSH keys: added root: ssh-ed25519 …". Package changes are only recorded. Everything is read-only: nothing is modified while snapshotting. Check now compares immediately; Set as baseline is for after you reviewed the changes and are sure they were all yours. This is evidence for an internal investigation, not legal evidence: a valid chain of custody needs procedures beyond Saka's reach.

Event timeline (stage 2). On the same card, pick 24 hours, 3 days, or 7 days to see events in order: SSH logins per user and IP with failed-login counts, sudo commands, Docker container events, packages installed or upgraded, boots, system errors, changes outside Saka, and Saka tasks (who ran them, through which channel). Everything is read from logs already on the server; shell history is deliberately not read since it has no timestamps and anyone can edit it.

Evidence bundle (stage 3). Pick a range from 24 hours to 30 days and press Create evidence bundle: one zip with the baseline, changes, timeline, raw log copies (sshd, sudo, system errors, docker events, dpkg), and a laporan.md report readable by non-technical people. Every file inside has a SHA-256 (SHA256SUMS), that hash list is signed with the agent's Ed25519 key (the private key stays on the server and is never sent to Saka), and the public key plus the zip hash are recorded in Saka when the bundle is created. VERIFIKASI.md inside the zip lists the sha256sum and openssl pkeyutl commands to verify it. Deleting the file from the server keeps the hash record. The zip also contains laporan.pdf. For an auditor or board member without a Saka account, Share link creates a read-only link (valid 7 days, revocable) with the summary, hash, the public key as recorded by Saka, verification steps, and a download button; downloads through the link are logged in the action history.

Server security

The Server security card on the server page gives a score from 0 to 100 and a VPS checklist. Every row that is not safe yet has a Fix button:

AI agents read this list through server_perbaiki kind keamanan-cek.

Saka Shield

A server-level guard that does not depend on your app (WordPress, Laravel, Git apps, n8n, and SSH too). New servers: on automatically from install, with your IP at the time you created the install command (or pressed Create server in a cloud account) excluded. Existing servers: turn it on from the server page, Saka Shield card. The agent reads SSH and web access logs every 20 seconds and blocks IPs that within 10 minutes:

Blocks are applied in nftables for every port and Docker container, and in Caddy for visitors coming through a load balancer, tunnel, or Cloudflare (their real IP is read from trusted headers). Blocks last 60 minutes; IPs blocked again within a day are blocked for 24 hours. Blocks expire on their own even if the agent stops.

So you are never locked out: your IP when turning it on from the panel is excluded automatically, as are connected SSH sessions, private IPs, Cloudflare ranges, the server's own IPs, and load balancer nodes. Add your office IP under Exceptions; a wrong block can be lifted with one click. In a real test, an attacking VM was blocked on every port less than 45 seconds after 8 SSH attempts, and again after probing 8 weakness paths. MCP: perisai_status, perisai_atur, perisai_lepas.

Advanced settings

In real tests: 900 fast requests from one IP were blocked after passing 600 per minute; blocking Singapore closed the web for an attacking VM in Singapore while its SSH stayed reachable and visitors from Indonesia were unaffected; the WAF in block mode rejected SQL injection, XSS, and path traversal (403) without affecting regular pages and searches.

Database fencing

A database node that is not fit to accept writes closes its own database port to outside traffic (TCP RST), checked every 2 seconds. This stops apps from writing to the wrong node and makes clients move to a healthy node. Details in Databases: Fencing.

A limited agent

Emergency terminal

Almost everything on a server has a button in the panel. For emergencies, the server page has a Terminal: a root shell on the server through the agent, with no open port and no SSH key.

Account security

Team and roles

The account owner can invite others in Settings, Team. Invitees sign in with their own Saka account (the email must match the invitation), so no password is shared.

Activity log

Account menu, Activity log, records every change in your account: who (you, a team member's email, an API token's name, or an AI agent through MCP with the tool name), when, from which IP, the target (e.g. server or site name), and whether it succeeded. Filter by AI agents, team, API tokens or panel; AI agents can read it with the MCP tool riwayat_aksi. Each row reads as a sentence (e.g. "Created database user analyst"), not an action code; on a phone rows become compact cards and the IP is hidden so they fit. Inputs such as passwords or env variables are not recorded, only the action. Kept for 180 days; visible to the account owner and members with the Admin role.

When the Saka team helps you

If you ask for help, the Saka team can open your panel or run safe actions on your server (read an app's log, restart an app, check a site, create swap). The rules:

Stopping using Saka

Saka never stops your apps because a server is disconnected or the agent is removed. To leave cleanly (removing everything Saka installed), use Lepas server (Release server). Details in Release a server.

If Saka Panel goes down

While Saka Panel cannot be reached
Websites, apps, OpenClawKeep running on your server.
DatabasesKeep running, and still fail over automatically if one server goes down (the primary is elected among your own servers).
Load balancersKeep running. Saka is not in the traffic path or the DNS path.
OpenClaw automatic updatesKeep running, handled by the agent itself.
Panel, API, MCPTemporarily unavailable.
Telegram notificationsTemporarily not sent.
If it stays disconnected for a long time, or the agent is removedApps and databases keep running; Saka never stops them.