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 serverDeploykin analyzes your server's resources and automatically selects optimal MySQL, PHP-FPM and Nginx settings. Apply the recommendations in a single click.
MySQL
innodb_buffer_pool_size
max_connections
PHP-FPM
pm.max_children
memory_limit
OPcache
Nginx
worker_connections
by defaultDeploykin recommendation
What gets tuned
No need to search for «optimal MySQL settings for 8 GB RAM». Deploykin figures it all out itself based on the server's actual resources. A block is shown only for what is installed: no MySQL — nothing to tune.
Calculating recommendations4 vCPU · 8 GB · all-in-one server
The InnoDB buffer pool gets a share of memory based on the server's role, and the connection limit grows with the amount of RAM. The slow query log is turned on with a 2-second threshold.
innodb_buffer_pool_size40% of memoryinnodb_log_file_sizea quarter of the buffer poolmax_connections100 + 50 per GBmax_allowed_packet256M from 4 GB of memory, 64M otherwiseslow_query_logslow query loglong_query_timeslow query threshold, secondsThe number of workers is capped by both memory and cores — the lower value wins. The script memory limit and the OPcache size follow the amount of RAM.
pm.max_children5 per core, up to 30% of memorypm.start_serversa quarter of max_childrenpm.min_spare_servers15% of max_childrenpm.max_spare_servers35% of max_childrenmemory_limit192–512M by amount of memoryupload_max_filesizepost_max_size gets the samemax_execution_timeseconds per requestmax_input_varsvariables per requestOPcache6% of memory, from 128 to 512MOne worker per core, connections sized by memory. The upload limit matches the PHP limit, gzip is on and the Nginx version is hidden.
worker_processesone worker per coreworker_connections1024–4096 by amount of memorykeepalive_timeoutsecondsclient_max_body_sizesame as the PHP upload limitgzipcompression of text responsesserver_tokensNginx version hiddenPanel
Current values sit next to the recommended ones — every difference is visible. This is a copy of the panel with demo data — click around or watch the tour.
01 / 06Auto-tune lives in the server menu, under Settings.
Applying
The “Apply recommendations” button runs the same action as saving settings by hand: config backup, writing the values, a check and a service reload.
rolled back — the service never stopped
nginx -tNot ready to change the whole block? Every parameter that differs from the recommendation has its own button: only that value is applied, the rest stay as they were.
On the MySQL and PHP settings pages, key fields show the value calculated for your server — with the same formulas as auto-tuning.
Current → Recommended
Auto-tuning works from the server's latest metrics. Move to a plan with more memory or add cores — new recommendations appear next to the current values.
Profiles
The same VPS is tuned differently depending on whether it runs everything, only the database or only queues. Deploykin derives the tuning profile from the server type.
InnoDBPHP-FPMsystem and everything else
Change the server type — you get a notification, and the panel leaves the values alone. Server management
FAQ
A short take on what auto-tuning does itself and what it leaves to you.
No. It calculates recommendations and shows them next to the current values. Configs change only when you click “Apply recommendations” or apply a single value. Even when the server type changes, the panel only sends a notification.
PHP-FPM and Nginx re-read the config with a reload, without stopping the service. MySQL is restarted: some of its parameters are read only at startup, so apply database recommendations during a quiet period.
If applying fails, Deploykin restores the config from the backup it made before the change. After a successful apply the backup is removed — previous values are brought back manually in the MySQL, PHP or Nginx settings.
The panel regularly reconciles settings with the files on the server, so the “Current” column shows what is actually written in the config, not what was once saved in the panel.
The formulas are deliberately conservative: they leave memory headroom for the OS and neighboring services. They are a solid starting point for a typical server, not a replacement for hand tuning — any value can be adjusted in the service settings.
In the panel 203.0.113.21 Connect done in 4 min 52 s
Connect a server — Deploykin will detect the resources and suggest optimal MySQL, PHP-FPM and Nginx settings.
We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.