How to Launch a Server on Linode (Akamai)
%203.png&w=256&q=75){kind=small}
Linode Is Now Akamai Cloud Compute
Linode was acquired by Akamai in 2022, and the product is now officially marketed as "Akamai Cloud Compute." In practice almost everyone, including Akamai's own support docs in places, still calls it Linode, and the console you sign into, the API, and the instance-creation wizard are effectively unchanged from before the acquisition.
The individual virtual machines are still called Linodes in the dashboard, billing still shows per-hour and per-month rates the same way it always has, and the regions, plan tiers, and Cloud Manager UI carry over directly. If you have used Linode before the rename, nothing about the actual workflow below will feel unfamiliar — the acquisition changed the parent company and some marketing copy, not the product you are about to provision.
Choosing a Plan: Shared CPU vs Dedicated CPU
For a single low-traffic WordPress site or a staging environment, a Shared CPU Nanode plan is enough and is the cheapest way to get a real Linux server running. For anything client-facing that needs to hold up under real traffic — a WooCommerce store, a multi-site agency box, or an app with background jobs — choose a Dedicated CPU plan instead.
Shared CPU plans put your Linode on a host alongside other customers' instances, and while Linode's fair-share scheduling generally keeps this reasonable, a noisy neighbor can still cause brief CPU steal and inconsistent response times during traffic spikes. Dedicated CPU plans give you cores that are never shared with anyone else, which matters most for PHP-FPM workloads processing many concurrent requests, since PHP-heavy sites are CPU-bound far more often than they are RAM-bound. As a starting point, a 2 GB Dedicated CPU plan comfortably runs a single production WordPress site with room for MariaDB and Redis; scale up the plan rather than adding servers until you actually need more than one box.
Picking Ubuntu 22.04 LTS and a Datacenter Region
On the Linode creation page, select Ubuntu 22.04 LTS from the Images tab. It is the distribution CloudStick's Direct Install expects, it has security updates through April 2027, and it is the same base every CloudStick-managed server runs, so there is nothing exotic to reconcile later when you connect this box to the dashboard.
For the region, pick the Akamai/Linode datacenter physically closest to the majority of your visitors, not to you personally. A site serving a US audience from a Newark or Chicago datacenter will feel noticeably faster than the same site hosted in Singapore, and datacenter choice is one setting you cannot change later without redeploying the entire server — it is worth the extra thirty seconds to check the region list against where your traffic actually comes from.
Adding an SSH Key and the Password Login Gotcha
Generate a key pair on your own machine first, then add the public key under "SSH Keys" in your Linode account settings before you create the instance, so you can attach it directly in the creation form instead of pasting it in manually after boot.
On the creation form, tick the SSH key under "Add SSH Keys" so it lands in root's authorized_keys automatically on first boot. Linode's form will still ask you to set a root password on this same page, even though you are also attaching a key — this is not optional, and skipping it just means Linode generates one for you.
That root password stays valid for password-based SSH login even after you have added a key — Linode does not disable password auth for you. If you want the server to be key-only, you must explicitly turn password login off in sshd_config once you are logged in, or the root password becomes a standing brute-force target on the public internet.
Test that key-based login still works in a second terminal window before you close your current session — if PermitRootLogin or the key path is wrong, you want to find out while you still have an active connection, not after you have locked yourself out.
Deploying and Making Your First SSH Connection
Click "Create Linode" and the instance boots in under a minute. The dashboard shows the new server's public IPv4 address on its detail page as soon as provisioning finishes — that IP is everything you need for the next step.
If the key you attached at creation matches the one in your local ssh-agent, this connects immediately with no password prompt. If it instead asks for a password, the key either was not attached correctly in the creation form or your local SSH client is not offering it — check ssh -v root@your-ip for which identity file it tried before assuming the server itself is misconfigured.
Connecting the Fresh Linode to CloudStick
Once you can SSH in, stop working on the terminal and add the server in CloudStick instead. From the dashboard, choose "Add Server" and pick Direct Install, then hand it the Linode's IP and either the root password or your SSH key — CloudStick connects over SSH and provisions Nginx, Apache for PHP, PHP-FPM, MariaDB, Redis, and the CSF firewall on top of the bare Ubuntu 22.04 image automatically.
From that point on, every routine task — creating websites, issuing SSL certificates, switching PHP versions, scheduling backups, managing SSH and FTP users — happens from the CloudStick dashboard, not a terminal. That is the entire value of pairing a raw Linode with CloudStick: Akamai/Linode gives you the compute at a competitive per-hour rate, and CloudStick's flat per-server pricing with no per-site fees means you can add as many sites to this one box as it can handle without your hosting bill scaling with your client count.
To recap the path from zero to a managed server: create the Linode account, choose Shared CPU for light workloads or Dedicated CPU for anything under real traffic, select Ubuntu 22.04 LTS in a region near your users, attach an SSH key at creation and lock down password login afterward, confirm you can SSH in directly, and then hand the IP to CloudStick's Direct Install so the rest of the stack and ongoing management never touch a terminal again.
