Cloud server management across nine providers, in your own accounts
Deployment creates and manages servers inside your own cloud accounts. Paste an API token from Hetzner, DigitalOcean, AWS, Vultr, Linode, Google Cloud, OVH, UpCloud or Scaleway, pick a region and size, and the server is created, provisioned and ready for its first deploy. Your provider bills you directly at its own price. Deployment never resells compute.
Multi-cloud without a multi-cloud headache
Teams rarely live in one cloud. The product runs on AWS because a customer asked for it, the marketing site sits on Hetzner because it is cheap, and an old client project still lives on DigitalOcean. Each console has its own way to create a machine, attach a firewall and add SSH keys, and each server ends up configured slightly differently. A managed cloud server from a reseller fixes the consistency but adds a markup on every instance and takes the account out of your hands.
One panel for every cloud account you own
Connect each provider once with a token you create in its console. Deployment uses the token to list regions and sizes, create servers, attach your SSH key and, where the provider supports it, set up a cloud firewall. Every server then goes through the same provisioning, so a Hetzner box in Falkenstein and an EC2 instance in Virginia end up with the same hardening, web server and runtimes.
- Create, resize where the provider allows it, and delete servers from the panel
- Servers, disks, snapshots and invoices stay in your provider account
- Mix created servers with existing ones connected over SSH through vps management
Supported cloud providers
| Provider | Connection | What Deployment does with it |
|---|---|---|
| Hetzner Cloud | API token | Create servers in all locations, attach firewalls and SSH keys |
| DigitalOcean | Personal access token | Create Droplets, attach cloud firewalls and SSH keys |
| AWS | IAM access key with a scoped policy | Launch EC2 instances, security groups and key pairs in your chosen region |
| Vultr | API key | Create cloud compute and high frequency instances |
| Linode (Akamai) | Personal access token | Create Linodes and cloud firewalls |
| Google Cloud | Service account key | Create Compute Engine VMs and firewall rules in your project |
| OVH Public Cloud | Application key and token | Create instances in your project |
| UpCloud | API credentials | Create cloud servers in all zones |
| Scaleway | API key | Create instances in Paris, Amsterdam and Warsaw zones |
Every integration is listed with setup steps on cloud server management integrations.
Tokens with the least privilege you choose
You decide what each token may do. On AWS you attach a policy that allows only the EC2 actions Deployment needs. On Google Cloud you use a service account limited to one project. On providers with read and write tokens only, you can revoke the token at any time, and servers already created keep running untouched. Tokens are stored encrypted and never shown again after saving. Read the full access model on the server security platform page.
From empty instance to production ready
Once the instance boots, provisioning sets up the firewall, SSH hardening, unattended security updates and swap, then installs nginx or Caddy and the runtimes your sites need: PHP 8.x, Node.js LTS, Python 3.x, Ruby, Go, Java 21, .NET 8 and Docker. Databases (MySQL, MariaDB, PostgreSQL) and Redis are added from the panel with users and grants.
Pay your cloud at cost, not at markup
A managed PaaS or a reselling host adds its margin on top of the same machines. With Deployment, a 4 vCPU and 8 GB server costs what your provider charges for it, and the panel is a flat plan that does not change with traffic or the number of instances inside your server limit. If you leave, the servers and everything on them stay in your account. Compare this model with a self hosted paas.
Same deploys on every cloud
Sites on any cloud server deploy from git with atomic releases, health checks and one-click rollback. Workers restart on deploy, cron runs with logs, uptime checks and alerts cover every domain, and backups go to S3-compatible storage of your choice, which can sit in a different cloud from the server for extra safety.
Stacks you can run on managed cloud servers
Laravel and PHP, Node.js and Next.js, Django, FastAPI and Flask, Rails, Go, Spring Boot, ASP.NET Core, static sites and Docker Compose, on x86 or ARM instances where the provider offers them.
Which plan fits your cloud footprint
Starter at 49 USD a month (24 USD billed yearly) for 3 servers. Team at 199 USD a month (99 USD yearly) for 15 servers and 10 people. Agency at 499 USD a month (249 USD yearly) for 60 servers. Enterprise at 1 499 USD a month (749 USD yearly) for 250 servers, SSO and an SLA of 99.9 percent. See PaaS pricing for the full table.
Does Deployment charge for the servers it creates?
No. Your cloud provider bills you directly. Deployment charges only the plan you choose.
Can I connect several accounts of the same provider?
Yes. Agencies often connect one account per client, so each client pays their own cloud bill.
What happens to servers if I remove a token?
Nothing. Servers keep running. You only lose the ability to create new servers in that account from the panel.
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.
Manage every cloud server from one place
Connect your first cloud account and create a production ready server in minutes.
Want to see a deploy plan for your code? Try the demo.
$ git push origin main
✓ build release 20261019-142210
✓ health check 200
✓ switch current 0.4 s
$