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

Write the configuration

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

Paste it in the configurator

Step eight, next to the hostname and keys.

Deploy

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

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.

Ask the help desk Service status

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.

Configure your server Talk to sales

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