Saki Panel
An open-source server operations panel with AI in the workspace.
Manage Minecraft, Steam, Docker, and ordinary processes from one web console. Saki uses live logs, files, and node metrics to help investigate incidents and can act after authorization.
Website · Quick start · Download a release · 简体中文
https://github.com/user-attachments/assets/99a8d410-c079-4368-86c9-f847413d4580
Beyond the panel
Make the workspace your own, or bring Saki to your desktop. Two more places to explore in the Saki family.
Screenshots
Version 5.0 puts Saki Assistant, live system metrics, and multiple workspaces on the overview page. The poster above uses an unmodified capture of the running app; click it to open the original screenshot. The examples use local demo services.
Review file changes, select what to commit, and browse history from the instance's Git workspace.
Saki Panel brings instances, nodes, terminals, files, databases, and access control into one workspace. When something fails, Saki can inspect the current instance's status and logs and propose actions without making you copy context between a panel, a terminal, and a separate chat.
What you can do
| Area | Capabilities |
|---|
| AI-assisted operations | Ask about status and logs, inspect or edit workspace files, manage instances, and run scoped commands. Supports Skills, MCP, and image or log attachments. |
| Saki Watch | Record unexpected exits and error fingerprints, diagnose incidents, review patches, and roll back a change when verification fails under supported conditions. |
| Instances and nodes | Connect remote Linux servers over SSH. Manage nine instance types across Daemon nodes, including Minecraft, Steam, Docker containers, and Compose stacks. |
| Daily administration | Web terminal, file editing and transfers, visual Git diffs, SQLite / MySQL / PostgreSQL / Redis, scheduled tasks, and instance templates. |
| Visibility and access | Cluster dashboard, reliability reports, audit history, and role-based access. Send incident notifications through webhooks, DingTalk, WeCom, or Telegram. |
| Extensions | Install themes, Saki skins, games, widgets, and locales. Import optional operations packs with templates and runbooks. |
Saki can use local Ollama or LM Studio models, or a cloud provider configured in Settings. Local inference keeps model requests on your chosen local endpoint; cloud models, online plugins, and operations packs use external services when selected.
Quick start
Run locally from source
Requires Node.js ≥ 22.13 and npm ≥ 9.
git clone https://github.com/EthanChan050430/Saki-Panel.git
cd Saki-Panel
npm install
npm run db:push
npm run dev
Open http://localhost:5478. The Panel API defaults to port 5479 and the local Daemon to 5480. The development login is admin / admin123456. Change the default password and secrets before making the services reachable from other devices.
Development start scripts are available at scripts/windows/start-dev.ps1, scripts/linux/start-dev.sh, and scripts/macos/start-dev.command. You can also choose a compatible package from Releases, when one is available for your system.
Use prebuilt Docker images
Download docker-compose.ghcr.yml into your deployment directory and create a .env file:
JWT_SECRET=replace-with-a-long-random-secret
ADMIN_PASSWORD=replace-with-a-strong-password
DAEMON_REGISTRATION_TOKEN=replace-with-a-separate-random-token
docker compose -f docker-compose.ghcr.yml pull
docker compose -f docker-compose.ghcr.yml up -d
The default web address is http://localhost:5478. For remote or public deployments, set WEB_ORIGIN, PANEL_PUBLIC_URL, and PANEL_CORS_ORIGINS to your actual origins, configure HTTPS for Web, Panel, and remote Daemons, and limit exposed ports. Node tokens authenticate requests; the default HTTP transport does not encrypt them. The Compose file mounts the Docker socket into the Daemon, so review the permissions granted to that node.
To build the images from source instead, use docker-compose.yml, supply the same secrets in .env, and run docker compose up -d --build. See .env.example for more options.
How Saki helps investigate
Saki combines the current instance's state, logs, files, and resource metrics with scoped tools for instance and file operations. Actions have risk levels; operations requiring approval are shown before execution, and the Daemon blocks certain dangerous commands. Results depend on the selected model, granted permissions, and node environment.
For example, ask it to inspect logs before a crash and identify a likely configuration error, or to restart a service and watch its new logs. You can attach screenshots and log files. Save recurring procedures as Skills or connect external tools through MCP.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
