CapacityLab
Console
← Back to blog

Hyperscaler field guide · July 18, 2026

AWS, GCP, Azure, or Cloudflare: how much cloud should one person operate?

The hyperscalers are not inherently wrong for a solo founder. The danger is assembling five individually cheap services whose billing, permissions, and failure modes no longer fit in one person’s head.

12 minute readDocumentedModeled

Method

What this comparison measures

  1. Compare approachable application surfaces, not every service in each cloud catalog.
  2. Model a small public container with a database, object storage, logs, and outbound traffic in a US and EU region.
  3. Count separately priced supporting services and distinguish a true spending limit from a notification budget.
  4. Show free grants as temporary or recurring and record what happens when each one ends.

Start with the smallest front door

AWS Lightsail bundles VM, disk, IP, DNS, monitoring, and transfer into a predictable monthly maximum. Google Cloud Run and Azure Container Apps instead meter active container resources and can scale to zero. Cloudflare Workers packages the runtime around requests and CPU time, with Containers available when a Worker is not enough.[1][4][6][8]

These are rational solopreneur products. The trouble begins when the first service silently requires a second for builds, a third for artifacts, a fourth for networking, and a fifth for logs. Each can remain inside its free allowance while the system becomes difficult to reason about.

The deliberately narrow entry point
CloudStart hereBest fitFirst complexity cliff
AWSLightsailPredictable always-on app or small VMMoving to EC2/VPC/RDS/CloudWatch pricing
GCPCloud RunBursty HTTP containerBuild, registry, networking and database SKUs
AzureContainer AppsEvent or HTTP containerSubscription, regions, Log Analytics and adjacent services
CloudflareWorkersEdge request processingD1 rows, R2 operations, Durable Objects and container meters

Free tier does not mean the same thing

Lightsail offers three free months on selected bundles, then charges the ordinary hourly rate up to the monthly cap. Stopped instances and databases continue to bill until deleted. This is a trial, not an always-free production tier.[1][2]

Cloud Run and Azure Container Apps publish recurring monthly grants. Both can scale to zero, but source builds, image storage, logs, databases, and networking sit outside the core compute grant. Cloudflare Workers Free has a daily request limit; the paid plan has a monthly minimum and usage meters.[4][6][8]

Azure’s free subscription has a real spending limit equal to the promotional credit. Once upgraded to pay-as-you-go, that custom hard limit is unavailable. Google Cloud budgets and AWS Budgets are primarily alerting tools; they should not be described as guaranteed kill switches.[7][5][3]

Protection against an accidental paid spikeEditorial score for a new account’s default path. Five means a documented hard stop; one means alerts without a general spending ceiling.
Protection against an accidental paid spikeEditorial score for a new account’s default path. Five means a documented hard stop; one means alerts without a general spending ceiling.Azure Free5 of 5Credit-sized spending limit until pay-as-you-go upgradeCloudflare Free5 of 5Hard product quotas; paid product behavior differsGCP free trial4 of 5Trial credit does not auto-charge; paid account removes that boundaryAWS Free Tier2 of 5Budgets alert; active resources can outlive the promotionPay-as-you-go cloud1 of 5Quotas and max instances are partial controls, not a bill ceilingof 5

The product-sprawl tax

A small application needs more than compute: build artifacts, domain and TLS, database, object storage, secrets, logs, and egress. The modeled count below asks how many separately metered products a founder must watch, not how many menu items the provider sells.

Cloudflare’s positioning feels unclear because it spans edge runtime, storage, SQL, queues, AI, browsers, and now containers. The unifying idea is a developer platform on Cloudflare’s network; the billing reality is still a set of separate meters. D1 rows read and written and R2 operation classes can matter even when egress is free.[8]

Separately metered products in a small production stackModeled count for app runtime, database, object storage, build/image storage, logs, and network. It measures billing surface, not implementation quality.
Separately metered products in a small production stackModeled count for app runtime, database, object storage, build/image storage, logs, and network. It measures billing surface, not implementation quality.AWS narrow stack6 metersLightsail reduces the count; a conventional AWS stack increases itGoogle Cloud7 metersRun, Build, Artifact Registry, database, storage, logging, networkAzure7 metersContainer Apps plus registry, data, storage, monitoring, networkCloudflare6 metersWorkers, D1, R2, logs, queues, container usage where neededmeters
Modeled monthly platform envelopeA small container, managed data, 10–1000 GB egress, and basic logs. This is a shape comparison; database choice and regional transfer dominate the exact invoice.
Modeled monthly platform envelopeA small container, managed data, 10–1000 GB egress, and basic logs. This is a shape comparison; database choice and regional transfer dominate the exact invoice.

A safe way to use a big cloud alone

Create one billing account and one production project or subscription. Pick one region. Refuse marketplace products during the first version. Put maximum instance counts on serverless compute, lifecycle rules on artifacts, retention on logs, and owner tags on everything.

Choose AWS when predictable bundled infrastructure or later catalog depth matters. Choose GCP for a clean container scale-to-zero path. Choose Azure when the product already lives in Microsoft’s identity and business ecosystem. Choose Cloudflare when global request processing and low egress are architectural advantages.

Source register

Specifications and prices change. The links make this snapshot auditable.

Sources and commercial facts were checked on 2026-07-18. Prices exclude tax unless the source says otherwise.

  1. Amazon Lightsail pricing ↗AWS · pricing
  2. Lightsail billing and account management ↗AWS · billing
  3. Control your AWS costs ↗AWS · billing
  4. Cloud Run pricing ↗Google Cloud · pricing
  5. Cloud Run cost optimization ↗Google Cloud · billing
  6. Azure Container Apps pricing ↗Microsoft Azure · pricing
  7. Azure spending limit ↗Microsoft · billing
  8. Workers pricing ↗Cloudflare · pricing