AWS EC2 vs Google Compute Engine
AWS EC2 and Google Compute Engine are both hyperscaler VM services: you rent a machine with its own kernel and build everything else yourself. EC2 adds Mac hosts and came in lower on list price in every scenario we priced. Compute Engine runs in a few more regions, and the E2 sizes we priced have twice the memory.
The companies and products
AWS EC2
AWS EC2 is Amazon's general-purpose cloud VM service, not a sandbox product: you rent virtual servers by the second and set them up yourself.
You pick an instance type (Intel, AMD, Graviton Arm, GPU or Mac), a machine image and a network, and EC2 boots a Nitro VM with its own kernel and root access. Disks are EBS volumes, and security groups control inbound traffic. You set up the agent parts yourself: agents, desktops, HTTPS URLs and key handling. AWS also sells managed agent sandboxes, Bedrock AgentCore Code Interpreter and Browser, as a separate product. EC2 serves every kind of server workload, from websites to GPU training, across AWS's worldwide regions.
Google Compute Engine
Google Compute Engine is Google Cloud's general-purpose VM service, not a sandbox product: you rent virtual machines by the second and set them up yourself.
You pick a machine type (E2, N2D, C3D, Arm T2A, GPU families and more), a boot image and a network. Compute Engine boots a KVM-based VM with its own kernel and root access. Disks are Persistent Disk or Hyperdisk volumes, and VPC firewall rules control traffic. You set up the agent parts yourself: agents, a desktop, HTTPS URLs and key handling. Compute Engine serves every kind of server workload, from websites to GPU training, in Google Cloud regions worldwide.
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. “7th cheapest of 359” means 6 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 workload | AWS EC2: price rank | Google Compute Engine: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Google Compute Engine ranks 29th as a full match, AWS EC2 ranks 118th as a compromise, and boat ranks 5th. On both clouds you build the agent setup, preview URLs and cloning yourself; boat has them built in. | 118th of 365, with limits $775 a month | 29th cheapest of 365 $2,607 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB | 177th of 361, with limits $646 a month | 45th cheapest of 361 $2,558 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 Short bursts suit both clouds better than boat's start limits allow: Google Compute Engine ranks 98th, AWS EC2 106th and boat 189th, all as a compromise. | 106th of 336, with limits $165 a month | 98th of 336, with limits $133 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 On both clouds you build HTTPS access, isolation per user and lifecycle tooling yourself, so both are a compromise. boat ranks 3rd here because it ships them for each sandbox. | 76th of 349, with limits $607 a month | 97th of 349, with limits $836 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 AWS EC2 ranks 15th for RL rollouts and Google Compute Engine 40th, both as a compromise; both can launch big fleets once your quota is raised. | 15th of 349, with limits $830 a month | 40th of 349, with limits $2,050 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 Agent evals fit all three fully: AWS EC2 ranks 7th, boat 10th and Google Compute Engine 12th. | 7th cheapest of 359 $177 a month | 12th cheapest of 359 $228 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 CI fits both clouds fully: AWS EC2 ranks 19th and Compute Engine 39th. boat ranks 2nd, with /dev/kvm on every sandbox. | 19th cheapest of 374 $255 a month | 39th cheapest of 374 $359 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB | 60th cheapest of 371 $76 a month | 84th cheapest of 371 $109 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 Compute Engine ranks 49th as a full match: Google's guide sets up Xfce and Chrome Remote Desktop. EC2 is a compromise (Amazon DCV is a stream you install). boat ranks 7th with a built-in 60fps desktop. | 145th of 367, with limits $195 a month | 49th cheapest of 367 $720 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 | 232nd of 356, with limits $101 a month | 86th of 356, with limits $378 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 | 259th of 343, with limits $116 a month | 99th cheapest of 343 $256 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 | 85th of 327, with limits $2,046 a month | 101st of 327, with limits $2,644 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 | 162nd of 351, with limits $45 a month | 21st cheapest of 351 $187 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 Of these three, only AWS EC2 is priced for GPU jobs here, at rank 26. Compute Engine rents GPUs too, but has no row in this table, and boat has no GPU. | 26th cheapest of 102 $1,723 a month | Not ranked: misses a requirement | 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 requirement | Not ranked: misses a requirement | Not ranked: misses a requirement |
Key features
| Feature | AWS EC2 | Google Compute Engine | boat |
|---|---|---|---|
| What you get | A general cloud VM; you install and wire everything else | A general cloud VM; you set up everything else from images, startup scripts or your own tooling | An agent sandbox: a full VM with agents, desktop, URLs and snapshots set up |
| Isolation | Every instance is a Nitro VM with its own kernel | Every instance is a KVM-based VM with its own kernel | Every sandbox is a full VM with its own kernel; vCPUs are shared, not dedicated cores |
| Docker and nested virtualization | Docker, root and systemd on any instance; KVM on Intel 7th/8th-gen families (C7i, M7i, R7i, C8i, M8i, R8i, X8i, I7i and variants) and metal, not on Graviton or AMD | Docker, root and systemd on any VM; nested KVM once you enable it per VM on Intel families or N4D, not on E2, Arm or other AMD VMs | Docker, root, systemd and /dev/kvm on every sandbox |
| Coding agents | You set it up: install agents and drive them over SSH or Systems Manager | You set it up: install agents and drive them over SSH or startup scripts | Seven harnesses installed, including Claude Code, Codex and OpenCode, with a prompt, steer and events API |
| Keeping keys out of the machine | IAM roles give the instance short-lived AWS credentials; for other API keys you run your own proxy | Service account tokens and Secret Manager values are read from inside the VM; for a key-injecting proxy you run your own | Optional paid AI credentials proxy ($1 a day plus $1 per 1,000 requests): real keys of supported model providers stay out; other secrets still enter |
| Desktop and computer use | Linux images have no desktop by default; install one and stream it with Amazon DCV (no license fee on EC2); Remote Desktop on Windows; no computer-use API | You set it up: install a desktop such as Xfce and Chrome Remote Desktop (Google guide), then add your own click and screenshot tools | Built-in desktop and Chrome at 1920x1080, 60fps, with computer-use tools and an embeddable stream |
| Reaching the machine | Public IPv4, static Elastic IPs and any port through security groups; HTTPS needs a domain plus an ACM certificate on a load balancer, or a web server you configure | External IPv4 (static on request) and any port through firewall rules; HTTPS needs a domain plus a load balancer with a Google-managed certificate, or a web server you configure | HTTPS URLs on up to 50 ports, token-gated by default; SSH; no static IPv4, and the IP changes at each resume |
| Files after a stop | EBS disks are kept until you delete them and billed while stopped; snapshots are manual or scheduled with Data Lifecycle Manager | Persistent disks are kept with no time limit and billed while stopped; snapshots are on demand or on a schedule you set | Disk saved every minute and at each stop; kept at least 14 days after a stop, longer with a saved snapshot |
| Copying a machine | Make an image and boot a new instance from it | Make a machine image (disks, not memory) and boot a new VM from it | Fork a running sandbox from its last 1-minute snapshot |
| Pausing with memory | Hibernation saves memory to disk and resumes the same instance | Suspend keeps memory for the same VM for up to 60 days, and the memory keeps billing while suspended | Memory is not kept; resume reboots from disk |
| Outbound network rules | Security group rules per instance; domain allowlists with AWS Network Firewall or DNS Firewall (paid) | VPC egress firewall rules by IP and port; domain rules on Cloud NGFW Standard (paid) | Open internet on every plan; no provider-side allowlist |
| GPUs | Nvidia GPU instances, from L4 and L40S up to H100 and H200 | Nvidia GPUs from T4 and L4 up to H100, H200, B200, GB200 and GB300 | No GPU on any size |
| Operating systems and CPUs | Linux and Windows on Intel, AMD and Graviton Arm; macOS on Mac Dedicated Hosts (24-hour minimum) | Linux and Windows Server on Intel, AMD and Arm; no macOS | Ubuntu 24.04 x86_64 on AMD Ryzen 7 9700X and Ryzen 9 9950X hosts; Windows programs through Wine |
| Regions | 39 regions and 124 availability zones, including several in the EU | 43 regions and 130 zones, including many in the EU | Germany, Finland and France; no US or Asia region, and you cannot pick one |
Every feature Battleships tracks (43)
| Feature | AWS EC2 | Google Compute Engine | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | Yes | No documented way | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Yes | Yes | Yes |
| Desktop GUI | With your own setup | With your own setup | Yes |
| Browser | No documented way | With your own setup | Yes |
| Computer-use API | No documented way | No documented way | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | No documented way | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | No documented way | Yes | Yes |
| Memory fork | No documented way | No documented way | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | Yes | Yes |
| Idle auto-stop | No documented way | No documented way | No documented way |
| Wake on request | No documented way | No documented way | No documented way |
| HTTPS preview URLs | No documented way | With your own setup | Yes |
| Raw TCP inbound | Yes | Yes | Yes |
| Public IPv4 | Yes | Yes | No documented way |
| Egress allowlist | Yes | Yes | No documented way |
| Secret proxy | No documented way | No documented way | Yes |
| Secret proxy for any API | No documented way | No documented way | Yes |
| Preinstalled agents | No documented way | No documented way | Yes |
| Agent harness API | No documented way | No documented way | Yes |
| MCP server | No documented way | No documented way | No documented way |
| GPU | Yes | Yes | No documented way |
| Windows | Yes | No documented way | No documented way |
| Arm64 | Yes | Yes | No documented way |
| Self-hosting | No documented way | No documented way | No documented way |
| BYOC | No documented way | No documented way | No documented way |
| Open source | No documented way | No documented way | No documented way |
| Scoped API keys | Not published | Not published | Yes |
| Spend limits | Not published | No documented way | Yes |
| Usage per sandbox (API) | Yes | Yes | Yes |
| Audit logs | Not published | Yes | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Yes | Yes | No documented way |
| HIPAA | Yes | Yes | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
Neither EC2 nor Compute Engine is in the public benchmarks we use, so we cannot say which is faster. Speed on both clouds depends on the machine family you pick. In StarSling's run of 3 October 2026 (run 37073680030), boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15. 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.
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. AWS EC2 and Google Compute Engine 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.
| Scenario | AWS EC2, a month | Google Compute Engine, a month | boat, 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 | $21 · Pay-as-you-go (no platform fee) | $31 · Pay-as-you-go billing account (no plan fee) | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $51 · Pay-as-you-go (no platform fee) · with limits | $64 · Pay-as-you-go billing account (no plan fee) · with limits | $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 | $944 · Pay-as-you-go (no platform fee) | $1,291 · Pay-as-you-go billing account (no plan fee) | $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 | $269 · Pay-as-you-go (no platform fee) | $378 · Pay-as-you-go billing account (no plan fee) | $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 | $502 · Pay-as-you-go (no platform fee) | $690 · Pay-as-you-go billing account (no plan fee) | $8,800 · $2000/mo · with limits |
AWS EC2: EC2 bills each instance per second with a 60 second minimum, here the Graviton c7g sizes on demand, with no platform fee. EBS disks bill on top, also while stopped. A public IPv4 address bills while the instance runs, and an Elastic IP you keep also bills while stopped. Lower rates need a 1-year or 3-year commitment.
Google Compute Engine: Compute Engine bills each VM per second after a 1 minute minimum, here E2 sizes on demand in us-central1, with no platform fee. Disks and external IPs bill on top while they exist, and a suspended VM keeps billing its memory. New users get $300 of trial credit for 90 days.
Limits in those scenarios
A new AWS account can run only 5 vCPUs of standard On-Demand instances per region, which is one 4 vCPU machine, until AWS raises it. Compute Engine sets per-region CPU quotas that vary by project, some new projects also have a global CPU cap, and a free trial account cannot ask for more. So 50 agents in parallel or 300 sandboxes for your users need a quota request first on both. On both, one agent that never stops reaches the price shown only with a 3-year commitment. boat's limits: plans cost $20, $100, $500 or $2,000 a month, and the plan price comes back as VM time for that month only. A stopped sandbox has no compute charge, but saved snapshots above the included count and the AI credentials proxy still charge. For 1,000 short jobs at once, boat's $2,000 plan includes 90 starts a minute and 2,400 a day, charges for extra starts and refuses them above 270 a minute, so that burst does not fit boat; both clouds fit it.
| Scenario | AWS EC2 | Google Compute Engine | boat |
|---|---|---|---|
| One coding agent, workdays | None for this scenario | None for this scenario | None for this scenario |
| One agent that never stops |
|
| None for this scenario |
| 50 agents in parallel | None for this scenario | None for this scenario | None for this scenario |
| Sandboxes for your users | None for this scenario | None for this scenario | None for this scenario |
| 1,000 short jobs at once | None for this scenario | None for this scenario |
|
Which one should you use?
Use AWS EC2 when
you need macOS or Windows alongside Linux, Graviton Arm machines, or the lower list price of the two clouds in our scenarios, and you have the people to build agent tooling on top.
- Mac hosts for macOS work. Useful if your agents need macOS or Xcode: EC2 rents Mac instances on Dedicated Hosts, and Compute Engine has no macOS.
- Lower list prices in our scenarios. EC2's Graviton sizes came in below Compute Engine's E2 sizes in all five scenarios we priced, though E2 gives more memory.
Use Google Compute Engine when
you want memory suspend, more memory per vCPU in the sizes we priced, or a Google Cloud region near your users, and you will build the agent tooling yourself.
- Memory suspend for up to 60 days. Useful if a VM must resume with its processes intact: Compute Engine can suspend a VM with its memory for up to 60 days.
- More memory in the sizes we priced. Useful for memory-hungry agents: the E2 sizes we priced give twice the memory of EC2's c7g sizes, such as 16 GiB on 4 vCPUs.
- A few more regions. Useful if you need a VM close to users in a specific place: Google Cloud runs 43 regions and 130 zones.
Where boat fits
EC2 and Compute Engine are general clouds, so the choice between them often comes down to GPUs, macOS, regions and the account you already have. If you run agents, both hand you a bare VM and leave the agent setup, desktops, URLs and copies to you. boat gives each agent a full VM with that ready, on machines in Germany, Finland and France.
Coding agents you drive from outside
On EC2 and Compute Engine you write the code that installs, prompts and watches each agent. boat installs seven harnesses with an API. Its optional paid credentials proxy keeps model provider keys out; other secrets still enter the sandbox.
/dev/kvm, minute snapshots and forks on every sandbox
Both clouds give nested KVM on chosen families: EC2 on Intel 7th/8th-gen and metal, Compute Engine on Intel families and N4D. On both, a copy means an image and a fresh boot, and stopped disks keep billing. boat forks a running sandbox; writes from the last minute can be missing from the fork.
Desktop, browser and HTTPS URLs ready
A computer-use agent on either cloud needs a desktop and stream you install, plus your own click tools, and each preview URL needs a certificate and a load balancer or web server. boat has a 60fps desktop and HTTPS on 50 ports.
Use boat when you run agents and want each one on a ready, full VM: coding agents with an API, /dev/kvm, a built-in desktop, HTTPS URLs, a disk saved every minute and forks, with no infrastructure to assemble. Compare it one to one: boat vs AWS EC2 and boat vs Google Compute Engine.
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 AWS EC2 cheaper than Google Compute Engine?
On list price, in all five scenarios we priced, yes. 50 agents in parallel come to $944 a month on EC2 against $1,291 on Compute Engine, and the 1,000-job burst to $502 against $690. The E2 sizes we priced carry twice the memory. boat comes to $317 a month for the 50 agents and does not fit the 1,000-job burst.
Which is faster, EC2 or Compute Engine?
We cannot say: neither is in the public benchmarks we use, and speed on both depends on the machine family you pick. boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB in StarSling's run of 3 October 2026, on an AMD Ryzen 9 9950X host.
Can EC2 and Compute Engine run Docker and nested virtualization?
Both run Docker with root and systemd on any VM. EC2 offers KVM on Intel 7th/8th-gen families (C7i, M7i, R7i, C8i, M8i, R8i, X8i, I7i and variants) and on metal, not on Graviton or AMD. Compute Engine offers Linux KVM on Intel families and N4D once you enable it per VM, not on E2, Arm or other AMD VMs. boat has /dev/kvm on every sandbox.
Do EC2 and Compute Engine support macOS and Windows?
EC2 runs Linux and Windows and rents Mac instances on Dedicated Hosts with a 24-hour minimum. Compute Engine runs Linux and Windows Server but has no macOS. boat runs Linux only; Windows programs run through Wine on its desktop.
Which has more regions?
Compute Engine runs in 43 regions and 130 zones, and EC2 in 39 regions and 124 availability zones, both including several in the EU. boat runs on machines in Germany, Finland and France, and you cannot pick a region. Snapshot copies can be stored outside the EU.
How does boat compare to EC2 and Compute Engine for agents?
boat is an agent sandbox rather than a general cloud: each sandbox is a full VM with coding agents, a desktop, HTTPS URLs, /dev/kvm, minute snapshots and forks ready. It has no GPUs, Windows or macOS, and its start limits do not fit a 1,000-job burst, where both clouds do.
Try boat
Install the CLI, then run boat new.
7-day free trial