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 serverA running server is connected as it is: the panel scans its packages, sites and databases and takes them under management. There is a separate wizard for Ploi and a clear order of steps for shared hosting.
Three cases
The move depends on where your sites live now. In all three cases you start the actions yourself — in the panel or over MCP.
The panel scans the configured server and takes it under management. Sites stay where they are and don't stop.
The server stays the same — what changes is who manages it. The wizard rewrites the Nginx and PHP-FPM configs for Deploykin.
From shared hosting you move the site yourself — with the panel's tools. The old site keeps working until you switch the domain.
Connecting a running server
The scan doesn't change the Nginx, PHP or site configs. A deploykin user is added to the server and root login is disabled; key-only SSH login and an SSH port change are up to you.
Nginx virtual hosts with their domains and directories.
Issued certificates and their expiry dates.
Schedules of the system users.
Background processes and their commands.
Where each site is deployed from.
What is installed and what is running.
The server's system users.
MySQL databases and users. Site credentials are taken from their .env files.
Nginx, the PHP-FPM pool, .env and the logs of every site.
Migration from Ploi
The wizard connects to a Ploi-managed server, scans it and moves it to Deploykin: the same server, the same sites, a different panel.
From shared hosting
There is no automatic transfer from shared hosting: every host gives access to files and the database in its own way. But on the VPS side every step is a button in the panel.
Rent a server from any provider and add it to the panel — it installs the stack itself.
Deploy from an archive accepts eight formats. If the code is already on GitHub, connect the repository.
Upload a dump as .sql, .sql.gz, .sql.zst or .zip — the panel restores it into a new database.
Once the domain points to the new server, Let's Encrypt is issued in one click. Your own certificate can be uploaded in advance.
For WordPress, after a domain change you'll want the site address replaced in the database — it's in the site card. WordPress
In the panel 203.0.113.21 Connect done in 4 min 52 s
7 days free. Connect a server and see what the scan finds.
We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.