Deploy Hatamoto on Linode (Akamai Cloud)
By the end you have Hatamoto running on a Linode in Akamai Cloud, with PostgreSQL and HTTPS in place and a link in the console that creates your owner account. Cloud Manager has an Add User Data box on the create form, so you paste one file and the Linode installs your CMS on first boot. The install starts as soon as the Linode boots.
The Nanode 1 GB costs $5.00 a month in most regions, and Cloud Firewalls are free.
What it costs
The 1 GB Nanode is the smallest Shared CPU plan that fits Hatamoto's memory minimum. Billing is hourly up to the monthly price, and charges continue while a Linode is powered off.
| Item | Price |
|---|---|
| Nanode 1 GB: 1 vCPU, 1 GB RAM, 25 GB storage, 1 TB transfer | $5.00 a month ($6.00 in Jakarta, $7.00 in Sao Paulo) |
| Linode 2 GB: 1 vCPU, 2 GB RAM, 50 GB storage, 2 TB transfer | $12.00 a month |
| Backups service on a Nanode | $2.00 a month |
| Cloud Firewall | Free |
| Reserved IP (a fixed address) | $0.0068 an hour, even when unassigned |
Prices as of 13 November 2026, from Linode's public plans API, which backs its pricing page. They change, so check the provider before you order.
Before you start
- A Linode account, and Cloud Manager at cloud.linode.com. The docs call the platform Akamai Cloud and the servers Linodes.
- An SSH public key, a root password, or both. Cloud Manager needs at least one, and the browser console needs the password.
- A domain with DNS you can change, for a name of your own. Skip it and the site runs on a free sslip.io name, which is fine for a trial.
- An email address for the certificate authority's expiry notices.
Step 1: Make a Cloud Firewall
Log in to Cloud Manager. Choose Firewalls in the navigation menu, then Create Firewall. Pick Custom Firewall, enter a Label, leave Default Inbound Policy on Drop and Default Outbound Policy on Accept, then choose Create Firewall. On the firewall's Rules page, use Add an Inbound Rule for TCP ports 22, 80 and 443 with the action Accept. Hatamoto's installer also turns on the server's own firewall, so this is a second layer.
Step 2: Open the Create form and pick a region
Click the Create dropdown on the top bar and choose Linode. Under Region, pick the datacentre nearest your visitors, for example Sydney or Melbourne. Choose the region before the plan, because the price can vary by region.
Step 3: Choose the distribution and plan
Under Distributions, pick Ubuntu 24.04 LTS. Images that support cloud-init show a cloud icon with a gear. In the plan list, choose the Shared CPU group and the Nanode 1 GB, or Linode 2 GB for a busier site.
Step 4: Set the label and security
Under Details, type a Label, which becomes the hostname. Under Security, set at least one form of authentication. Fill in Root Password and add your key with Add an SSH Key. The password is what lets you use the browser console later.
Step 5: Add User Data
Expand Add User Data and paste this file into the User Data field:
#cloud-config
runcmd:
- 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'Replace cms.example.com with your domain and you@example.com with your email address, which goes to the certificate authority. To stay on the free sslip.io name, delete the env part. The file runs as root, so leave sudo out and keep a secret setup code out too. In Cloud Manager you paste plain text. You cannot edit user data on an existing Linode, so check it now.
Step 6: Choose networking and the firewall
Under Networking, choose the default interface type Public Internet. The public IPv4 address is Auto-assigned by default at no extra cost. In the firewall dropdown, choose the firewall from step 1. The dropdown also offers "No firewall", which Linode marks as not recommended.
Step 7: Decide about Backups, then create the Linode
Under Additional options, you can tick Add the Backups service, which costs $2.00 a month on a Nanode. Leave Encrypt Disk off if you want Backups, because the service needs unencrypted ext3 or ext4 disks. Check the Linode Summary and click Create Linode. Provisioning can take around 3 minutes.
Step 8: Point your domain at the Linode
Copy the IPv4 address from the Linode's page. At your DNS host, create an A record for the domain with that address. Until the record works, the site answers on the sslip.io name and Hatamoto switches to your domain by itself.
Step 9: Watch the install
The login user is root. The SSH Access field under Access on the Linode's page has a ready ssh root@ command. For the browser console, open Linodes, pick the Linode and click Launch LISH Console at the top right, then log in as root with the root password. Press CTRL+A then D to leave. Wait a few minutes, then run:
cloud-init status --long
cat /var/log/cloud-init-output.logThe login message then shows a "Hatamoto is ready." block with the setup link.
Step 10: Open the setup link
Open the link in a browser. The setup code is already filled in, and the part after # never leaves your browser. Create the owner account, then read First run. If you skipped the Backups service, you can add it from the Linode's Backups tab with Enable Backups.
Check it worked
In the Lish console or over SSH, run:
curl -i http://127.0.0.1:8090/healthThe reply begins HTTP/1.1 200 OK. Browse to your domain next. The padlock and starter home page mean it is done.
If something goes wrong
- If the Linode booted and did not install, pick a Distributions image with the cloud icon, because user data works only on images with cloud-init. Check
cat /var/log/cloud-init.logfor what ran. - If the Lish console asks for a root password you never set, reset it from the Linode's page. Weblish needs one.
- If the site is unreachable after you attach the firewall, add Accept rules for TCP 80 and 443. A new Cloud Firewall drops inbound traffic that no rule accepts.
- If Backups will not enable, the Linode was created with Encrypt Disk on. Create it again with that option off.
- If the bill shows a Linode you powered off, delete it. Charges accrue even while it is off.
Use the command line instead
Install the tool with pip3 install linode-cli --upgrade and sign in with linode-cli configure. Save the file as hatamoto-user-data.yaml. On the command line the user data must be Base64 encoded without line wraps, which base64 --wrap=0 does on Linux:
linode-cli linodes create --label hatamoto --region ap-southeast --type g6-nanode-1 --image linode/ubuntu24.04 --authorized_keys "$(cat ~/.ssh/id_ed25519.pub)" --metadata.user_data "$(base64 --wrap=0 hatamoto-user-data.yaml)"On macOS, use base64 --break=0 --input=hatamoto-user-data.yaml. ap-southeast is Sydney and g6-nanode-1 is the Nanode 1 GB. Add --root_pass for the Lish console and --firewall_id for the firewall from step 1. This command was not run for this page.
FAQ
How much does Hatamoto cost to run on Linode?
A Nanode 1 GB is $5.00 a month in most regions. The Backups service adds $2.00 a month on that plan. Hatamoto is free to install.
Where do I paste the script?
On the Create form, expand Add User Data and paste into the User Data field. You cannot add or edit it on an existing Linode.
Is the default user root?
Yes. Linode adds your SSH key to the root user, and the root password works on the Lish console. There is no default ubuntu or admin account.
Does Linode offer arm64?
Not in the plans and images lists used for this page, which are all x64. It covers amd64.
Are Linode Backups enough?
They help if the whole Linode is lost, but they are file copies taken while the server runs, which is not ideal for a database. Keep Hatamoto's own nightly backups as well. See Backups.
Do I need a root password?
Only for the browser console. An SSH key alone is enough for SSH.
How do I switch the domain later?
Point the new name's A record at the Linode, then run sudo ./install.sh set-domain cms.example.com --email you@example.com from a fresh copy of the installer. The old name redirects.
Hatamoto installs the same way on DigitalOcean, Vultr, Amazon Lightsail, Amazon EC2 and Hetzner Cloud. The full option list is in Install on a VPS.