A project unites several servers and sites into one infrastructure: master and worker roles, a shared .env, cross-server database access and a firewall that configures itself.
The master site sets the configuration, worker nodes take the jobs, the database lives on its own server — all in one project.
Deploykin keeps the project's servers in a consistent state — without editing configs on each one by hand.
A project environment template: worker nodes pull .env from the master site, and an update rolls out to all of them.
A site on one server reaches a database on another over private access opened only to the project's peers.
A shared Redis for cache and queues — access between the project's servers is configured automatically.
UFW rules rebuild themselves: database and Redis ports are open only to the project's servers, not to the whole internet.
Link the project's sites into a deploy chain: updating the master site automatically triggers deploys of the linked sites — with the delay you set and full logs.
Project-level cron and daemon templates deploy to the matching servers automatically. A new server in the project gets the right configuration right away.
Servers, sites, roles and shared data — under one roof, with automatic synchronization.
We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.