Table of Contents
The Free Tier, exactly as documented
| Free Tier item (Compute Engine) | Allowance per month | Condition |
|---|---|---|
| VM instance | 1 non-preemptible e2-micro | In us-west1 (Oregon), us-central1 (Iowa) or us-east1 (South Carolina) |
| How the limit is counted | Hours equal to the hours in the month | "By time, not by instance"; usage combined across the three regions |
| Disk | 30 GB-months standard persistent disk | |
| Outbound transfer | 1 GB from North America to all regions | Excluding China and Australia |
| GPUs and TPUs | None | Always charged |
Two points people miss. The free allowance is a time budget, so two e2-micro instances running all month consume double and half the month is billed; run one. And the three qualifying regions are fixed; an e2-micro in Ashburn or Los Angeles is a paid instance. The e2-micro itself is a shared-core machine intended for light, bursty work; Google's own free-tier page says nothing about what it can run, and this page makes no performance claim beyond the obvious: a static site, a bot, a cron job or a small tool fit, a busy database-backed application does not.
The $300 credit and what happens after
Google's Free Tier documentation describes $300 in credit for new customers, with the Free Trial ending when the credit is used or 90 days have passed, whichever comes first. During the trial nothing is charged. To continue afterward you upgrade to a paid billing account; the Always Free allowances above remain, and everything else is billed at the published rates. The credit is meaningful for a learning quarter or a short project and irrelevant to the price of a server kept for years, which is why this page separates it from the Free Tier.
Nine US regions
From Google's regions and zones documentation in September 2026: us-central1 (Council Bluffs, Iowa), us-east1 (Moncks Corner, South Carolina), us-east4 (Ashburn, Virginia), us-east5 (Columbus, Ohio), us-south1 (Dallas, Texas), us-west1 (The Dalles, Oregon), us-west2 (Los Angeles), us-west3 (Salt Lake City) and us-west4 (Las Vegas). That is the widest US footprint of any provider covered here, and the locations are named to the city, which the budget hosts rarely do. Machine prices differ by region, and the Free Tier applies in three of the nine.
How a Compute Engine bill is built
There is no plan. A VM is a machine type (e2-micro, e2-small, e2-medium and up through many families) priced per hour of vCPU and memory in a given region and billed by the second after a one-minute minimum (Google's page: "After 1 minute, your instance is billed on a per-second basis"). On top come the persistent disk, an external IP address if you keep one, and outbound data transfer beyond the free allowance, each on its own pricing page. Google's pricing page states two automatic and contractual reductions: sustained use discounts, "automatic discount of up to 30% on resources that are used for more than 25% of a month", and committed use discounts, "up to a 70% discount for memory-optimized machine types and up to a 55% discount for all other machine types" for one- or three-year commitments.
The per-hour figures on that page are rendered by script and are not quoted here; the number that matters is the one Google's pricing calculator gives for your machine type, region, disk size and expected egress. For a small always-on VM the monthly total is a platform price rather than a VPS price, and the difference between a careful and a careless configuration (a larger disk, a forgotten static IP, egress to the wrong region) can exceed the VM itself.
Where Google Cloud fits, and where it does not
- Fits: a team already using Google Cloud services (Cloud SQL, GCS, BigQuery) that wants a VM next to them; someone learning cloud infrastructure with the $300 credit; a free e2-micro for a light, always-on task; anyone who needs a specific US region among nine.
- Does not fit: a person who wants one server at one monthly price; anyone who will not read a billing report; workloads that move a lot of data out (egress is billed); anyone expecting a hosting-style support desk.
Using the free e2-micro well
- Create the instance in us-west1, us-central1 or us-east1, machine type e2-micro, standard persistent disk of 30 GB or less. Any other region or disk type is billed.
- Set a billing budget and alert in the console before anything else, so a mistake emails you rather than surprising you.
- Watch egress. The free allowance is 1 GB a month from North America; a site serving images to the public can pass that. Put Cloudflare or another cache in front if traffic grows.
- Release external IP addresses you stop using and check Google's network pricing page for how reserved addresses are charged.
- Harden it like any server: SSH keys through OS Login or metadata, a firewall rule that opens only the ports you serve, automatic updates, and a backup outside the project (disk snapshots are priced separately on Google's disk pricing page).
Against a paid VPS
| Option | Monthly | What you get | US locations | Billing shape |
|---|---|---|---|---|
| Google Cloud Free Tier e2-micro | $0 | Shared-core micro VM, 30 GB disk, 1 GB egress | Oregon, Iowa, South Carolina | Free within limits; everything else itemised |
| Google Cloud paid VM | Calculator | Any machine type | Nine regions | Per second; VM + disk + IP + egress |
| InterServer 1 slice | $3 | 1 core, 2 GB, 40 GB SSD, 2 TB | New York City, Los Angeles, Dallas | One monthly price |
| OVHcloud VPS-1 | $5.35 | 2 vCores, 4 GB, 40 GB NVMe, unlimited | Virginia, Oregon | One monthly price |
| Vultr vc2-1c-1gb | $5 | 1 vCPU, 1 GB, 25 GB, 1 TB | Nine regions | Hourly, one plan price |
| Oracle Cloud Free Tier | $0 | 2 Arm OCPUs, 12 GB (documented equivalent), 200 GB, 10 TB egress | Ashburn, Phoenix, San Jose, Chicago | Free within limits; idle instances reclaimed |
Between the two hyperscaler free tiers, Oracle's is far larger; Google's is simpler to keep (no idle reclamation rule) and smaller. Against the paid hosts, the comparison is about the shape of the bill: a $3 or $5 plan is a known number, a Compute Engine VM is a sum.
Verdict and rating
Compute Engine is a first-class cloud platform with a genuine free server and nine US regions, and none of that makes it a good VPS for most people who type "google cloud vps" into a search box. It has no plan price, its costs are itemised, and its strengths (regions, services, discounts for commitment) reward people who already know what they are doing on Google Cloud. Rating as a VPS: 3.8 out of 5. Credit for the documented Free Tier, the $300 trial, nine US regions and per-second billing after the first minute; held down by the absence of a plan price, script-rendered pricing pages, egress and disk line items that catch beginners, and a console built for something much larger than a server.
Choose Google Cloud if you are on it already, learning it, or need one of its nine US regions and understand the bill. Choose a fixed-price VPS if you want a server at a price: InterServer for $3, OVHcloud for $5.35, Vultr for $5 hourly. Choose Oracle's free tier if free and larger matters more than simple.