Deployment.sh

Server panel for developers who ship more than one stack

A server panel should make a server easier to run without hiding how it works. Deployment is a hosted server panel and vps control panel built for developers: it provisions Ubuntu and Debian servers, deploys any stack from git with zero downtime and gives your team roles and an audit log. Here is how it compares with the other kinds of panels you may be weighing.

Three engineers in a small agency office, seen from behind, in front of a wall screen listing servers with green status rows

Why picking a server panel is confusing

The word panel covers very different tools. Some were made for shared hosting resellers who sell mailboxes and FTP accounts. Some were made for one framework. Some you install and run yourself. They all show a list of servers and a button that says deploy, so the differences only appear after you have moved your apps. The right question is not which panel has more buttons, but which model fits how your team builds and ships software.

Four kinds of server panels compared

Classic hosting control panelsPHP-only panelsSelf-hosted Docker panelsDeployment
Built forHosting resellers and webmastersPHP and WordPress developersDevelopers who run their own panelTeams shipping several stacks
Where the panel runsOn your serverHostedOn a server you maintainHosted
StacksPHP sites, mail, FTPPHP, some Node.jsAnything in a containerPHP, Node.js, Python, Ruby, Go, Java, .NET, static, Docker
DeploysFile upload or git pullGit with deploy scriptContainer buildsGit with atomic releases and health checks
RollbackManualVaries by toolPrevious imageOne click to any kept release
Team roles and audit logAccount levelVaries by planVaries by toolRoles per server, audit log from Team
Licence modelPer server or per accountMonthly per user or serverOpen source, optional cloud planFlat monthly plan per server count

Check each vendor's current pricing page for exact prices, they change often.

Top-down view of a developer's desk with a laptop terminal, a notebook with a hand-sketched diagram of boxes and arrows and a hardware security key

Classic hosting control panels

Classic control panels install on the server itself and manage websites, mailboxes, DNS zones and FTP users. They are the right choice if you resell hosting to customers who need email and file managers. For a development team they add a heavy layer of software to every server, run with high privileges, and treat a modern app as a folder of PHP files rather than a git repository with a build step, workers and releases.

PHP-only panels

Panels such as Laravel Forge, Ploi and RunCloud are excellent at PHP, Laravel and WordPress, with tidy defaults for PHP-FPM, queues and scheduling. Many teams outgrow them only when a Next.js frontend, a Python worker or a Go service joins the stack and has to be deployed by hand next to the PHP app. If everything you run is PHP, they are a good option; we compare them in detail on the laravel forge alternative and RunCloud alternative pages.

Self-hosted Docker panels

Open-source panels such as Coolify run on a server you manage and deploy apps as containers. They are flexible and the software is free to run, in exchange for maintaining the panel itself: updates, backups of the panel database, its own uptime and security. Our coolify alternative page lays out that trade-off honestly.

Deployment as your VPS control panel

Deployment is hosted, so there is nothing to install or patch on your side besides the servers you deploy to. It runs apps natively on the server with the runtime they need, or in Docker when your repository has a Dockerfile or compose file.

See every capability on software deployment automation.

  • Provisioning with firewall, SSH hardening, unattended updates, swap, nginx or Caddy and runtimes per site
  • Push to deploy, editable deploy script, atomic releases, health checks and one-click rollback
  • MySQL, MariaDB, PostgreSQL and Redis with users and grants
  • Let's Encrypt SSL, wildcard certificates through DNS API, redirects
  • Workers, daemons and cron with logs, monitoring and alerts
  • Backups to your own S3-compatible storage
  • Roles, per-server access, audit log and SSO on Enterprise

When Deployment is the right server panel

When it is not the right fit: if you sell hosting with email accounts to end customers, a classic hosting panel serves that model better.

  • Your team runs more than one language or framework in production
  • Several people deploy and you need to know who changed what
  • You want servers in your own cloud account and no compute markup, as explained on cloud server management
  • You do not want to host, patch and back up the panel itself

Which plan fits your server panel needs

Starter costs 49 USD a month, or 24 USD a month billed yearly, for 3 servers and 15 sites. Team costs 199 USD a month (99 USD yearly) with 15 servers, 100 sites, 10 members, roles and audit log. Agency costs 499 USD a month (249 USD yearly) with 60 servers. Enterprise costs 1 499 USD a month (749 USD yearly) with 250 servers and SSO. Details on PaaS pricing.

Does Deployment install anything heavy on my server?

No panel software runs on your server. Deployment connects over SSH with its own key and installs only the web server, runtimes, databases and process managers your sites use.

Can I manage mailboxes or FTP accounts?

No. Deployment focuses on applications. Use a dedicated email provider for mail, and git plus SSH or SFTP for files.

Can I move from a PHP-only panel without downtime?

Yes. Connect a new server, recreate the sites, copy databases, deploy and test on a temporary domain, then switch DNS when ready.

Can I try Deployment before I pay?

Yes, with the free one-time demo on the home page. Plans start at 49 USD a month, or 24 USD a month billed yearly.

Try a server panel built for every stack

Connect a server and deploy your PHP, JavaScript, Python or Go app from the same screen.

See the plan for your own repository first. Try the demo.