Deploy
Ships a commit, waits for the task to finish and re-runs a failed one.
Core
ServersProvisioning in 5 minutes SitesWordPress, Laravel, PHP DeployOn push, with no downtime DatabasesMySQL, users, privileges DockerContainers alongside your sitesAI and automation
AI assistantManage your server in plain words MCP server80 tools for Claude and Cursor Operations centerEvery task step with logs Auto-tuningSettings tuned to your hardwareObservability
MonitoringMetrics, APM and alerts LogsNginx, PHP, MySQL, application BackupsTo your storage, encrypted ClustersServers and sites togetherSecurity and access
SecurityFirewall, Fail2Ban, isolation NetworkingInterfaces, DNS, diagnostics Web terminalCommands without an SSH client ConfigurationPHP, Nginx, MySQL from the panelManage servers from Claude and Cursor
Who it's for
WordPress2-click install, WP-CLI LaravelQueues, Horizon, Reverb For web agenciesAll clients in one panel For freelancersClient servers in one placeComparisons
Deploykin vs Laravel Forge Deploykin vs Ploi Deploykin vs RunCloud Deploykin vs ISPmanagerA running server connects as it is: the panel scans its packages, sites and databases. There is a separate wizard for Ploi.
How to connect a running serverThe assistant knows your infrastructure: it reads logs and metrics, deploys, runs commands and SQL. Changes wait for your approval, and every call lands in the audit log.
Assistant chat
Why is shop.example.com returning 502?
Checking logs and metrics…
PHP-FPM hit its limit: pm.max_children = 16, all workers are busy. I suggest raising it to 32 and restarting the pool.
update_php_settingspm.max_children = 32sudo
restart_servicephp8.4-fpm
Done. Pool restarted, shop.example.com is returning 200 again.
MCP
Reads3
no approvalChanges2
ApprovedServer web-01
shop.example.comweb-01 · 203.0.113.10
200OK38 msResponse time
Logs · nginx-error
[error] connect() to unix:/run/php/php8.4-fpm-shop.example.com.sock failed (11: Resource temporarily unavailable)
[error] connect() to unix:/run/php/php8.4-fpm-shop.example.com.sock failed (11: Resource temporarily unavailable)
no new entriesMetrics
CPU34%
RAM61%
Disk48%
PHP-FPM 8.4Workers 9 / 32
pm.max_children32
Tools
The assistant doesn't just answer — it calls real panel tools and shows every step. Everything you do by hand in the panel, the assistant does with a tool call.
Ships a commit, waits for the task to finish and re-runs a failed one.
Reads the tail of a log and quotes the line with the error.
Server CPU, memory and disk, service status and whether the site answers.
Read-only SQL, dumps and writes — as a separate MySQL user with access to one database only.
Shell, artisan and WP-CLI — on the server or in the site directory.
Runs a backup now, lists earlier copies and restores the one you need.
Issues a certificate for a new domain and renews an expiring one.
Shows UFW rules, opens or closes a port.
Control
The assistant goes through the same checks as MCP tokens: access level, approvals, the dangerous command guard and secret masking.
The assistant reads on its own. Before a deploy, a restart or a database write it stops and shows a card: what will run and where. That is the default, and for sudo actions it is always the case.
sudonpm ci && npm run buildThe assistant has three levels: read only, operate and sudo. Operate is the default: deploys and restarts are in, arbitrary shell and database writes are out.
Sudo tools
Every shell command and every SQL statement is checked before it is sent. The guard is on by default; a refusal goes to the audit log and you get a notification.
Before an .env, a config or command output goes to the model, secret values are replaced with [redacted]. The same applies to external MCP clients.
Audit log
The assistant never works around the panel: every tool call is recorded, allowed or denied. One log covers the chat, the Telegram bot and MCP clients.
Telegram bot
Text the bot in plain words — and it deploys, reads logs, runs a command or SQL. The same assistant, same tools and same limits as in the panel. The reply arrives in real time.
Deploy main → prod started…
Deploy finished in 14 s. I will remove old releases with a command — it needs your approval.
rm -rf releases/old-*Done. Removed 6 old releases, freed 1.2 GB.
Model and limits
On the Pro plan the assistant runs on Deploykin AI — no keys, no setup. On Business, connect your own key from your favorite provider and pick the model: tokens are billed directly to them, with no markup from us. Conversation history is saved in the panel.
On Business, pick a provider, paste a key and test it with one button. You can switch the provider or the model at any time.
Key and model
gpt-5.1An AI action is a tool call that changes something: a deploy, a restart, a database write. Reading logs and metrics and running SELECT queries do not use up the limit.
Used38 / 200
In the panel 203.0.113.21 Connect done in 4 min 52 s
The assistant and MCP server are available on the Pro and Business plans. Open the chat in the panel — and start managing your infrastructure with words.
We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.