Side-by-side comparison of AWS, GCP, Azure, and DigitalOcean free tiers in 2026. Compare always-free compute, databases, serverless, storage, startup credits, and hidden costs across all 4 major clouds.

Cloud Free Tier Comparison 2026

Published 2026-03-31 · Reviewed 2026-10-21 · Figures compiled 2026-03-31, last checked 2026-10-21 · 43 of 97 figures in the tables below come from our records for 1,498 developer tools · 4 cloud providers compared

📂 Browse all 15 Cloud IaaS services with free tiers → Cloud IaaS Category Hub
4
Clouds Compared
GCP
Free Services
$5–300
Trial Credits Range
Up to $350K
Startup Program Credits

Quick verdict: Of these four clouds, GCP is the only one with a permanent free VM (e2-micro), with always-free limits of Cloud Run 2M req/mo and BigQuery 1 TiB. Oracle Cloud, not compared here, also has Always Free VMs. AWS has a service catalog and serverless stack (Lambda + DynamoDB). Azure has Active Directory, Cosmos DB lifetime free tier, and the .NET ecosystem. DigitalOcean doesn't compete on free tiers but offers paid Droplets ($4/mo).

The catch: Every cloud hides costs differently. AWS charges for data transfer and NAT gateways. GCP charges for egress and has confusing Firestore pricing tiers. Azure has no spending cap on pay-as-you-go. DigitalOcean has minimal free services but the fewest gotchas. We compare all of them below.

Jump to section

  1. Free Trial Credits
  2. Always-Free Compute
  3. Always-Free Databases
  4. Serverless Functions
  5. Storage & CDN
  6. Startup Credit Programs
  7. By Use Case
  8. Hidden Costs Comparison
  9. Pricing Change Timeline
  10. Data Source

Free Trial Credits

Every major cloud offers trial credits to new accounts. The amounts, durations, and restrictions vary significantly.

Provider Credit Amount Duration Restrictions Credit Card Required
AWS CHANGED NOV 7 $100 + up to $100 Source ↗ 6 months (Free plan) New accounts only; the Free plan closes at 6 months or when the credits run out, and AWS erases the account 90 days later unless you upgrade No for most new customers on the new sign-up, which AWS is still rolling out; a card is required on the advanced sign-up
GCP No record $300 90 days New accounts only: never a paying user of Google Cloud, Google Maps Platform or Firebase; no GPUs during the trial Yes
Azure CHANGED NOV 19 Source ↗ $200 30 days Shorter window than GCP; transitions to pay-as-you-go Yes
DigitalOcean CHANGED NOV 12 Source ↗ $5 90 days New accounts only Yes
GCP offers the most generous trial: $300 over 90 days vs Azure's $200/30 days. AWS gives new accounts $100 in credits and up to $100 more for trying key services, on a Free plan that closes after 6 months or when the credits run out. DigitalOcean gives new accounts a $5 credit for 90 days. GCP, Azure and DigitalOcean require a credit card. None of the AWS, GCP or Azure trials charges that card when its credit runs out unless you upgrade: Google closes the Free Trial billing account, AWS closes the Free plan account, and Azure disables the subscription.

Always-Free Compute

Persistent compute is the most valuable free tier category.

Provider VM / Instance Limits Duration
AWS CHANGED NOV 7 Source ↗ EC2 No free hours; paid from Free plan credits (up to $200) Free plan: 6 months
GCP Source ↗ e2-micro VM 2 shared vCPU, 1 GB RAM, 30 GB disk, us-* regions Always free
Azure CHANGED NOV 19 Source ↗ B2pts v2 / B2ats v2 VMs 750 hrs/mo each, 2 vCPU, 1 GiB RAM 12 months only
DigitalOcean CHANGED NOV 12 Source ↗ No free compute Cheapest: $4/mo Droplet (512 MB RAM) Paid only
GCP is the only provider of the four with a permanent free VM. AWS gives new accounts no free VM hours, with EC2 paid from the Free plan's credits, and the plan closes after 6 months unless upgraded. Azure's free VM hours last 12 months for accounts that move to pay-as-you-go within 30 days, and VMs still running after 12 months are billed at pay-as-you-go rates. If you need a persistent server that costs nothing, GCP's e2-micro is the only option among the Big Four. DigitalOcean doesn't offer any free compute but starts at just $4/mo.

Always-Free Databases

Free managed databases are critical for side projects. The offerings vary dramatically between providers.

Provider Database Type Free Limits Duration
AWS CHANGED NOV 7 DynamoDB NoSQL (key-value) 25 GB, 25 WCU/RCU Source ↗ Always free
AWS CHANGED NOV 7 Source ↗ RDS (MySQL/PostgreSQL) Relational No allowance of its own: paid from the Free plan's credits (up to $200) Free plan, up to 6 months
AWS CHANGED NOV 7 Aurora PostgreSQL Serverless Relational (serverless) Up to 4 ACUs and 1 GiB per cluster, paid from the Free plan's credits Source ↗ Free plan, up to 6 months
GCP No record Firestore NoSQL (document) 1 GiB storage, 50K reads/day, 20K writes/day Always free
GCP No record BigQuery Data warehouse 1 TiB queries/month, 10 GB storage Always free
Azure CHANGED NOV 19 Source ↗ Cosmos DB Multi-model NoSQL 1,000 RU/s, 25 GB storage Always free
Azure CHANGED NOV 19 Source ↗ SQL Database Relational Up to 10 serverless databases, each 100K vCore seconds/mo and 32 GB Always free
Azure CHANGED NOV 19 Source ↗ Database for PostgreSQL Relational 750 hrs/mo Flexible Server B1MS, 32 GB storage, 32 GB backup 12 months
Azure CHANGED NOV 19 Source ↗ Database for MySQL Relational 750 hrs/mo Flexible Server B1MS, 32 GB storage, 32 GB backup 12 months
DigitalOcean CHANGED NOV 12 Source ↗ No free managed databases — cheapest: $15/mo for managed PostgreSQL/MySQL
AWS, GCP and Azure each have a managed database that stays free with no time limit. AWS DynamoDB has 25 GB storage and 25 WCU/RCU. GCP Firestore has 1 GiB storage and 50K reads and 20K writes a day; BigQuery has 1 TiB of queries a month and 10 GB storage. Azure Cosmos DB has 1,000 RU/s and 25 GB storage; Azure SQL Database has up to 10 serverless databases, each 100K vCore seconds a month and 32 GB. AWS RDS and Aurora PostgreSQL serverless are paid from the Free plan's credits for up to 6 months. Azure Database for PostgreSQL and MySQL have 750 free hours a month for 12 months. DigitalOcean has no free managed database.

Serverless Functions

Serverless compute is where free tiers shine — you only pay for what you use, and the free tiers are generous.

Provider Service Free Requests Free Compute Duration
AWS CHANGED NOV 7 Lambda 1M requests/mo Source ↗ 400K GB-seconds Always free
GCP No record Cloud Functions 2M invocations/mo 400K GB-seconds, 200K GHz-seconds Always free
GCP No record Cloud Run 2M requests/mo 180K vCPU-seconds, 360K GiB-seconds Always free
Azure CHANGED NOV 19 Source ↗ Functions 1M executions/mo 400K GB-seconds Always free
DigitalOcean CHANGED NOV 12 Source ↗ Functions No separate request quota 90K GiB-seconds Every month (no end date stated)
GCP leads with 2M invocations/month on Cloud Functions plus 2M req/mo on Cloud Run (container-based serverless). AWS Lambda (1M req) has the best ecosystem integration — pair it with DynamoDB and API Gateway for a fully serverless backend at $0. Azure matches AWS on limits. DigitalOcean Functions includes 90,000 GiB-seconds of compute a month per account, with no separate request quota.

Storage & CDN

Object storage and CDN are essential infrastructure. All four providers offer some free storage, but with very different limits.

Provider Object Storage CDN / Data Transfer Duration
AWS CHANGED NOV 7 S3: no free storage (paid from credits) CloudFront: 1 TB transfer, 10M requests/mo CloudFront always free; S3 from credits
GCP No record Cloud Storage: 5 GB Standard in us-east1, us-west1 or us-central1 100 GB/mo free egress to anywhere except China and Australia, including Europe; Cloud CDN not free Always free (storage)
Azure CHANGED NOV 19 Source ↗ Blob Storage: 5 GB LRS hot Azure CDN not free-tier; first 100 GB/mo outbound free from North America and Europe 12 months (Blob Storage)
DigitalOcean CHANGED NOV 12 Source ↗ Spaces: $5/mo (250 GB + CDN) Included with Spaces; no free tier Paid only
For free storage, consider alternatives: Cloudflare R2 (10 GB, zero egress fees) and Supabase (1 GB storage) often beat the Big Four for developer-scale storage. CloudFront is always free up to 1 TB of data transfer out and 10,000,000 requests a month. S3 is paid from the Free plan credits, which last up to 6 months.

Startup Credit Programs

All four clouds offer startup credit programs, but eligibility requirements and credit amounts vary significantly. See our complete startup credits guide for full details.

Provider Program Max Credits Duration Key Requirement
AWS CHANGED NOV 7 Activate Up to $200K Source ↗ — Activate Provider Org ID (Portfolio)
GCP No record Google for Startups Up to $350K 1–2 years VC funding, pre-seed to Series A
Azure CHANGED NOV 19 Source ↗ Microsoft for Startups Up to $150K 90 days to 2 years No funding requirement (easiest to qualify)
DigitalOcean CHANGED NOV 12 Source ↗ DigitalOcean Startups Amount varies (up to $10,000 a month) 12 months Not accepting new applications: paused until early 2027
Microsoft for Startups needs no investor: B2B tech startups start at $200 and can reach $150K with Azure usage. GCP offers up to $350K to AI-first startups and needs VC funding. AWS Activate Portfolio needs an Activate Provider Org ID.

By Use Case

When to Pick Each Cloud

Side project / hobby → GCP

GCP's e2-micro VM is the only permanent free VM among these four clouds. Oracle Cloud, not compared here, also has Always Free VMs. Cloud Run's 2M req/mo and Firestore give you a complete stack at $0 indefinitely. Read the full GCP guide →

Serverless backend → AWS

Lambda + DynamoDB + API Gateway is the gold standard for serverless. 1M requests/month + 25 GB always-free database. Nothing else matches this ecosystem. Read the full AWS guide →

Startup (easiest qualification) → Azure

Microsoft for Startups needs no investor. B2B tech startups can reach $150K in credits with Azure usage. Azure's Cosmos DB and SQL Database both stay free with no time limit. Read the full Azure guide →

Startup (largest credits) → GCP

Google for Startups offers up to $350K to AI-first startups. Its Scale tier needs VC funding; its $2K Start tier needs none.

Simple VPS / paid hosting → DigitalOcean

If you need predictable pricing, clean docs, and a simple UI, DO's $4/mo Droplets beat the complexity of AWS/GCP/Azure. Per-second billing means you only pay for uptime. Read the full DigitalOcean guide →

Enterprise / Microsoft ecosystem → Azure

Active Directory (50K objects always free), .NET native support, seamless Office 365 integration. Azure DevOps (5 users, unlimited repos) makes it a natural fit for Microsoft shops.

Hidden Costs Comparison

Every cloud has surprise costs that catch new users. Here's what to watch for on each provider.

AWS Most gotchas CHANGED NOV 7 Source ↗

Data transfer: $0.09/GB after 100 GB free. NAT Gateway: $32+/mo if Lambda needs VPC internet. Public IPv4: $0.005/hr ($3.60/mo) whether in use or idle. EBS on stopped instances: You pay for disk even when EC2 is stopped. Free plan closure: nothing is charged to your card on the Free plan; the account closes at 6 months or when credits run out, and content is deleted after 90 days unless you upgrade to the Paid plan.

GCP Moderate gotchas

Egress charges: $0.12/GB to internet past the free allowance (100 GB a month from Cloud Storage, 1 GB from Compute Engine), higher than AWS. Firestore pricing confusion: Native mode vs Datastore mode have different pricing and limits. Region restrictions: Free e2-micro VM only in us-west1, us-central1, us-east1. Cloud SQL not free: Managed PostgreSQL/MySQL starts at $7/mo — use Firestore or an external DB.

Azure CHANGED NOV 19 Source ↗

Spending limit: the free account's spending limit is on by default, so your card is not charged; at 30 days or when the $200 credit runs out, services are disabled unless you upgrade. Upgrading to pay-as-you-go removes the limit, and from then on there is no automatic stop. Log Analytics ingestion: 5 GB/mo free, then $2.76/GB — logging can cost more than compute. App Service F1 limits: 60 CPU-min/day with 1 GB RAM — apps sleep after the quota. VM deallocation: You must "deallocate" (not just "stop") VMs to stop charges.

DigitalOcean Fewest gotchas CHANGED NOV 12 Source ↗

Minimal free tier: The biggest "gotcha" is that there's almost nothing free — but what you do pay for is predictable. Bandwidth overage: $0.01/GB beyond your Droplet's allocation (much cheaper than AWS/GCP). Backups: 20% surcharge if enabled. Reserved IPs: Free when assigned. Unassigned IPv4 costs $5/month.

Pricing Change Timeline

Recent pricing changes we've tracked across all 4 cloud providers. See the full timeline for all 569 tracked changes.

Date Provider Change Impact
effective Nov 19, 2026 Azure Azure OpenAI retires o1 (version 2024-12-17), o1-pro (2025-03-19), o3 (2025-04-16), o3-deep-research (2025-06-26), o3-mini (2025-01-31), o3-pro (2025-06-10) and o4-mini (2025-04-16) on November 19, 2026. These models are deprecated, so new customers cannot deploy them. After that date a request to a retired model returns HTTP 410 Gone. Microsoft names gpt-5.6-sol as the replacement for o1, o1-pro, o3, o3-deep-research and o3-pro, and gpt-5.6-terra for o3-mini and o4-mini. Microsoft upgrades Global Standard, Data Zone Standard and Standard deployments to the named replacement where an upgrade is supported, and does not upgrade Provisioned deployments. Microsoft Foundry also retires Llama-4-Maverick-17B-128E-Instruct-FP8 that day, with no replacement named. Source ↗ MEDIUM
effective Nov 12, 2026 DigitalOcean DigitalOcean Managed Databases keep running. PostgreSQL 14 reached end of life on DigitalOcean on November 12, 2026. From that date DigitalOcean upgrades the remaining PostgreSQL 14 clusters to a supported version outside each cluster's maintenance window. Source ↗ MEDIUM
effective Nov 7, 2026 AWS Amazon OpenSearch Service charges an Extended Support surcharge equal to the instance price on every domain still running Elasticsearch 1.5, 2.3, 5.1, 5.3, 5.5, 6.0, 6.2, 6.3, 6.4, 6.5, 6.7, 7.1, 7.4, 7.7 or 7.8, or OpenSearch 1.0, 1.1, 1.2, 2.3, 2.5, 2.7 or 2.9 from November 7, 2026. The surcharge doubles the instance cost. Storage costs are not affected. Before November 7, 2026 these OpenSearch Service domains paid $0.0065 per Normalized Instance Hour (NIH) in US East (N. Virginia). Amazon OpenSearch Service's example: an m7g.medium.search instance at $0.068 an hour on demand costs $1.632 a day. The surcharge adds another $1.632 a day. The surcharge applies automatically and stops when the domain is upgraded to a supported version. This rate applies until November 7, 2027. Elasticsearch 5.6 domains still pay $0.0065 per NIH. Elasticsearch 6.8, 7.9, 7.10 and OpenSearch 1.3, 2.11, 2.13, 2.15, 2.17 and 2.19 pay no surcharge before November 7, 2027. Source ↗ MEDIUM
effective Oct 30, 2026 Google Cloud Run Google decommissioned the Node.js 20 runtime of Cloud Functions for Firebase and Cloud Run functions on October 30, 2026. Since then, functions on Node.js 20 cannot be created or updated. The Firebase CLI refuses to deploy them with the error "Runtime Node.js 20 was decommissioned on 2026-10-30". Functions already deployed on Node.js 20 can keep running, but Google says functions that stay on a decommissioned runtime may be disabled. To deploy again, move the functions to Node.js 22 or Node.js 24. Source ↗ MEDIUM
effective Oct 7, 2026 AWS AWS Proton reaches end of support on 2026-10-07, when its console and resources stop being accessible. AWS: "Your deployed CloudFormation stacks and the resources they manage will remain intact and continue to function." New customers could not sign up after 2025-10-07. Source ↗ MEDIUM
effective Sep 30, 2026 AWS AWS App Mesh reached end of support on 2026-09-30. AWS: "After September 30, 2026, you will no longer be able to access the AWS App Mesh console or AWS App Mesh resources." AWS points App Mesh users to Amazon ECS Service Connect. Source ↗ MEDIUM
discovered Aug 28, 2026 · effective date unknown Amazon ECR Public The free tier for public repositories is now 50 GB/month, up from 500 MB/month. The anonymous data transfer limit is 500 GB/month, and with an AWS account, it's 5 TB/month. Unconfirmed. We could not check this change against an archived copy of Amazon ECR Public's page, so it does not count toward the rating. Source ↗ LOW
effective Jul 10, 2026 Amazon Kiro Kiro added a Pro Max plan at $100 per user a month with 5,000 credits, between Pro+ and Power. It first appears on kiro.dev/pricing between the 2026-06-03 and 2026-07-10 captures. Source ↗ LOW
effective Jun 30, 2026 AWS Fargate platform version 1.3.0 reached end of support on June 30, 2026. AWS blocked new tasks and services on it from June 15 and said it would terminate the tasks still running on it on June 30. Platform version 1.4.0 replaces it. Source ↗ MEDIUM
effective Jun 14, 2026 AWS Activate AWS raised Activate Portfolio from up to $100,000 to up to $200,000 in credits. aws.amazon.com/startups/credits/ said "Up to $100,000 USD AWS Activate Credits" in the Internet Archive's capture of 2026-05-31 and "Up to $200,000 USD in Activate Credits" in the capture of 2026-06-14. Source ↗ MEDIUM
effective Jun 3, 2026 Amazon Kiro Kiro stopped giving new users 500 bonus credits on sign-up, usable within 30 days, and now credits $20 toward the first paid plan instead. The change falls between the 2026-05-02 and 2026-06-03 captures of kiro.dev/pricing. Source ↗ MEDIUM
effective May 13, 2026 DigitalOcean As of 2026-05-13, DigitalOcean's startup credits exclude Dedicated and Serverless Inference, third-party AI models, Paperspace Machines, Cloudways and Bare Metal GPUs as well as GPU Droplets and H100 GPU products, the two exclusions its page stated before. The page also now puts the monthly credit limit at $10,000; its April capture mentioned a monthly limit without an amount. Source ↗ MEDIUM

Upcoming Changes

These are announced changes that have not taken effect yet, listed soonest first.

Date Vendor Change Impact
effective Dec 7, 2026 AWS Infrastructure Composer The standalone AWS Infrastructure Composer console shuts down on December 7, 2026. New customers have not been able to sign up since October 29, 2026. Existing customers can use the console until December 7, 2026. The visual editor remains in the AWS Toolkit for Visual Studio Code. CloudFormation templates and stacks continue to work normally. Source ↗ MEDIUM
effective Dec 15, 2026 Azure Azure OpenAI retires whisper, tts and tts-hd (version 001) on December 15, 2026. After that date every request to them returns HTTP 410 Gone. Microsoft names no replacement. OpenAI's own API retires whisper-1 later, in February 2027, and tts-1 and tts-1-hd later, in January 2027. Those are OpenAI's dates, and Azure OpenAI's are Microsoft's. Source ↗ MEDIUM
effective Dec 15, 2026 Azure Azure OpenAI retires gpt-realtime-mini version 2025-12-15 on December 15, 2026. gpt-realtime-mini version 2025-10-06 retires later on Azure OpenAI, in April 2027, and is not covered by this date. Microsoft names no replacement. After that date requests to version 2025-12-15 return HTTP 410 Gone. OpenAI's own API retires gpt-realtime-mini later, on January 20, and that is OpenAI's date, not Azure's. Source ↗ MEDIUM
effective Jan 1, 2027 Google Cloud SQL for MySQL From January 1, 2027, Google charges extended support on every Cloud SQL for MySQL 8.0 instance, on top of the regular instance price. Cloud SQL enrolls them automatically. MySQL 8.4 or later instances are not affected. In Iowa (us-central1), Cloud SQL extended support for MySQL 8.0 costs $0.07 per vCPU-hour in years 1 and 2 and twice that in year 3. High-availability instances pay twice the per-vCPU rate. On shared-core instances the extended support charge is $0.018 an hour for db-f1-micro and $0.035 for db-g1-small. Committed use discounts do not apply. The charge stops when the instance is upgraded. On July 1, 2029, Cloud SQL upgrades remaining MySQL 8.0 instances to the default major version automatically. Source ↗ MEDIUM
effective Jan 1, 2027 AWS AWS discontinues its Developer Support and Business Support plans on January 1, 2027. Accounts on either plan must opt in to Business Support+ before then. A Developer Support account that does not opt in is downgraded to Basic Support. Basic Support gives access to the Resource Center, Service Health Dashboard, Product FAQs and Discussion Forums at no charge. Business Support accounts are not moved to Business Support+ automatically. Business Support+ costs the greater of $29 a month per account or 9% of monthly AWS charges, falling in steps to 3% on larger bills. Neither plan has accepted new subscriptions since December 2, 2025. AWS emails each account 30 days before its plan changes. Enterprise On-Ramp also ends on January 1, 2027, and its customers are moved to Enterprise Support automatically. The three plans stay available in the AWS GovCloud (US) Region. Source ↗ MEDIUM
effective Jan 8, 2027 AWS Amazon Bedrock removes Claude Opus 4.1 on January 8, 2027. The date covers us-east-1, us-east-2 and us-west-2. Requests to it on Bedrock fail after that date. It has been Legacy on Bedrock since July 8, 2026. New customers cannot use it. Accounts that leave it unused for 15 days may lose access. Since October 8, 2026 it has been in public extended access. Bedrock says to expect higher prices set by Anthropic. Anthropic's own Claude API retired Claude Opus 4.1 on August 5, 2026. Bedrock's dates apply only to Bedrock. Bedrock lists Claude Opus 4.8, Claude Opus 5 and Claude Opus 5.5. Source ↗ LOW
effective Jan 14, 2027 Azure Azure OpenAI retires gpt-4o version 2024-05-13 on January 14, 2027. gpt-4o versions 2024-08-06 and 2024-11-20 and gpt-4o-mini version 2024-07-18 retire later on Azure OpenAI, on April 14, 2027, in all active deployments including Global Standard. Microsoft upgrades Global Standard and Data Zone Standard deployments of version 2024-05-13 to gpt-5.1 version 2025-11-13 that day. Provisioned deployments of version 2024-05-13 are not upgraded. Create a gpt-5.1 deployment and move traffic before the date. Microsoft does not promise automatic upgrades for Global Batch deployments of version 2024-05-13. After that date, requests to version 2024-05-13 return HTTP 410 Gone. Source ↗ MEDIUM
effective Feb 1, 2027 AWS Amazon ElastiCache charges an Extended Support premium on every cache still running Redis OSS 6 starting February 1, 2027. Standard support for Redis OSS 6 ends January 31, 2027. Caches move to Extended Support automatically. The premium is 80% of the on-demand node price in years 1 and 2 and 160% in year 3. Reserved node discounts do not apply to the premium. AWS's example: a cache.m5.large node in US East (Ohio) costs $0.156 an hour plus $0.1248 an hour. The premium stops when the cache is upgraded to Valkey or Redis OSS 7 or later, or deleted. Source ↗ MEDIUM
effective Feb 1, 2027 Google Cloud SQL for PostgreSQL From February 1, 2027, Google charges extended support on every Cloud SQL for PostgreSQL 14 instance, on top of the regular instance price. Cloud SQL enrolls them automatically. Databases on PostgreSQL 15 or later are not affected. In Iowa (us-central1), Cloud SQL extended support costs $0.07 per vCPU-hour in years 1 and 2 ($0.14 for HA vCPUs), $0.14 per vCPU-hour in year 3, and $0.018 an hour on a db-f1-micro instance. Committed use discounts do not apply. Read replicas pay the same rate. There is no setting to turn it off. The charge stops when the instance is upgraded. On February 1, 2030, Cloud SQL upgrades remaining PostgreSQL 14 instances to the default major version automatically. Source ↗ MEDIUM
effective Feb 1, 2027 Azure Azure Database for PostgreSQL flexible server 14 leaves standard support on January 31, 2027. From February 1, 2027 every server still on PostgreSQL 14 is enrolled in Extended Support automatically. Servers on PostgreSQL 15 or later are not affected. There is no opt-out. Charges stop only when the server is upgraded to a supported version. Azure charges $0.07 per vCore-hour in East US in years 1 and 2. Year 3 is charged at twice the year 1 and 2 rate. Only running servers are charged. Stopped servers are not charged. Extended Support for PostgreSQL 14 ends November 11, 2029. Source ↗ MEDIUM
effective Feb 1, 2027 Azure Azure charges Extended Support on every Azure Database for MySQL flexible server 8.0 server starting February 1, 2027, after standard support ends on January 31, 2027. Azure enrolls them automatically. Servers on MySQL 8.4 or later are not affected. Azure charges $0.07 per vCore-hour in East US in years 1 and 2, and twice that in year 3. Stopped servers are not charged for Extended Support. There is no opt-out: the charge stops when the server is upgraded to a supported major version. Extended Support for MySQL 8.0 ends May 31, 2029. Source ↗ MEDIUM
effective Feb 22, 2027 Azure Deployment Environments Azure Deployment Environments retires on February 22, 2027. Creating and deploying environments and other write operations are expected to be blocked on that date. Inventory, read, log and delete stay available for a limited cleanup period. Microsoft Dev Box retires later, in September 2028. Source ↗ MEDIUM
effective Mar 1, 2027 AWS On March 1, 2027, AWS charges for RDS Extended Support on Amazon RDS for PostgreSQL 14 and Aurora PostgreSQL 14 databases that are enrolled and still on version 14. Standard support for PostgreSQL 14 on RDS and Aurora ends February 28, 2027. Databases on PostgreSQL 15 or later are not affected. Each database's RDS Extended Support setting decides what happens: an enrolled PostgreSQL 14 database is charged, and a PostgreSQL 14 database with it disabled is upgraded to a supported version on or shortly after February 28, 2027. The AWS CLI, the RDS API and CloudFormation enable it by default, and the console does not select it for new databases. The charge stops when the database is upgraded to a version under standard support or deleted. For earlier versions AWS charges $0.10 per vCPU-hour in years 1 and 2 in US East (Ohio), and Aurora Serverless v2 on PostgreSQL 14 is $0.085 per ACU-hour in years 1 and 2. On the same date RDS for PostgreSQL 12 moves from $0.100 to $0.200 per vCPU-hour in US East (Ohio). Source ↗ MEDIUM
effective Mar 30, 2027 AWS Amazon Bedrock removes 26 models on March 30, 2027. DeepSeek: DeepSeek-R1, DeepSeek-V3.1. Google: Gemma 3 4B IT, Gemma 3 12B IT, Gemma 3 27B PT. Meta: Llama 3 8B Instruct, Llama 3 70B Instruct, Llama 3.1 8B Instruct, Llama 3.1 70B Instruct, Llama 3.3 70B Instruct, Llama 4 Maverick 17B Instruct, Llama 4 Scout 17B Instruct. MiniMax: MiniMax M2, MiniMax M2.1. Mistral AI: Devstral 2 123B, Mistral 7B Instruct, Mixtral 8x7B Instruct, Voxtral Mini 3B 2507, Voxtral Small 24B 2507. Moonshot AI: Kimi K2 Thinking. NVIDIA: NVIDIA Nemotron Nano 9B v2, NVIDIA Nemotron Nano 12B v2 VL BF16. Qwen: Qwen3-Coder-30B-A3B-Instruct, Qwen3 Coder 480B A35B Instruct. Z.AI: GLM 4.7, GLM 4.7 Flash. They have been Legacy on Bedrock since September 30, 2026. New customers cannot use them. Accounts that leave one unused for 15 days may lose access. No new Provisioned Throughput can be created. Bedrock moves them to public extended access before the end date, with higher prices set by the provider. It has not announced when. After March 30, 2027 requests to them on Bedrock fail. Bedrock does not migrate applications automatically. The date covers the Regions Bedrock lists for each model, us-west-2 among them for all 26. A model can stay available in other Regions. Bedrock names no replacement. Its model cards list newer models: DeepSeek V3.2, GLM 5, Gemma 4, Kimi K3, MiniMax M2.5 and Mistral Large 3. Source ↗ MEDIUM
effective Mar 31, 2027 Azure Microsoft retires two tiers of Azure Cache for Redis on March 31, 2027: Enterprise and Enterprise Flash. The Basic, Standard and Premium tiers retire later, on September 30, 2028. From April 1, 2027 every remaining Enterprise cache and every remaining Enterprise Flash cache is disabled. Creating new Enterprise or Enterprise Flash caches has been blocked since April 1, 2026. Reservations for both tiers are supported until March 30, 2027. Microsoft's replacement is Azure Managed Redis. Applications must switch to the new cache's hostname and access credentials. Azure Managed Redis is clustered by default, so applications should check that their client library works with a clustered cache. New customers cannot create Basic, Standard or Premium caches either. Since April 1, 2026, in Azure's public cloud, only a tenant that had any Azure Cache for Redis instance before that date can create them. Source ↗ MEDIUM
effective Apr 4, 2027 Google Cloud Run Google decommissions the Python 3.10 runtime of Cloud Functions for Firebase and Cloud Run functions on April 4, 2027. From that date, functions on Python 3.10 cannot be created or updated. Google says functions that stay on a decommissioned runtime may be disabled. Python 3.10 has been deprecated since October 4, 2026. Until April 4, 2027, functions on Python 3.10 can still be created and updated. Move them to Python 3.11 or a later Python runtime before then. The Node.js 20 runtime of these products was already decommissioned on October 30, 2026. Node.js 20 functions can no longer be deployed. The Firebase CLI refuses with the error "Runtime Node.js 20 was decommissioned on 2026-10-30". Source ↗ MEDIUM
effective Apr 8, 2027 AWS Amazon Bedrock removes Claude Sonnet 4.5 on April 8, 2027. The date covers its commercial AWS Regions. In the AWS GovCloud (US) Regions it is later in April 2027. Requests to it on Bedrock fail after that date. Anthropic's own Claude API retires the model at the end of November 2026. Bedrock says only its own dates apply to Bedrock usage. It has been Legacy on Bedrock since October 8, 2026. New customers cannot use it. Accounts that leave it unused for 15 days may lose access. From January 2027 it is in public extended access. Bedrock says to expect higher prices set by Anthropic. Bedrock lists Claude Sonnet 5 and Claude Sonnet 5.5. Source ↗ MEDIUM
effective Apr 14, 2027 Azure Azure OpenAI retires gpt-4o versions 2024-08-06 and 2024-11-20, gpt-4o-mini version 2024-07-18, and gpt-4.1, gpt-4.1-mini and gpt-4.1-nano versions 2025-04-14 on April 14, 2027. Regional Standard deployments that already retired stay retired. Microsoft names gpt-5.1 as the replacement for gpt-4o. No replacement is named for the others. Fine-tuned deployments of these models have later dates on a separate Microsoft schedule. OpenAI's own API shuts down gpt-4o, gpt-4o-mini, gpt-4.1 and gpt-4.1-mini earlier, in January 2027. That is OpenAI's date, not Azure's. Source ↗ MEDIUM
effective Jun 2, 2027 Azure Fluid Relay Azure Fluid Relay retires on June 2, 2027. It can be used until June 1, 2027. The Fluid Framework remains open source. Replace it with a self-hosted Fluid service you run yourself. Source ↗ MEDIUM
effective Jun 16, 2027 Azure Azure OpenAI retires gpt-image-1.5 version 2025-12-16 on June 16, 2027. Microsoft names no replacement. After that date requests to it return HTTP 410 Gone. OpenAI's own API retires gpt-image-1.5 earlier, on December 1, and that is OpenAI's date, not Azure's. Source ↗ MEDIUM
effective Jun 30, 2027 Google Cloud Deployment Manager Google Cloud Deployment Manager is turned down after June 30, 2027. Support ended April 1, 2026. Since June 30, 2026, new users cannot enable the Deployment Manager API or create a first deployment. Existing deployments can use Deployment Manager until June 30, 2027. After that date, Deployment Manager can no longer be used. Resources it created continue to run and are managed with standard Google Cloud tools. Google recommends Infrastructure Manager. Source ↗ MEDIUM
effective Aug 31, 2027 AWS AWS Lambda blocks creating new functions on its deprecated runtimes from July 29, 2027. It blocks updating the code and configuration of existing functions from August 31, 2027. AWS is delaying these blocks beyond its usual 30 and 60 days after deprecation. Functions on .NET 8, Python 3.10 and the other deprecated runtimes can still be created and updated until those dates through the AWS CLI, AWS SAM or CloudFormation, not the Lambda console. After both dates, existing functions can still be invoked and can still be switched to a supported runtime. Deprecated runtimes include Node.js 16, 18 and 20; Python 3.8, 3.9 and 3.10; Ruby 3.2; .NET 6 and 8; and provided.al2. Python 3.10 was deprecated on October 31, 2026 and .NET 8 on November 10, 2026. These runtimes are deprecated next and get the same two dates: Ruby 3.3 on March 31, 2027, Node.js 22 on May 30, 2027, and Python 3.11 and Java 8, 11 and 17 on Amazon Linux 2 on June 30, 2027. Older runtimes are the exception: functions on Node.js 14, Python 3.7, Ruby 2.7, Go 1.x, Java 8 on Amazon Linux and provided can no longer be created since 2024 and can no longer be updated from August 31, 2027. Source ↗ MEDIUM
effective Sep 14, 2027 Google Cloud Video Intelligence API Google Cloud Video Intelligence API shuts down on September 14, 2027. It has been deprecated and unsupported since September 14, 2026, and can be used until its shutdown. Google recommends migrating to its Gemini family of models. Source ↗ MEDIUM
effective Sep 29, 2027 Functions on Azure Container Apps V1 Functions on Azure Container Apps V1 retires on September 29, 2027. After that date V1 function apps stop running and stop processing requests and triggers. Migrate to Functions on Azure Container Apps V2, a native Container App with kind=functionapp, using the same container image and no function code changes in the standard path. Azure Functions and Azure Container Apps keep running. Source ↗ MEDIUM
effective Sep 30, 2027 Amazon DevOps Guru Amazon DevOps Guru shuts down on September 30, 2027. New customers have not been able to sign up since October 29, 2026. Existing customers can use it until September 30, 2027. After that date, the console and API become unavailable, past insights are no longer retrievable, and stacks declaring AWS::DevOpsGuru::ResourceCollection or AWS::DevOpsGuru::NotificationChannel fail to create or update. Running workloads are not interrupted. AWS recommends Amazon CloudWatch and Amazon DevOps Agent. Source ↗ MEDIUM
effective Nov 7, 2027 AWS After November 7, 2027, Amazon OpenSearch Service isolates every domain still running Elasticsearch 1.5, 2.3, 5.1, 5.3, 5.5, 6.0, 6.2, 6.3, 6.4, 6.5, 6.7, 7.1, 7.4, 7.7 or 7.8, or OpenSearch 1.0, 1.1, 1.2, 2.3, 2.5, 2.7 or 2.9. Isolated domains can no longer be accessed. AWS keeps their data for at least 30 days. Data must be restored into a new domain on a supported version. New domains cannot be created on these versions after that date. Since November 7, 2026, these domains have paid an Extended Support surcharge equal to their instance price, doubling the cost. Elasticsearch 1.5 and 2.3 domains cannot be upgraded in place. Upgrading before November 7, 2027 stops the surcharge and avoids isolation. Source ↗ MEDIUM
effective Sep 30, 2028 Azure Communication Services Azure Communication Services' standalone services retire on September 30, 2028. Retired services include Email, SMS, WhatsApp messaging, Chat, Rooms, number management, Job Router, Direct Routing and the UI Library SDKs. Customers without an ACS resource created before October 23, 2026 cannot acquire phone numbers for SMS or PSTN calling. Voice and video calling stay available after 2028 only with Microsoft Teams integrations, on new SDK major versions. Source ↗ HIGH
effective Sep 30, 2028 Azure Microsoft retires the Basic, Standard and Premium tiers of Azure Cache for Redis on September 30, 2028. From October 1, 2028 every remaining Basic, Standard or Premium cache is disabled. Since April 1, 2026 new customers in Azure's public cloud cannot create caches in these tiers. A tenant that had any Azure Cache for Redis instance before April 1, 2026 can keep creating them until the retirement. Reservations are supported until September 30, 2028. Microsoft's replacement is Azure Managed Redis. Applications must switch to the new cache's hostname and access key. Azure Managed Redis is clustered by default, so the client library must be set up for a clustered cache. Source ↗ MEDIUM

Data Source

Powered by AgentDeals. The tables on this page were compiled by hand from official cloud provider pricing pages and have not been re-checked since. We track pricing changes across all 4 major clouds. The pricing changes we track are updated continuously; the tables above are not.

Deep-dive guides: AWS · GCP · Azure · DigitalOcean · Databases

Query cloud pricing programmatically via our MCP tools — compare cloud services, track pricing changes, or plan your infrastructure stack from your AI coding assistant.

A source check reads each cited page for that service's name and a price. The figures in the tables above are from our own records, except for the services whose entry below dates them to a read of the vendor's own page.

Frequently Asked Questions

What is the best free cloud IaaS service in 2026?

We publish no ranking of these. Nothing we record measures popularity or generosity, so naming a best or a top few would be our preference rather than our data. We hold 15 Cloud IaaS services in our catalogue, each with the free tier terms. This page compares them on free tier limits, what each charges past them, and lock-in risk; the table above carries the figures side by side. Our ranking rule is published at /criteria.

Which cloud IaaS free tier is most generous?

We name no most generous free tier here, because generosity is not one quantity: the columns above measure different things and a tier that leads one trails another.

How do cloud IaaS free tiers compare on limits?

Each provider structures free tier limits differently — some cap storage, others cap requests or compute hours. Our comparison table provides exact numbers for each provider. Check the growth cost analysis section to understand what you'll pay when you exceed free tier limits.

Related Comparisons

Related Guides

Explore all 1,498 developer tool deals → Browse the full index or connect via MCP