What's new in Saka Panel. 147 releases so far. Agent updates roll out automatically and are signed, so your servers stay current without you doing anything. Want something that isn't here? Request a feature.
Nov 152026
Domain names in the egress lists
The seen and blocked lists now show the domain name the app asked for, not just the IP.
Apps
- FeatureSaka passively reads the DNS replies a container receives and remembers which name each IP answered. The monitor, allowed and blocked lists show that name next to the IP, with an Allow domain button that adds it to the allow list (safer than an IP for services behind a CDN). Nothing is changed or stored beyond name and IP; DNS over TCP, DoH or DoT is not visible, so those stay IP only.
Oct 182026
Forensic audit, stage 3: signed evidence bundle
One zip per time range with the baseline, changes, timeline, raw logs, and a plain-language report; every file hashed, the hash list signed by the agent, and the zip hash recorded in Saka off the server.
Servers
- Evidence bundleFrom the Forensic audit card pick 24 hours to 30 days and create a bundle: garis-dasar.json, perubahan.json, linimasa.json, log/ (sshd, sudo, system errors, docker events, dpkg), laporan.md for non-technical readers, SHA256SUMS, an Ed25519 signature over it, the agent's public key, and VERIFIKASI.md with the openssl commands to check it all.
- Recorded off the serverThe zip's SHA-256 and the signing public key are stored in Saka when the bundle is created, so a bundle altered on the server afterwards no longer matches. Download from the panel; deleting removes the file but keeps the record.
- For AI agentsserver_perbaiki forensik-bukti (dari/sampai) and forensik-bukti-daftar.
Oct 182026
Forensic audit, stage 2: event timeline
One timeline per server answers "what happened between X and Y": SSH logins, sudo, Docker, packages, boots, system errors, changes outside Saka, and Saka tasks.
Servers
- Timeline on the Forensic audit cardPick 24 hours, 3 days, or 7 days. Sources: journal sshd (logins per user and IP, failed-login counts with top IPs), sudo commands, Docker container events (start, stop, exit code), dpkg.log or dnf history, boots, journal errors (deduplicated per unit), stage-1 changes, and Saka tasks with who ran them. Filter by source with one click. Read-only; shell history is deliberately not read (no timestamps, editable by anyone).
- For AI agentsserver_perbaiki forensik-linimasa with dari/sampai (unix), up to 30 days.
Oct 92026
Kubernetes app domains keep working when a node dies
Every cluster gets an ingress address that always points at healthy nodes, the panel checks each app domain's DNS, and Traefik retries requests away from dead nodes in 3 seconds.
Kubernetes
- Ingress addressapp-<id>.k8s.saka.work has an A record for every node that is Ready, connected and answering on port 80, checked every minute. Point subdomains at it with a CNAME; root domains get A records for all IPs. Replaces the old advice of pointing a domain at any single node. New MCP tool k8s_domain.
- Domain checkEach Ingress domain shows whether it is a CNAME to the cluster, points at all nodes, only some nodes, somewhere else, or nowhere yet, using a public resolver.
- Faster retriesTraefik now gives up on a silent backend after 3 seconds instead of 30, so the retry middleware moves to a live pod quickly. Applied automatically to existing clusters.