/etc/nginx
- nginx.conf
- sites-available/*
Nginxeditor and form
worker connections, client_max_body_size, gzip, and server blocks for each site.
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 serverSupported configs
Deploykin finds the configs of the packages it installed, site files and the server's system files on its own. Each opens in the editor, and Nginx, PHP, MySQL and Redis also have forms for the core parameters.
/etc/nginx
worker connections, client_max_body_size, gzip, and server blocks for each site.
/etc/php/8.4
memory_limit, upload_max_filesize, max_execution_time, OPcache, and other settings.
/etc/mysql/mysql.conf.d
max_connections, innodb_buffer_pool_size, slow query log, and other parameters.
/etc/redis
Memory limit, key eviction policy, password and AOF.
/etc/supervisor
Daemon configuration: command, directory, number of processes, auto-restart.
/home/shop/shop.example.com
Environment variables of Laravel sites. Only the keys you changed are saved — the rest stay as they are on the server.
/etc
SSH, DNS, network, limits and the system cron — files Deploykin finds while setting up the server.
A backup (.bak) is created before every save, and a syntax check catches errors before applying..bak.20261001140211
Panel
The Nginx config and the PHP-FPM pool are in the site menu, shared settings are on the server. The tabs in the window title switch the tour's chapters. This is a copy of the panel with demo data.
01 / 07Every file Deploykin tracks is in one list: with a category filter and a search by path.
Editor
Syntax highlighting for nginx, php, ini, json, yaml, xml, html, css, sql, sh. The editor checks the file as you type, keeps a copy before writing and never silently overwrites someone else's edits.
From the editor, the assistant opens with a question about this file already filled in. It reads the config and looks at the server's hardware and metrics. It may change the config only at the sudo access level — and every time with your approval.
Assistant's answer
For 2 vCPU and 4 GB of RAM: raise worker_connections from 768 to 2048 and enable Brotli. I will change it through the Nginx settings — with nginx -t and a rollback on failure.
Nginx configs, INI files, .env and JSON are checked right in the editor as you type: with an error the Save button is disabled. The Test button runs the file through nginx -t or php-fpm -t on the server — before anything is written.
http {
sendfile on;
keepalive_timeout 65; client_max_body_size 64M;
server_tokens off;
include sites-enabled/*;
}
File check
The editor writes the whole file. If the file changed on the server while you were editing — over SSH, through MCP or from another tab — the save stops and shows exactly what changed.
pm = dynamic - pm.max_children = 16 + pm.max_children = 32 pm.start_servers = 4 pm.min_spare_servers = 2
Saving
Before writing, Deploykin copies the current file next to it — with the date and time in the name. The write itself is atomic, and the file's owner and permissions are kept.
Settings as forms
Nginx, PHP, MySQL and Redis have forms for the core parameters. You save — the panel copies the file, changes only the directives involved, checks the config and reloads the service. If anything goes wrong, the file goes back to the previous version.
The global nginx.conf parameters live in the server settings. Request size, proxy timeouts, security headers and static asset caching are set per site.
brotli on;
Core PHP and FPM pool parameters — without editing files by hand. Validation before applying.
32
pm.max_children = 32
The form changes directives in mysqld.cnf and restarts MySQL itself. If the service does not come up with the new config, the file goes back to the previous version.
2G
innodb_buffer_pool_size = 2G
Server and site
The server's Configurations page lists every file Deploykin tracks: grouped by directory, with a category filter and search by path. A site's list has only its own files — the Nginx config, the PHP-FPM pool and .env.
In the panel 203.0.113.21 Connect done in 4 min 52 s
Edit PHP, Nginx, MySQL and other configurations right from the browser. Validation and a backup before saving are included.
We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.