Deployment.sh

VPS management for every stack, from one panel

A VPS gives you a fast machine for a fraction of PaaS prices, and then hands you every chore that a platform used to hide. Deployment takes over those chores on any Ubuntu or Debian VPS from any provider: hardening, runtimes, web server, SSL, databases, deploys, workers, monitoring and backups. You keep root access and the server stays yours.

Sysadmin at a kitchen table at dawn running a server setup in a terminal on a laptop beside a router and notebook

What unmanaged VPS hosting really costs

The monthly price of a VPS is small. The hours are not. The first server takes a day to set up properly, the second one is configured slightly differently, and a year later nobody remembers which box runs which Node version or why port 6379 is open to the world. Security updates wait for a quiet week that never comes. Deploys are a git pull over SSH, so every release has a few seconds where the app is half old and half new.

Good VPS management is not about clicking buttons instead of typing commands. It is about every server being configured the same way, every change being visible, and every deploy being reversible.

How Deployment manages your VPS

You run one command on the server as root. It installs a dedicated SSH key for Deployment and reports the operating system, CPU, memory and disk. From that moment the server is managed from the panel, and you can still SSH in whenever you like.

  • Works on Hetzner, DigitalOcean, Vultr, Linode, OVH, UpCloud, Scaleway, AWS Lightsail and EC2, Google Compute Engine and any other provider that gives you SSH
  • Ubuntu 22.04, Ubuntu 24.04 and Debian 12, on x86 or ARM
  • Prefer to create the VPS from the panel too? Use cloud server management with an API token
bash 
curl -fsSL https://deployment.sh/connect/<token> | sudo bash
Close-up inside a server rack: a patch cable plugged into a switch port next to a row of small green link lights, out-of-focus cabinet behind

VPS security set up on day one

Provisioning applies a baseline that most hand-built servers never reach. The firewall allows SSH, HTTP and HTTPS and nothing else. Password logins and root password logins are disabled. Unattended upgrades install security patches every day, and swap protects small instances from out-of-memory kills during builds.

  • Firewall rules you can extend from the panel, per port and source IP
  • Key-only SSH with one Deployment key per server
  • Automatic security updates with a log of what changed

Run many apps on one VPS without conflicts

A 4 GB VPS can comfortably run several small apps. The trouble starts when they need different runtime versions. Deployment installs runtimes per site, so a PHP 8.2 legacy app, a PHP 8.4 app and a Node.js 22 frontend live side by side, each with its own nginx or Caddy site, its own user and its own release folders.

  • PHP 8.x, Node.js LTS, Python 3.x, Ruby, Go, Java 21, .NET 8 and Docker
  • One system user per site, so one app cannot read another app's files
  • MySQL, MariaDB, PostgreSQL and Redis on the same VPS or on a separate one

Deploys that do not take the VPS offline

Each deploy builds into a new release folder while the current release keeps serving traffic. A health check confirms the new release answers, then a symlink switches over and workers restart. If the health check fails, the switch never happens. If you spot a problem later, rollback is one click. This is the same zero downtime deployment flow for every stack, triggered when you deploy from git.

Monitoring, logs and backups for every VPS

The panel shows CPU, RAM, disk and load for each server and streams nginx and application logs. HTTP uptime checks watch your domains and send alerts to email, Slack, Discord or a webhook when something stops answering. Scheduled backups of databases and files go to your own S3-compatible bucket, with retention and one-click restore.

Who uses Deployment for VPS management

  • Freelancers who host client projects on a few VPS and want each one set up identically
  • Startups that moved off a PaaS to cut the bill and need deploys to stay as easy
  • Agencies with dozens of client apps spread over several providers
  • In-house teams that need roles and an audit log for production access

Which stacks run on a managed VPS

Laravel and plain PHP, WordPress, Node.js with Express or NestJS, Next.js and Nuxt, Django, FastAPI and Flask, Ruby on Rails, Go services, Spring Boot, ASP.NET Core, static sites and Docker Compose projects. The full feature list is on software deployment automation.

Which plan fits your VPS fleet

Starter at 49 USD a month (24 USD a month billed yearly) manages 3 servers and 15 sites for one person. Team at 199 USD a month (99 USD yearly) covers 15 servers, 100 sites and 10 team members. Agency at 499 USD a month (249 USD yearly) covers 60 servers. Enterprise at 1 499 USD a month (749 USD yearly) covers 250 servers with SSO. Compare everything on PaaS pricing.

See pricing

Do I lose root access to my VPS?

No. Deployment adds its own key and leaves your keys alone. You can SSH in, install extra packages and inspect anything at any time.

Can Deployment manage a VPS that already runs apps?

Yes, but provisioning is designed for clean servers. On a server with existing apps, connect it, add sites for new deploys and move old apps over one at a time.

What happens if Deployment is unavailable?

Your VPS keeps serving traffic, workers keep running and cron keeps firing. Only the panel, new deploys and alerts pause until the service is back.

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.

Put your VPS under real management

Connect your first VPS and have it hardened and ready to deploy in minutes.

Curious what your repository needs? Try the demo first.