Laravel
Ready-made configuration: public root, .env, queues, scheduler.
- composer install
- npm run build
- key:generate
- storage:link
- schedule:run
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 serverLaravel, WordPress, PHP, Node.js, Go — create a site in seconds. Domains, SSL, PHP versions, health checks and isolation out of the box.
Site types
Three types are created in the wizard; WordPress and phpMyAdmin are installed from templates. Deploykin runs the whole chain itself: user, code, PHP-FPM pool, Nginx config, database.
Ready-made configuration: public root, .env, queues, scheduler.
Any PHP application. Nginx + PHP-FPM with the PHP version you need.
Go, Node.js or any process on its own port: Nginx proxies requests to it. No PHP and no PHP-FPM pool needed.
Automatic WP install, wp-config.php setup, database.
Manage databases from the browser. Auto-login, Basic Auth.
The same setup chain as for a new site: code, PHP-FPM pool, Nginx config. On the same server or another one.
Site settings
What you would normally edit by hand in Nginx and PHP-FPM configs is changed in the site settings. The panel regenerates the config, tests it and applies it.
Set a primary domain and add as many aliases as you like. SSL is issued from the panel in one click — for the primary domain and all aliases, then renews automatically.
Every site has its own PHP-FPM pool and its own PHP version — from 7.3 to 8.5. A legacy project stays on 7.4, a new one runs on 8.5, and they don't get in each other's way.
Version for blog.example.com
Security headers, a password on any path and a maintenance page are switched on in the site settings. Deploykin regenerates the Nginx config and applies it.
Basic authentication
Every 5 minutes Deploykin requests each site and records the response time. The site list shows at a glance which sites are online, how many requests came in today and what share of them are errors.
User isolation
Every site runs under its own system user. One site's files are inaccessible to another — even if one of them is compromised.
~$ whoami
blog
~$ cat ../shop/.env
cat: ../shop/.env: Permission denied
.env and cloning
For Laravel sites, .env is edited right in the panel: the file is synced from the server and only the changed keys are saved. Any site can be cloned to the same server or another one — a Laravel site together with its database.
In the panel 203.0.113.21 Connect done in 4 min 52 s
Pick a template, set the domain — Deploykin configures Nginx, PHP and the system user automatically. SSL is issued in one click.
We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.