Skip to content

Deploy Hatamoto on Vultr

By the end you have Hatamoto running on a Vultr Cloud Compute server, with PostgreSQL and HTTPS in place and a link in the console that creates your owner account. You paste one script into the deploy form and Vultr runs it on first boot. The install runs by itself after you press Deploy.

The server costs $5 a month. Vultr's pre-ticked Automatic Backups option adds 20%, so decide on it before you deploy.

What it costs

The 1 GB Cloud Compute plan is the smallest that meets Hatamoto's memory minimum. Vultr bills hourly up to the monthly price, and a stopped instance costs the same as a running one.

ItemPrice
Cloud Compute: 1 vCPU, 1 GB RAM, 25 GB SSD, 1 TB transfer$5 a month ($7.50 in Sao Paulo)
Cloud Compute: 1 vCPU, 2 GB RAM, 55 GB SSD, 2 TB transfer$10 a month
Automatic Backups20% of the plan price
Snapshots$0.05 per GB each month
Reserved IP (a fixed address)$3 a month

Prices as of 13 November 2026, from Vultr's public plans API, which backs its pricing page. They exclude tax. They change, so check the provider before you order.

Before you start

  • A Vultr account.
  • An SSH public key. Add it to your account first, because adding one in the console after deployment wipes the instance.
  • A domain name you can edit DNS for, if you want one. Without it, Hatamoto uses a free sslip.io name such as 203-0-113-7.sslip.io.
  • An email address for certificate expiry notices.

Step 1: Add your SSH key

Sign in to the Vultr console. Under Account, open SSH Keys (it sits in the OTHER group of the menu) and choose Add SSH Key. Paste your public key and save, so you can pick it in the deploy form.

Step 2: Start a new instance

Go to Compute, click Instances, then Create Instance +.

Step 3: Pick the type, plan and location

Choose Shared CPU as the instance type. In the Plan Selection sidebar pick the Cloud Compute category and the plan with 1 vCPU, 1 GB of RAM and 25 GB of SSD at $5 a month. Choose a location near your visitors, then click Configure.

Step 4: Choose the operating system

In Image Selection and Configuration, keep Operating System and choose Ubuntu 24.04 LTS x64. Vultr's default image can be a short-term release such as Ubuntu 26.10, so check the name before you move on.

Step 5: Paste the script into Cloud-Init User Data

Under Server Settings, tick your key in SSH Keys and leave Startup Script empty, because that field needs a script saved separately under Orchestration. Scroll to Additional Features and switch on Cloud-Init User Data. Paste this script into the User Data field:

#!/bin/sh
sh -c 'curl -fsSL -o /tmp/hatamoto-install.sh https://hatamoto.dev/install.sh && chmod +x /tmp/hatamoto-install.sh && env HATAMOTO_DOMAIN=cms.example.com HATAMOTO_ADMIN_EMAIL=you@example.com /tmp/hatamoto-install.sh'

Vultr says a user-data script must start with a valid shebang line, as this one does. Replace cms.example.com with your domain and you@example.com with your email address. For the free sslip.io name, delete the env part so the command ends with /tmp/hatamoto-install.sh. The script runs as root. Do not put a secret setup code in this field, because it stays readable in your Vultr account.

Leave Instance Connectivity on Instance(s) with Public IP with Public IPv4 on, and leave Limited User Login off so you log in as root.

Step 6: Decide about Automatic Backups and deploy

Still under Additional Features, look at Automatic Backups. The console switches it on by default. Keep it for whole-server copies or turn it off, and enable it later from the instance's Backups tab if you wish. Enter Server 1 Hostname and Server 1 Label, check the Summary panel for the monthly price and click Deploy. The instance shows as installing, then running.

Step 7: Point your domain at the instance

Open the instance's Overview tab and copy its IPv4 address. Add an A record for your domain at your DNS host, pointing at that address. Not ready yet? Hatamoto serves the sslip.io name meanwhile and switches within minutes of the record working.

Step 8: Add a firewall group (optional)

Hatamoto's installer already turns on the server's own firewall for 22, 80 and 443, and a Vultr firewall group filters only once it holds a rule, so you can skip this. To use one, go to Network, then Firewall Groups, then Create Firewall Group, enter a Name and choose Add Firewall Group. Under Inbound IPv4 Rules, use Add Rule for each of ports 22, 80 and 443, then Add Firewall Rule. To attach it, open the instance, then Settings, then Firewall, choose the group and click Update Firewall Group.

Step 9: Watch the install in the console

Open the instance and use the View Console icon at the upper right, after allowing pop-ups. The console expects a US keyboard, shows nothing as you type a password and has a Clipboard button for pasting. The Overview tab shows the root login. Check progress with:

cloud-init status
cat /var/log/cloud-init-output.log

When the install ends, the console prints the "Hatamoto is ready." block with your setup link.

Step 10: Open the link and take a snapshot

Your browser opens the setup page. The code is already entered, and anything after the # stays on your side. Make the owner account, then read First run.

In Vultr, open the instance's Snapshots tab, type a Label and choose Take Snapshot. It can take up to 30 minutes, and the result appears under Orchestration, then Snapshots.

Check it worked

In the console or over SSH, run:

curl -i http://127.0.0.1:8090/health

A healthy server answers HTTP/1.1 200 OK on the first line. Open your domain next: a padlock and the starter home page confirm it.

If something goes wrong

  • If the server came up on a short-term Ubuntu release, redeploy with Ubuntu 24.04 LTS for long support. Hatamoto installs on the other one with a warning.
  • If the server was wiped, you changed an SSH key or the startup script after deploying, which Vultr says wipes the instance. Set both before you press Deploy and redeploy.
  • If the site times out after you attach a firewall group, add rules for ports 22, 80 and 443 under Inbound IPv4 Rules. IPv6 traffic has its own rule list.
  • If the first invoice is 20% higher than the plan price, Automatic Backups were on. Turn them off on the instance's Backups tab.
  • If the domain shows a certificate warning, check that the A record points at the instance's address. Until it does, the site answers on the sslip.io name.

Use the command line instead

vultr-cli has a --userdata-file flag and encodes the file itself. Save the script as hatamoto-userdata.sh, find your key's id with vultr-cli ssh-key list and run:

vultr-cli instance create --region ewr --plan vc2-1c-1gb --os 2284 --label hatamoto --host hatamoto --ssh-keys SSH_KEY_ID --userdata-file hatamoto-userdata.sh

ewr is New Jersey, vc2-1c-1gb is the $5 plan and 2284 is Ubuntu 24.04 LTS x64. The flags come from the vultr-cli source and README, and the command has not been run for this page.

FAQ

What does Hatamoto cost to run on Vultr?

The 1 GB Cloud Compute plan is $5 a month. Keeping Automatic Backups on raises that by 20%. Hatamoto is free to install.

Which field takes the script, Startup Script or Cloud-Init User Data?

Use Cloud-Init User Data, under Additional Features. Vultr's docs say Linux systems use cloud-init user data, while the Startup Script field needs a saved script that you create separately under Orchestration.

Does Vultr offer an arm64 server?

Not in Vultr's public plan and image lists, which are all x64. This page is written for amd64.

Is the public IP address behind NAT?

No. Vultr assigns a public IPv4 address to the instance at deployment. The NAT gateway is an option you would have to choose under Instance Connectivity.

Can I run it on Debian?

Yes. Vultr offers Debian 12 and 13 and Hatamoto supports both. This guide uses Ubuntu 24.04 LTS.

How do I keep the address when I rebuild?

Add a Reserved IP, which costs $3 a month and belongs to one instance in the same location. Pick it under IP Address in Server Settings when you deploy.

Can I change the domain later?

Point the new name's A record at the instance and run sudo ./install.sh set-domain cms.example.com --email you@example.com from a fresh copy of the installer. The old name redirects to the new one.

Hatamoto installs the same way on DigitalOcean, Amazon Lightsail, Amazon EC2, Hetzner Cloud and Linode. The full option list is in Install on a VPS.