You have a stateless web app or HTTP API in a supported language and want to deploy code, not servers. Traffic is spiky — autoscaling absorbs it, and Standard can scale to zero between bursts. You want minimal ops: no VM lifecycle, no instance groups, no networking setup.

App Engine vs Compute Engine? · Decisions

The verdict

Pick App Engine to ship application code and let Google run it — no servers, no OS patching, autoscaling built in. Pick Compute Engine when you need the OS, root/SSH access, custom networking, GPUs, or anything that is not a stateless web app. The deciding line is the operations boundary: App Engine trades infrastructure control for near-zero ops burden; Compute Engine gives you full control and the responsibility that comes with it.

Decide interactively

Answer the questions — the helper scores both the options against the sourced table below and shows its reasoning. A heuristic, not an oracle: the verdict above stays the authority.

Head to head

Criterion	App Engine	Compute Engine
Abstraction	PaaS — deploy app code, Google runs the servers	IaaS — you provision and manage the VMs
Scale to zero	Standard: yes. Flexible: no (min 1 instance)	Only via schedule-based autoscaling
Cold starts	Yes — loading requests; warmup mitigates	None inherent — you own the VM lifecycle
Runtimes	Standard: Go, Java, Node, Python, PHP, Ruby. Flexible: any (Docker)	Any — pick the OS, install anything
OS / root access	Standard: no SSH. Flexible: SSH, OS still managed	Full root / SSH; Linux or Windows
Pricing model	Standard: instance-hours. Flexible: vCPU + memory + disk	Per-second; sustained- & committed-use discounts
Max request time	Standard: 10 min auto / 24 h basic. Flexible: 60 min	N/A — not a request-scoped platform
Ideal workload	Stateless web apps & HTTP APIs, minimal ops	Databases, GPU/TPU jobs, daemons, lift-and-shift

When to pick which

Pick App Engine when

You have a stateless web app or HTTP API in a supported language and want to deploy code, not servers.
Traffic is spiky — autoscaling absorbs it, and Standard can scale to zero between bursts.
You want minimal ops: no VM lifecycle, no instance groups, no networking setup.

Pick Compute Engine when

You need root/SSH, a specific OS, kernel modules, or software App Engine will not host.
The workload is not a web app — databases, batch/HPC, GPU/TPU, long-running daemons.
You need full VPC control or fine-grained machine sizing and cost levers.

Sources

Choose an App Engine environment — https://docs.cloud.google.com/appengine/docs/the-appengine-environments
Compute Engine overview — https://docs.cloud.google.com/compute/docs/overview
App Engine Standard — instance management — https://docs.cloud.google.com/appengine/docs/standard/how-instances-are-managed
App Engine Standard runtimes — https://docs.cloud.google.com/appengine/docs/standard/runtimes
Compute Engine autoscaler — https://docs.cloud.google.com/compute/docs/autoscaler
Compute Engine VM pricing — https://cloud.google.com/compute/vm-instance-pricing

Related instruments