Cobanto
Deploy a server
Pricing

Products

More

Locations Service status
Cloud VPS Shared vCPU on SSD Performance VPSNVMe AMD EPYC cores on NVMe, up to 900 GB Cloud VDS Dedicated cores with full separation Storage VPS Up to 1.4 TB for backups and media Windows VPS 2022 or 2019, licence included Custom configure Plan, region, image and add-ons before you pay

Built into every server

Free network firewall Snapshots and backups Private networking Additional IPv4 and rDNS SSH keys and access Locations and latency
Web hosting Sites, mail and SSL on our own machines WordPress hosting Tuned stack, staging and one-click install HosTpanelOurs The panel we build and run, free on every server Free migration We move your sites from any provider

For agencies

How reselling works Client accounts and logins Provision in bulk by API Priority support queue
Operating systems Ubuntu, Debian, Rocky, AlmaLinux, Windows Control panels HosTpanel free, Webmin, Proxmox VE, or cPanel and Plesk licensed monthly Developer stacks Docker, GitLab, LAMP, Dokploy, WireGuard Business apps Nextcloud and n8n AI and blockchain OpenClaw, Hermes, Ollama, Bitcoin and Ethereum nodes Custom images Upload your own qcow2 or ISO Cloud-init Bring your own first-boot configuration

Most deployed

Docker GitLab n8n Nextcloud See all images and apps
Help desk Ask our engineers. Average first reply in 15 minutes. Service statusLive Every component, in real time Tutorials and guides Products, billing, migrations and more Free workshops Live sessions on Docker, WordPress and DevOps

Servers and hosting

Server tutorials DevOps workshops Video guides

Developers

Past incidents

Account

Billing and invoices Abuse reports
Images

Cloud-init

Your configuration runs alongside ours, so the branding, hostname and reverse DNS are applied and your own packages, users and files land in the same boot.

Describe the first boot and stop configuring servers by hand. Paste your configuration in the configurator or send it with the API, and the machine comes up finished.

A configuration that finishes the job
#cloud-config
package_update: true
packages:
  - nginx
  - postgresql-client

users:
  - name: deploy
    groups: sudo
    shell: /bin/bash
    ssh_authorized_keys:
      - ssh-ed25519 AAAA... ada@studio

write_files:
  - path: /etc/nginx/sites-available/app
    content: |
      server { listen 80; root /srv/app/public; }

runcmd:
  - systemctl enable --now nginx
  - ufw allow 80,443/tcp
How it runs

From your file to a booted machine

01

Write the configuration

Plain cloud-config YAML, or a shell script if you prefer.

02

Paste it in the configurator

Step eight, next to the hostname and keys.

03

Deploy

The server boots, applies it, and is ready to use.

04

Reuse it

Send the same block with every API call and your fleet stays identical.

Questions

Straight answers before you deploy

Still deciding?
Engineers answer, not scripts.

No. Both run in the same boot; yours is applied as its own part, so nothing is overwritten.

The server still boots. Open the console, read the cloud-init log and fix it.

Ready when you are.

Configure a server now. Your account is created right before payment, with the configuration saved.

No setup fee
On any contract term
No card on file
Prepaid balance, topped up when you choose
Same price at renewal
The one you signed up for
Cancel from the panel
One click, no phone call