Azure Virtual Machines vs Linode

Azure Virtual Machines is a large cloud with Linux, Windows and Arm sizes, billed per minute, that stops charging for compute once you deallocate a VM. Linode is a plain Linux server on Akamai Cloud, billed by the hour with a monthly cap on most plans, and billed until you delete it.

The companies and products

Azure Virtual Machines

Azure Virtual Machines is Microsoft's general-purpose cloud VM service: you rent Linux or Windows machines by the minute in Azure regions worldwide.

It is a hyperscaler IaaS product, not a sandbox API. Each VM runs on Microsoft's Hyper-V hypervisor with its own kernel, root and SSH. You pick from hundreds of sizes, including Arm, burstable and GPU families. Networking, disks, images, firewalls and agent tooling are separate pieces that you set up. It suits teams that already run on Azure and want full control.

Linode

Linode is a general-purpose cloud, now sold as Akamai Cloud, and a Linode is one of its Linux virtual machines.

A Linode is a Linux VM you rent by size, with root, a public IP, local disk and, on older plans, a monthly transfer allowance. You pick a distribution, then install and run your own software on it, next to Akamai Cloud products like Kubernetes, block storage, NodeBalancers, VPCs and cloud firewalls. It is a server host, not an agent sandbox, so this page compares the two where they overlap: giving an agent its own Linux machine.

Which use cases each one fits

For each use case, Battleships prices every sandbox provider on the same workload and sorts them from the cheapest monthly bill up. “5th cheapest of 359” means 4 of the other 358 providers run that workload, with every feature it needs, for less. “With limits” means the provider runs it but misses something, so it is listed after every full match. Open a use case for its whole ranking and what each provider misses.

Use case and its workloadAzure Virtual Machines: price rankLinode: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
Both can host a software factory on full VMs, but on each you build the images, HTTPS and agent driver yourself. boat has those on every sandbox.
114th of 365, with limits
$730 a month
176th of 365, with limits
$1,292 a month
5th cheapest of 365
$634 a month
Always-on AI employees
50 machines 24/7 · 2 vCPU / 4 GB
176th of 361, with limits
$644 a month
218th of 361, with limits
$1,200 a month
6th cheapest of 361
$657 a month
Code interpreter bursts
100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month
118th of 336, with limits
$222 a month
177th of 336, with limits
$1,200 a month
189th of 336, with limits
$2,000 a month
Sandboxes for your users
300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month
Linode bills each 10-minute user session as a full hour, while Azure bills per minute, so Azure costs far less here. boat adds the sandbox API on top.
69th of 349, with limits
$500 a month
118th of 349, with limits
$1,090 a month
3rd cheapest of 349
$209 a month
RL rollouts
1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month
Azure fits RL fleets much better because Spot VMs sell spare capacity cheaply, if rollouts survive eviction with 30 seconds of notice.
22nd of 349, with limits
$1,039 a month
190th of 349, with limits
$24,000 a month
39th of 349, with limits
$2,000 a month
Agent evals
250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month
All three fit. Azure's per-minute billing suits eval batches, while Linode's hourly rounding makes short runs cost more.
5th cheapest of 359
$173 a month
70th cheapest of 359
$1,080 a month
10th cheapest of 359
$200 a month
CI runners
40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month
Both run Docker builds on full VMs, but on Linode every short job is billed as a full hour, and on both you run the runner software yourself.
33rd cheapest of 374
$335 a month
138th cheapest of 374
$4,320 a month
2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
Linode suits a 24/7 dev box well: a flat hourly price with a monthly cap and no commitment, where Azure's low always-on price needs a reservation.
74th cheapest of 371
$94 a month
41st cheapest of 371
$48 a month
19th cheapest of 371
$26 a month
Computer-use agents
50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month
On both you set up the desktop yourself: on Azure you install xfce and xrdp, and on Linode you install a desktop such as Xfce and open it in the Glish console. boat streams a 60 fps desktop.
143rd of 367, with limits
$192 a month
303rd of 367, with limits
$1,440 a month
7th cheapest of 367
$200 a month
Browser-use agents
50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month
233rd of 356, with limits
$107 a month
327th of 356, with limits
$1,080 a month
7th cheapest of 356
$200 a month
Scraping & bots (startup scale)
50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month
258th of 343, with limits
$116 a month
255th of 343, with limits
$108 a month
6th cheapest of 343
$90 a month
Mass scraping & bots (undetectable)
1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month
84th of 327, with limits
$2,044 a month
91st of 327, with limits
$2,160 a month
73rd of 327, with limits
$1,800 a month
Parallel red teaming
200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month
164th of 351, with limits
$46 a month
228th of 351, with limits
$182 a month
3rd cheapest of 351
$200 a month
GPU eval jobs
10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month
Linode is ranked here with GPU instances priced by the hour. Azure also has GPU families such as NC with Nvidia H100 and A100, and boat has no GPU on any size.
Not ranked: misses a requirement80th of 102, with limits
$1,500 a month
Not ranked: misses a requirement
macOS agents
5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month
Not ranked: misses a requirementNot ranked: misses a requirementNot ranked: misses a requirement

Key features

FeatureAzure Virtual MachinesLinodeboat
What you getA general cloud VM in a hyperscaler, with hundreds of sizesA general Linux server on Akamai Cloud that you set up yourselfA sandbox API for agents, on full VMs
IsolationFull Hyper-V VM with its own kernelFull VM with its own kernel, isolated at the hypervisorFull VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared
Docker and nested virtualizationRoot and Docker; nested virtualization on many Intel and AMD sizes (such as D, E and F series), not on Arm or B-seriesRoot and Docker; Akamai documents no nested virtualization, and Linode staff said in 2020 it was not supported because of live migrationDocker, root, systemd and /dev/kvm on every sandbox
BillingPer full minute while running; no plan feeHourly, rounded up to the next hour; monthly cap on most plans; no plan feePer second while running, from a monthly plan of $20 or more; starts per minute, hour and day capped by plan
StoppingA deallocated VM stops compute billing; disks and static IPs keep billingA powered-off Linode is still billed; to stop paying you save an image, delete the Linode and rebuild it laterNo compute charge while stopped; disk kept at least 14 days, longer as a saved snapshot
Snapshots and pauseManual disk snapshots; scheduled ones need Azure Backup; hibernation keeps memory on supported sizesPaid Backups add-on: scheduled backups plus one manual snapshot per Linode; custom images billed per GB-monthDisk saved every minute and at each stop; writes after the last good snapshot can be lost if a machine fails; resume reboots from disk
Fork and cloneCapture a gallery image (the VM stops briefly) or snapshot its disks, then create new VMs that boot coldClone copies all disks to a new Linode; the docs say to power off first to avoid corruptionFork a running sandbox in one call, from its last 1-minute snapshot (disk, no memory)
Desktop and computer useYou set it up: install a desktop such as xfce and xrdp, then open port 3389 (Microsoft guide)You set it up: install a desktop such as Xfce and open it in the Glish console (Akamai guide)1920x1080 desktop and Chrome at 60 fps, computer-use tools and browser control, embeddable stream
Reaching the machinePublic IPv4, static if you pay for it, and ports through security groups; you set up HTTPS, or add a load balancer or gatewayA stable public IPv4 on any port; HTTPS needs a TLS certificate on the instance or a paid NodeBalancerUp to 50 HTTPS URLs per sandbox, token-gated by default; public IPv6; no static IPv4, and the IP changes at each resume
Outbound rulesSecurity group rules by IP; domain allowlists with the paid Azure FirewallFree Cloud Firewall with outbound rules by protocol, port and IP rangeOpen internet on every plan; no provider-side allowlist
Coding agents and keysYou set it up: install agents with Run Command, scripts or SSH; Key Vault secrets are fetched into the VMYou set it up: install each agent CLI yourself or with a StackScript; secrets reach the server through user data or filesSeven harnesses installed, including Claude Code, Codex and OpenCode, with a prompt, steer and events API; optional AI credentials proxy ($1 a day plus $1 per 1,000 requests)
Operating systems and CPUsLinux and Windows on Intel, AMD and Arm sizes, including burstable B-seriesLinux on shared or dedicated CPU plansLinux x86_64 only; no promised CPU model; Windows apps through Wine
GPUsGPU families such as NC with Nvidia H100 and A100Nvidia RTX 4000 Ada, RTX PRO 6000 Blackwell (on request) and Quadro RTX 6000 by the hourNo GPU on any size
Regions77 regions worldwide, available or coming soon33 regions in 15 countriesGermany, Finland and France; you cannot pick a region; no US or Asia region
Every feature Battleships tracks (43)
FeatureAzure Virtual MachinesLinodeboat
Full VM (own kernel)YesYesYes
Docker insideYesYesYes
Nested virtualizationYesNo documented wayYes
RootYesYesYes
SystemdYesYesYes
Desktop GUIWith your own setupWith your own setupYes
BrowserNo documented wayNo documented wayYes
Computer-use APINo documented wayNo documented wayYes
SSHYesYesYes
Persistent diskYesYesYes
Pause/resumeYesNo documented wayYes
Automatic snapshotsNo documented wayNo documented wayYes
Fork/cloneYesYesYes
Live fork (no pause)No documented wayNo documented wayYes
Memory forkNo documented wayNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopNo documented wayNo documented wayNo documented way
Wake on requestNo documented wayNo documented wayNo documented way
HTTPS preview URLsNo documented wayWith your own setupYes
Raw TCP inboundYesYesYes
Public IPv4YesYesNo documented way
Egress allowlistYesYesNo documented way
Secret proxyNo documented wayNo documented wayYes
Secret proxy for any APINo documented wayNo documented wayYes
Preinstalled agentsNo documented wayNo documented wayYes
Agent harness APINo documented wayNo documented wayYes
MCP serverYesNo documented wayNo documented way
GPUYesYesNo documented way
WindowsYesNo documented wayNo documented way
Arm64YesNo documented wayNo documented way
Self-hostingNo documented wayNo documented wayNo documented way
BYOCNo documented wayNo documented wayNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysNot publishedYesYes
Spend limitsNo documented wayNo documented wayYes
Usage per sandbox (API)YesNo documented wayYes
Audit logsYesYesNo documented way
SSOYesYesNo documented way
SOC 2YesYesNo documented way
HIPAAYesYesNo documented way
EU data residencyYesYesNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

Azure Virtual MachinesNot measured
LinodeNot measured
boat28.06 runs/s

Azure Virtual Machines and Linode are not in the public benchmarks we use, so we cannot say which is faster. In StarSling's run of 3 October 2026 (run 37073680030), boat did 28.06 V8 Web Tooling Benchmark runs per second at 4 vCPU / 8 GB, second of 15. Every boat sandbox in that run ran on an AMD Ryzen 9 9950X host. boat also places sandboxes on Ryzen 7 9700X hosts, which that run did not test, and does not promise a CPU model. Speed on Azure and Linode depends on the CPU family or plan you pick.

V8 Web Tooling Benchmark at a 4 vCPU / 8 GB target, runs per second, higher is better. Source: StarSling's run of 3 October 2026 (run 37073680030), median of 5 sandboxes. Providers ran on different hardware in different regions. StarSling gives a shared rank when the run cannot separate two providers. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure. Azure Virtual Machines and Linode are not in the public benchmarks we use, so we cannot say which is faster.

Pricing in five scenarios

Each bill is priced from the providers' public price lists by the open Battleships engine, with the cheapest plan that runs the scenario. Start limits, per-start fees and plan minimums are in the price, boat's included.

ScenarioAzure Virtual Machines, a monthLinode, a monthboat, a month
One coding agent, workdays
4 vCPU / 8 GB, 50 GB disk, 8 hours a day, 22 days a month, files kept between days
$26 · Pay-as-you-go subscription (no plan fee)$13 · Usage account$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$48 · Pay-as-you-go subscription (no plan fee) · with limits$48 · Usage account$26 · $20/mo
50 agents in parallel
50 machines of 4 vCPU / 8 GB at once, 8-hour sessions, 1,100 sessions a month, Docker inside
$1,168 · Pay-as-you-go subscription (no plan fee)$634 · Usage account$317 · $20/mo × 3 seats
Sandboxes for your users
2 vCPU / 4 GB, 30,000 sessions of 10 minutes a month, up to 300 at once
$225 · Pay-as-you-go subscription (no plan fee)$1,080 · Usage account$200 · $100/mo × 2 seats
1,000 short jobs at once
2 vCPU / 4 GB, 1,000 at once, 3 minutes each, 200,000 jobs a month
$483 · Pay-as-you-go subscription (no plan fee) · with limits$7,200 · Usage account · with limits$8,800 · $2000/mo · with limits

Azure Virtual Machines: Azure bills each VM per full minute while it runs, with no plan fee. Disks, public IPv4 addresses and egress bill on top, and disks keep billing while the VM is deallocated. Its lowest always-on price needs a 3-year reservation, billed whether the VM runs or not. Below about $20 of use a month, Azure costs less than boat's smallest plan.

Linode: Each Linode size has an hourly price, rounded up to the next full hour, billed from create to delete, also while powered off. A shared 4 vCPU / 8 GB Linode costs $0.072 an hour, capped at $48 a month. G8 dedicated and GPU plans have no monthly cap since July 2026. Backups, images and extra egress cost extra.

Linode: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. A default 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs. The $20 plan includes 12 starts a minute, 60 an hour and 200 a day; extra starts cost $0.03 to $0.07 each. A stopped sandbox has no compute charge. Saved snapshots above the plan's count and the AI credentials proxy still bill while stopped.

Limits in those scenarios

Azure caps how many vCPUs you can run per region and per VM family, stopped VMs still count, and new subscriptions raise the quota by request. Linode publishes no fixed instance limit, and a new account raises its limits by support ticket. For 1,000 short jobs at once none of the three fits. Azure's burstable B-series guarantees 20% to 40% of each vCPU depending on size and throttles above that. Linode bills every 3-minute job as a full hour, on shared vCPUs that other tenants can slow. On the $2,000 plan, boat charges for starts above 90 a minute, refuses them above 270 with 429, and never queues a start.

ScenarioAzure Virtual MachinesLinodeboat
One coding agent, workdaysNone for this scenarioNone for this scenarioNone for this scenario
One agent that never stops
  • 3-year commitment
None for this scenarioNone for this scenario
50 agents in parallelNone for this scenarioNone for this scenarioNone for this scenario
Sandboxes for your usersNone for this scenarioNone for this scenarioNone for this scenario
1,000 short jobs at once
  • burstable CPU: 30% of each vCPU guaranteed, throttled above that
  • shared vCPUs on this tier: heavy, sustained CPU use can be slowed by other tenants
  • 2,400 starts/day included, paid above that (needs ~6,667)
  • 600 starts/hour included, paid above that (needs ~1,000)
  • starts above 90/min are paid, and starts above 270/min fail with 429

Which one should you use?

Use Azure Virtual Machines when

you need Windows, Arm, nested virtualization on Intel and AMD sizes, Spot pricing, per-minute billing, or your company already runs inside Azure.

  • Windows, Arm and nested VMs. Useful if you need Windows guests, Arm sizes, or nested virtualization, which Azure offers on many Intel and AMD sizes such as D, E and F series.
  • Per-minute billing and real stops. Useful for short or bursty work: Azure bills per minute and stops compute billing once you deallocate a VM.
  • Spot VMs, hibernation and durable disks. Useful if big batches can survive eviction for a lower price, a machine must resume with its memory, or disks must keep three replicas.

Use Linode when

you want a plain Linux server that runs all month at a simple capped price, with a stable IPv4, a free outbound firewall, GPUs by the hour and regions around the world.

  • Simple, capped server billing. Useful for a server that runs all month: one hourly price with a monthly cap on most plans, and no commitment.
  • Free outbound firewall and a stable IP. Useful if outbound traffic must follow rules: Cloud Firewall limits it by protocol, port and IP range at no charge, and the public IPv4 stays for the life of the Linode.
  • Shared or dedicated CPU. Useful if you want to choose between low-cost shared CPU and dedicated CPU on the same simple plans.

Where boat fits

Azure Virtual Machines and Linode rent you plain servers, and both leave the agent layer to you. If you run agents, boat gives each one a full VM that already has Docker, /dev/kvm, a desktop, HTTPS URLs and coding agents you drive by API. Keep Azure or Linode for GPUs, Windows, a static IP or regions outside Germany, Finland and France.

No compute charge while stopped, forks of live machines

A powered-off Linode keeps billing, and a deallocated Azure VM still bills its disks. On Linode a clone needs the machine powered off first, and an Azure copy boots cold from an image or snapshot. boat forks a running sandbox from its last 1-minute snapshot and saves its disk every minute.

/dev/kvm on every sandbox

Akamai documents no nested virtualization on Linode, and Azure has it on many Intel and AMD sizes but not on Arm or burstable ones. On boat, Android emulators, Firecracker and VMs inside work on every sandbox, next to Docker and systemd.

Agents, desktop and keys built in

On both clouds you install and supervise each coding agent, a desktop and TLS yourself, and keys placed on the server are readable by agent code. boat ships agents, a 60 fps desktop and HTTPS on up to 50 ports. Its optional paid proxy keeps the real keys of supported AI providers out.

Use boat when you run agents: each one gets a full VM with Docker, /dev/kvm, forks of running sandboxes, snapshots every minute, a desktop, HTTPS URLs and coding agents driven by API, with no compute charge while stopped. Compare it one to one: boat vs Azure Virtual Machines and boat vs Linode.

boat's own limits
  • Plans start at $20 a month. The plan price comes back as VM time for that month. Unused time does not carry over. Source
  • Starts (create, fork, resume): the $20 plan includes 12 a minute, 60 an hour and 200 a day. The $2,000 plan includes 90 a minute, 600 an hour and 2,400 a day. Extra starts cost $0.03 to $0.07. A start fails with 429 above 3 times the included starts per minute, or 6 times per hour or per day. Source
  • A stopped sandbox has no compute charge. boat keeps its disk for at least 14 days. A saved snapshot keeps it longer; extra saved snapshots and the AI credentials proxy are paid. Source
  • Auto-stop defaults to 1 hour. You can turn it off on a paid plan. The trial allows 2 hours at most. Source
  • boat saves the disk every minute and at each stop. Memory, running programs and /tmp are not saved: a resume is like a reboot. A machine failure loses writes after the last good snapshot. Source
  • Machines run in Germany, Finland and France only. Snapshot copies can be stored outside the EU. Source
  • Public IPv6 and outbound IPv4. No dedicated IPv4. The IP changes at each resume. Source
  • Hosts are AMD Ryzen 7 9700X and Ryzen 9 9950X. vCPUs are shared. No GPU. You cannot boot your own Docker image. Source

Questions people ask

Is Azure Virtual Machines cheaper than Linode?

It depends on how the machine runs. One coding agent on workdays comes to $13 a month on Linode, if you delete the Linode each night, against $26 on Azure. 50 agents in parallel come to $634 on Linode against $1,168 on Azure. Short sessions flip it: 30,000 ten-minute user sandboxes come to $225 on Azure against $1,080 on Linode, because Linode bills each one as a full hour. boat comes to $20, $317 and $200 for those three.

Which is faster, Azure Virtual Machines or Linode?

Neither is in the public benchmarks we use, so we cannot say. Speed depends on the size you pick: Azure has burstable B-series and many CPU families, and Linode has shared and dedicated CPU plans. boat did 28.06 V8 Web Tooling Benchmark runs per second at 4 vCPU / 8 GB in StarSling's run of 3 October 2026, on an AMD Ryzen 9 9950X host.

Can Azure Virtual Machines or Linode run nested VMs and Docker?

Both run Docker with root. Azure supports nested virtualization on many Intel and AMD sizes, such as D, E and F series, but not on Arm or B-series. Akamai documents no nested virtualization, and Linode staff said in 2020 it was not supported because of live migration. boat has /dev/kvm on every sandbox.

Do I pay for a stopped VM on Azure or Linode?

On Linode, yes: a powered-off Linode is billed until you delete it. On Azure, a VM shut down from inside the OS keeps billing; a stop (deallocate) from the portal, CLI or API ends compute billing, but disks and static IPs still bill. A stopped boat sandbox has no compute charge, and boat keeps its disk for at least 14 days. Saved snapshots above the plan's count and the AI credentials proxy still bill.

Does Linode have Windows or Arm like Azure?

Linode plans run Linux, while Azure has Windows guests and Arm sizes on Cobalt 100 and Ampere Altra. boat also runs Linux only, on x86_64, with Windows apps through Wine.

Where does my data run?

Azure lists 77 regions worldwide and Linode has 33 regions in 15 countries, and both have regions in the EU. boat sandboxes run on machines in Germany, Finland and France, and you cannot pick a region. boat can store snapshot copies outside the EU.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons