Amazon RDS Alternatives

Seven managed databases for teams leaving Amazon RDS, with the real entry price of each and the meters behind it.

The best Amazon RDS alternative depends on what you want to fix. For the closest like-for-like service on another cloud, Google Cloud SQL: MySQL, PostgreSQL and SQL Server, high availability and up to 35 days of point-in-time recovery. For a bill you can predict to the cent, DigitalOcean Managed Databases, from $15.15 a month. If your database is the backend of an app, Supabase; if it sits idle most of the day, Neon, which scales to zero. Aiven runs the same plans on six clouds, Azure Database for PostgreSQL fits a Microsoft shop, and Amazon Aurora is the move if you want to stay on AWS. For reference, the smallest RDS for PostgreSQL instance costs $13.98 a month with its 20 GiB minimum of storage. Below, how each alternative is billed, where it is weaker than RDS, and the traps that make a cheap database expensive.

Romain CochardCEO of Hack'celeration
Updated 20267alternatives compared5criteria each2026pricing checked

The ranking is editorial: a sponsored placement is always flagged on its card, and no affiliate link changes a score.

The honest take

Why teams are leaving Amazon RDS

Amazon RDS keeps strong reviews: 4.7 out of 5 across 218 user ratings, with setup and backups praised again and again. Teams rarely leave because it fails. They leave because of how the bill is built, because it never sleeps, and because AWS keeps a few keys for itself. Here are the six reasons that come up most, each with the RDS fact behind it.

Six meters on one invoice

RDS bills DB instance hours, storage per GB-month, I/O requests on magnetic storage, provisioned IOPS whether you use them or not, backup storage and data transfer, plus the public IPv4 address. The entry point looks small: a db.t4g.micro for PostgreSQL costs $0.016 an hour in US East (N. Virginia), $11.68 for a 730-hour month, and gp3 storage adds $0.115 per GB-month on a 20 GiB minimum, so $13.98 a month. It grows line by line after that. In 2025, a cloud engineer with three to five years on it summed it up as reliable with pricey I/O, and another reviewer found it costly for high-performance workloads.

An idle database still bills

A stopped instance stops the instance-hour meter, but you still pay for provisioned storage, provisioned IOPS and backups. After seven consecutive days stopped, RDS starts the instance again on its own to apply maintenance, and the hours start billing again. A staging or preview database that sees a query twice a day costs you the whole month.

High availability doubles the line

Multi-AZ keeps a standby in a second Availability Zone, and you pay for it. The same db.t4g.micro goes from $0.016 to $0.032 an hour, and gp3 storage from $0.115 to $0.23 per GB-month: $27.96 a month instead of $13.98 with 20 GiB. Write I/O also doubles, since every write is copied to the standby.

Egress and cross-zone traffic

AWS gives 100 GB of data transfer out to the internet free each month, shared across all its services and regions. Past that, the first 10 TB cost $0.09 per GB in US East (N. Virginia), and an EC2 instance in another zone pays $0.01 per GB in each direction to reach the database. A startup based in Singapore wrote in 2024 that egress fees were what made RDS expensive, and that its move cut database costs by over 47%.

Postgres with a lid on it

The first user RDS creates belongs to the rds_superuser role, not the real PostgreSQL superuser, and RDS supports a curated set of over 85 PostgreSQL extensions. Running an old major version past its end of standard support adds Extended Support, billed per vCPU: $0.100 per vCPU-hour for the first two years in US East (Ohio), then $0.200. On a 2-vCPU instance that is $146 a month at the lower rate.

The free year is gone for new accounts

Accounts opened before mid-2025 kept the old offer: 750 hours a month of a single-AZ instance for 12 months, with 20 GB of storage and 20 GB of backups. Newer accounts get credits instead, $100 at sign-up and up to $100 more for trying AWS services, valid up to 12 months. A side project now pays from the first month once the credits run out.
1
Best like-for-like replacement on another cloud

Google Cloud SQL

4.5/5

Cloud SQL is Google's answer to RDS, and it maps onto it almost line for line. It runs MySQL, PostgreSQL and SQL Server, so a multi-engine RDS estate can move without changing database. It comes in two editions. Enterprise Plus keeps up to 35 days of point-in-time log retention and carries a 99.99% SLA that includes maintenance; Enterprise keeps up to 7 days and a 99.95% SLA.

The bill reads like an RDS bill, which is the good news and the bad news. Dedicated cores are billed per vCPU and per GiB of memory ($0.0413 per vCPU-hour and $0.007 per GiB-hour in Iowa for Enterprise), SSD storage costs $0.000232877 per GiB-hour (about $0.17 per GiB-month), and internet egress outside Cloud Interconnect costs $0.19 per GiB. Billing runs per second, so a short test costs almost nothing.

The entry point is a shared-core db-f1-micro at $0.0105 an hour, about $7.67 a month, below the $11.68 a month of the smallest RDS for PostgreSQL instance in US East (N. Virginia). Read the footnote first: shared-core machines are not covered by the Cloud SQL SLA, so production starts on a dedicated core. New customers get $300 in credits to run the migration pilot. If your whole stack is moving to Google, our page on leaving Google Cloud covers the reverse trip, worth reading before you commit.

Standout features
  • MySQL, PostgreSQL and SQL Server in one service
  • Up to 35 days of point-in-time recovery on Enterprise Plus
  • Per-second billing
+Pros
  • ✓Closest feature match to RDS on another cloud
  • ✓99.99% SLA including maintenance on Enterprise Plus
  • ✓$300 of credits to pilot the move
−Cons
  • ✗Bill has as many meters as RDS
  • ✗Shared-core entry is outside the SLA
  • ✗Internet egress at $0.19 per GiB
Google Cloud SQL vs Amazon RDS
CriterionGoogle Cloud SQLAmazon RDS
Entry price$0.0105/hr shared-core$0.016/hr db.t4g.micro
EnginesMySQL, PostgreSQL, SQL ServerSix engines incl. Oracle, Db2
Point-in-time recoveryUp to 35 days (Enterprise Plus)Up to 35 days
Internet egress$0.19/GiB100 GB free, then $0.09/GB
Verdict

The pick when you want RDS without AWS, engine for engine. If cutting the bill is the goal, look at DigitalOcean or Neon instead.

See Cloud SQL pricing → →
2
Best for a predictable monthly bill

DigitalOcean Managed Databases

4.4/5

DigitalOcean sells managed PostgreSQL, MySQL, MongoDB, Kafka, Valkey and OpenSearch at a flat monthly price per node. The smallest PostgreSQL node, 1 GiB of RAM and 1 vCPU with 10 to 30 GiB of storage, costs $15.15 a month, and storage beyond the base is $0.215 per GiB-month in 10 GiB steps. You read the figure on the pricing page and you get it on the invoice: no I/O line, no provisioned IOPS line.

High availability is a second node, not a multiplier you discover later, but on a new cluster it now sits on the Advanced Edition: in late 2026, new Standard Edition clusters can no longer add standby or read-only nodes. Advanced is listed at $135.75 a month for an 8 GiB, 2 vCPU General Purpose primary (older DigitalOcean pages still quote $130), and each standby bills at the primary's rate, so a two-node cluster costs $271.50 a month. Each cluster is limited to three nodes, and a standby can only run in the same region.

The limits are where RDS still wins. Point-in-time recovery covers the last 7 days only, against up to 35 on RDS. The 1 GiB plan accepts 22 backend connections, so plan on the built-in PgBouncer pools. You cannot use the superuser role. New Standard clusters also stop at 4 GiB of RAM, so anything larger goes to Advanced too. If you later outgrow it, our DigitalOcean switch guide lists where teams go next.

Standout features
  • Flat price per node, no I/O or IOPS line
  • Built-in PgBouncer connection pools
  • Six managed engines
+Pros
  • ✓Same figure on the pricing page and the invoice
  • ✓High availability priced as a visible second node
  • ✓Entry at $15.15 a month
−Cons
  • ✗Point-in-time recovery limited to 7 days
  • ✗22 backend connections on the 1 GiB plan
  • ✗New Standard clusters: 4 GiB max, no standby
DigitalOcean Managed Databases vs Amazon RDS
CriterionDigitalOcean Managed DatabasesAmazon RDS
Entry price$15.15/mo flat$13.98/mo (instance + 20 GiB)
High availabilityAdvanced Edition, $271.50/mo for two 8 GiB nodesMulti-AZ, instance price doubled
Point-in-time recoveryLast 7 daysUp to 35 days
SuperuserNot availablerds_superuser role
Verdict

The pick when a predictable invoice matters more than every knob. If you need more than 7 days of recovery or above 4 GiB on Standard, take Cloud SQL or Aiven.

See DigitalOcean databases → →
3
Best when the database is your app backend

Supabase

4.3/5

Supabase wraps a full PostgreSQL database in a backend: authentication, file storage, realtime, auto-generated APIs and edge functions. For a team that uses RDS only as the database of one app, that removes several AWS services at once, and every project is a full Postgres database, so pg_dump works on the way in and on the way out.

Pro starts at $25 a month and includes $10 a month of compute credits, enough to cover one Micro instance. Each extra project starts from $10 a month, and compute sizes run from Micro to 16XL, billed by the hour. The plan includes an 8 GB disk per project (then $0.125 per GB), 250 GB of egress (then $0.09 per GB) and 100,000 monthly active users. A spend cap is on by default on Pro, so a traffic spike stops at the quota instead of landing on the invoice.

The catch is the free plan and the extras. Free projects pause after one week of inactivity, and you get two active projects. Point-in-time recovery is an add-on at $100 a month per 7 days of retention. Read our Supabase review for the full breakdown, and our Supabase alternatives page if you are weighing it against Firebase or Appwrite. To get a team productive on it fast, see our Supabase training, or have our Supabase agency run the move.

Standout features
  • Postgres plus auth, storage and realtime
  • Spend cap on by default on Pro
  • $10 of compute credits included
+Pros
  • ✓Replaces several AWS services for one app
  • ✓Plain Postgres, easy to dump and leave
  • ✓Free plan to rehearse the migration
−Cons
  • ✗Free projects pause after a week idle
  • ✗Point-in-time recovery costs $100/mo per 7 days
  • ✗Each extra project from $10 a month
Supabase vs Amazon RDS
CriterionSupabaseAmazon RDS
Entry priceFree; Pro $25/mo$13.98/mo (instance + 20 GiB)
Egress250 GB included on Pro, then $0.09/GB100 GB free, then $0.09/GB
Point-in-time recoveryAdd-on, $100/mo per 7 daysIncluded, up to 35 days
Beyond the databaseAuth, storage, realtime, APIsDatabase only
Verdict

The pick when your RDS instance is really an app backend. If you need a plain database for several services, Cloud SQL or DigitalOcean fit better.

See Supabase plans → →Read our Supabase review
4
Best for databases that sit idle

Neon

4.2/5

Neon is serverless PostgreSQL: compute and storage are separate, so the database scales to zero after 5 minutes without a query and wakes up within a few hundred milliseconds when one arrives. An idle RDS instance bills every hour it is running, and a stopped one restarts on its own after seven days.

The paid plans have no monthly minimum. Launch bills $0.106 per CU-hour and $0.35 per GB-month of storage, where one CU is about 4 GB of RAM with its CPU; Neon puts typical Launch spend at $15 a month for an intermittent 1 GB database. Each project includes 500 GB of egress, then $0.10 per GB. Branching gives a pull request or a test its own copy of the database, billed only above the 10 branches per project included on Launch. HIPAA support and SLAs come with Scale, at $0.222 per CU-hour.

The limit is steady load. A database that runs all month at 1 CU costs 730 CU-hours, about $77 on Launch before storage, more than DigitalOcean's fixed 4 GiB node at $60.90. Use Neon where the idle hours are, and keep busy production on a fixed instance. If your team drives the database from an AI assistant, our Neon integration for Claude page shows the setup.

Standout features
  • Scale to zero after 5 minutes idle
  • Database branching for previews and tests
  • No monthly minimum on paid plans
+Pros
  • ✓Pays nothing for idle compute
  • ✓Free plan with 100 CU-hours per project
  • ✓Branches cut dev and staging copies
−Cons
  • ✗Costs more than a fixed instance under steady load
  • ✗PostgreSQL only
  • ✗HIPAA only on Scale
Neon vs Amazon RDS
CriterionNeonAmazon RDS
Entry priceFree; usage from $0.106/CU-hr$13.98/mo (instance + 20 GiB)
Idle databaseScales to zeroBilled per hour, restarts after 7 days stopped
Storage$0.35/GB-month$0.115/GB-month (gp3)
Egress500 GB/project, then $0.10/GB100 GB free, then $0.09/GB
Verdict

The pick for the RDS instances that wait more than they work. For a busy database running 24/7, take DigitalOcean or Cloud SQL instead.

See Neon pricing → →
5
Best for one bill across several clouds

Aiven for PostgreSQL

4.1/5

Aiven runs managed PostgreSQL, MySQL, Kafka, Valkey and more on Amazon Web Services, Google Cloud, Microsoft Azure, DigitalOcean, OVH and UpCloud. You pick the cloud and region, Aiven runs the service, and the plan card shows one hourly rate that covers the virtual machines, the networking and the backups. That is the opposite of RDS, where networking, backups and Multi-AZ are separate lines.

The ladder is public. Free costs $0 with 1 GB of storage, Developer $5 a month, Hobbyist from $12, Startup from $75, Business from $180 with high availability on two VMs, and Premium from $270 with a second standby. Point-in-time recovery goes from 2 days on Startup to 14 on Business and 30 on Premium. Because Aiven also runs on AWS, a move can keep your application on the cloud it already uses.

The entry plans are thin: Free, Developer and Hobbyist keep a single backup for disaster recovery and no point-in-time recovery, and Free and Developer do not let you pick the cloud or region. A production setup with failover starts at the Business price, well above an RDS Multi-AZ micro instance, so Aiven pays off on medium databases where the bundled networking and support offset the gap.

Standout features
  • All networking cost included in the plan
  • Same service on six clouds
  • Bring Your Own Cloud for larger setups
+Pros
  • ✓One hourly rate, no egress or backup line
  • ✓Also runs on AWS, next to your apps
  • ✓Public price ladder from $0 to $270
−Cons
  • ✗High availability starts at $180 a month
  • ✗No point-in-time recovery below Startup
  • ✗Free plan has no cloud or region choice
Aiven for PostgreSQL vs Amazon RDS
CriterionAiven for PostgreSQLAmazon RDS
Entry priceFree; Hobbyist from $12/mo$13.98/mo (instance + 20 GiB)
High availabilityBusiness, from $180/moMulti-AZ, instance price doubled
NetworkingIncludedBilled per GB
CloudsAWS, Google Cloud, Azure, DigitalOcean, OVH, UpCloudAWS only
Verdict

The pick when you want one predictable rate and the freedom to change cloud. If the budget is under $50 a month, DigitalOcean or Neon go further.

See Aiven plans → →
6
Best for Microsoft shops

Azure Database for PostgreSQL

4.0/5

Azure Database for PostgreSQL Flexible Server is Microsoft's managed PostgreSQL, the Azure counterpart of RDS for PostgreSQL. The smallest Burstable server, B1ms with 1 vCore and 2 GiB of memory, costs $12.410 a month pay as you go, and Premium SSD storage is $0.115 per GiB-month. Backup storage is free up to 100% of your provisioned storage.

High availability has three levels with their own SLA: 99.9% without a standby, 99.95% with a standby in the same zone and 99.99% with a standby in another zone. A zone-redundant server bills compute and storage for both replicas, and zone redundancy is not available on the Burstable tier, so zone-redundant HA starts on General Purpose. Reserved capacity saves up to 47% over one year and 64% over three.

Stop and start works like on RDS: while a server is stopped you pay only for storage and for backup storage above 100% of it. The Azure side has the same weak spot as AWS: network egress is billed at standard rates, and moving from one hyperscaler to another changes your landlord more than your bill. MySQL lives in a separate service, Azure Database for MySQL.

Standout features
  • Zone-redundant HA with a 99.99% SLA
  • Stop/start: pay storage only while stopped
  • Backup storage free up to 100% of storage
+Pros
  • ✓Burstable entry at $12.41 a month
  • ✓Reserved capacity up to 64% off over three years
  • ✓Fits Microsoft identity and billing
−Cons
  • ✗No zone-redundant HA on Burstable
  • ✗HA bills both replicas
  • ✗Network egress billed on top
Azure Database for PostgreSQL vs Amazon RDS
CriterionAzure Database for PostgreSQLAmazon RDS
Entry price$12.41/mo B1ms + storage$13.98/mo (instance + 20 GiB)
Storage$0.115/GiB-month$0.115/GB-month (gp3)
High availabilitySame-zone or zone-redundant, both replicas billedMulti-AZ, instance price doubled
Reserved discountUp to 64% (3 years)Up to 69%
Verdict

The pick when your company already runs on Azure. If you are not moving the rest of your stack, choose Cloud SQL or DigitalOcean instead.

See Azure PostgreSQL → →
7
Best if you stay on AWS

Amazon Aurora

3.9/5

Aurora is still part of Amazon RDS, but it is the alternative most guides start with, and for many teams the right one. It is MySQL- and PostgreSQL-compatible and runs up to 15 Aurora replicas for reads. Its serverless configuration now starts at 0 ACU, so an idle cluster can pause, and scales in steps as small as 0.5 ACU.

The price model is where you need a calculator. In AWS's own pricing example, serverless capacity costs $0.12 per ACU-hour on Aurora Standard, where storage is $0.10 per GB-month and I/O $0.20 per million requests. On Aurora I/O-Optimized, capacity costs $0.156 per ACU-hour and storage $0.225 per GB-month, with no I/O charge; AWS says it saves up to 40% when I/O exceeds 25% of your Aurora spend. A cluster that never pauses at 0.5 ACU costs $43.80 a month in capacity alone.

Moving from RDS is the shortest trip on this page: the database stays in the same AWS account, VPC and IAM setup. The flip side: you keep the AWS egress rates and the AWS bill. If the reason you are leaving is AWS itself, read our page on leaving AWS before you look at Aurora.

Standout features
  • Serverless that starts at 0 ACU
  • Up to 15 read replicas
  • I/O-Optimized option with no I/O charge
+Pros
  • ✓Easiest migration from RDS
  • ✓Same AWS account, VPC and IAM
  • ✓Scales in 0.5 ACU steps
−Cons
  • ✗Capacity, storage and I/O to model
  • ✗Keeps AWS egress pricing
  • ✗MySQL and PostgreSQL only
Amazon Aurora vs Amazon RDS
CriterionAmazon AuroraAmazon RDS
Entry price$0.12/ACU-hr + storage + I/O$0.016/hr db.t4g.micro
Idle databaseCan scale to 0 ACUBilled per hour
Read replicasUp to 15Up to 15 (PostgreSQL)
I/O billingPer million on Standard, none on I/O-OptimizedProvisioned IOPS billed if chosen
Verdict

The pick when RDS is the problem but AWS is not. If the AWS bill or egress is why you leave, go to Cloud SQL, DigitalOcean or Aiven instead.

See Aurora pricing → →
At a glance

7 Amazon RDS alternatives compared

Start with the "Main edge over RDS" column: each service fixes a different reason to leave. Prices are in US dollars, at the smallest paid or usage unit each vendor lists, in its default US region. For scale, the smallest RDS for PostgreSQL instance comes to $13.98 a month with 20 GiB of gp3 storage, before backups beyond the free allowance, IOPS and egress.

Best forMain edge over RDSFree planTeam sizeVisit
1Google Cloud SQLBest like-for-like replacement on another cloudMySQL, PostgreSQL and SQL Server, 35-day recovery4.5/5$0.0105/hr shared-core (~$7.67/mo)—Teams moving to Google CloudVisit →
2DigitalOcean Managed DatabasesBest for a predictable monthly billFlat price per node, no I/O or IOPS line4.4/5$15.15/mo—Startups, small teamsVisit →
3SupabaseBest when the database is your app backendAuth, storage and APIs around Postgres4.3/5Free; Pro $25/mo✓App teamsVisit →
4NeonBest for databases that sit idleScales to zero when idle4.2/5Free; $0.106/CU-hr✓Dev, staging, spiky appsVisit →
5Aiven for PostgreSQLBest for one bill across several cloudsNetworking included, six clouds4.1/5Free; Hobbyist $12/mo✓Multi-cloud teamsVisit →
6Azure Database for PostgreSQLBest for Microsoft shopsZone-redundant HA, stop/start4.0/5$12.41/mo B1ms + storage—Microsoft shopsVisit →
7Amazon AuroraBest if you stay on AWSServerless from 0 ACU, same AWS setup3.9/5$0.12/ACU-hr + storage + I/O—AWS teams staying on AWSVisit →

Scores from each service's official pages and our comparison on five criteria, each score the plain average of its five sub-scores. Prices read in 2026 on each pricing page.

Is your tool missing from this page? Email us: hello@hackceleration.com

Buyer's guide

How to choose an Amazon RDS alternative

Amazon RDS is a managed relational database service. You choose an engine (MySQL, PostgreSQL, MariaDB, Oracle, SQL Server or Db2) and a machine size; AWS installs the database, patches it, takes the backups, replaces failed hardware and, with Multi-AZ, keeps a standby ready to take over. You keep the schema, the queries and the tuning. Every alternative on this page sells the same deal: you stop running servers, and you pay for the work in the price. What changes from one vendor to the next is how they meter it.

Six units come back in every quote, and each vendor mixes them its own way. An instance-hour is one database server running for one hour, whether it serves queries or not: RDS, Cloud SQL and Azure bill this way, and a month counts about 730 of them. A vCPU is one virtual processor; Cloud SQL prices its dedicated machines per vCPU-hour plus a price per GiB of memory, and AWS bills Extended Support per vCPU-hour. A compute unit is a slice of CPU and memory sold by usage: Neon's CU is about 4 GB of RAM, Aurora's ACU is its own measure, and you pay only for the units the database uses while it is awake. A GB-month is one gigabyte stored for a full month: 50 GB kept for half a month counts as 25 GB-months. IOPS are input/output operations per second, the speed of the disk; some services include a baseline and charge for provisioned IOPS above it, whether you consume them or not. Egress is data leaving the provider's network, to your users or to another cloud, billed per GB above an allowance.

Priced at the same size, the order changes. Take one PostgreSQL server with 2 vCPU and 8 GiB of memory running all month, compute only, at list price: $101.18 on Cloud SQL Enterprise in Iowa, $122.64 for an RDS db.m7g.large in US East (N. Virginia), $129.94 for an Azure General Purpose D2s v6 server pay as you go, $135.75 for DigitalOcean's 8 GiB Advanced Edition node, $154.76 on Neon at 2 CU around the clock, and $350.40 on Aurora Serverless held at 4 ACU, since one ACU is about 2 GiB of memory. Storage, backups and egress come on top. The services billed by usage only win when the database sleeps; under steady load, a fixed instance costs less.

Before you compare, ask each vendor five questions. What does it cost at your current instance size and storage, with high availability on? How many days of point-in-time recovery do you get, and on which plan? Which PostgreSQL or MySQL extensions and versions are supported, and do you get superuser? How much egress is included, and what does each GB above it cost? Can the move run with logical replication, so the cutover takes minutes instead of a weekend? Then run a pilot on a copy of your largest table, not on a demo database.

Several names other lists rank deserve a line. Crunchy Bridge is managed PostgreSQL on AWS, Azure or Google Cloud, with plans starting at $10 a month and storage at $0.10 per GB, picked by teams that want pure Postgres. ScaleGrid's smallest standalone node costs $6 a month. PlanetScale Postgres starts at $5 a month on a single node and runs high availability on one primary and two replicas across three zones. AlloyDB is Google's PostgreSQL-compatible service for heavier workloads, next to Cloud SQL. Oracle Database, Microsoft SQL Server and MongoDB show up in software directories as alternatives, but they are database engines: RDS can run the first two for you, and MongoDB Atlas is a document database, not a drop-in for SQL. App platforms bundle Postgres too: see our pages on Render alternatives, Railway alternatives and leaving Heroku. And self-hosting on a rented server costs least on paper, as long as someone on your team owns backups, failover and upgrades.

Before you switch

Five traps RDS leavers fall into

01

Burst credits on the smallest instances

RDS for PostgreSQL T4g and T3 instances run in Unlimited mode: when average CPU over 24 hours passes the instance baseline, you pay CPU credits at $0.075 per vCPU-hour. That is more than four times the $0.016 hourly price of a whole db.t4g.micro. Before you compare a $13.98 RDS figure with an alternative, check last month's CPU credit line.

02

Price the idle IP and the idle copy

On Cloud SQL, an IPv4 address on an idle instance costs $0.01 an hour, $7.30 a month, almost the price of a running db-f1-micro at about $7.67. On RDS, a stopped instance restarts after seven days. If you are moving to save on idle databases, a service that scales to zero (Neon, Aurora Serverless at 0 ACU) removes the compute line.

03

Check connections before the plan

DigitalOcean's 1 GiB PostgreSQL plan accepts 22 backend connections, and the 2 GiB plan 47. An app that opens a pool of 50 connections on RDS will fail on the entry plan. Put PgBouncer in front of it, or budget the 4 GiB plan at $60.90 a month.

04

Read the free plan's egress, not only its storage

Neon's Free plan suspends compute when a project uses its 100 CU-hours or 5 GB of network transfer in the month, until the next billing period. Supabase Free includes 5 GB of egress. A demo with images or exports can hit transfer before storage.

05

Count recovery days as a price

RDS lets you keep up to 35 days of point-in-time recovery, with backup storage free up to your provisioned storage. DigitalOcean gives 7 days, Aiven 14 on Business, and Supabase sells it at $100 a month per 7 days of retention, so matching 28 days costs $400 a month. Decide how far back you need to restore before you compare plans.

FAQ · 8 questions

Amazon RDS alternatives, the FAQ

  • Is it cheaper to run PostgreSQL on EC2 than on RDS?
    On the instance line, yes, by about half. An m7g.large EC2 server (2 vCPU, 8 GiB) costs $0.0816 an hour in US East (N. Virginia), against $0.168 for a db.m7g.large on RDS for PostgreSQL: $59.57 a month against $122.64. The gap pays for what RDS does for you, patching, automated backups with point-in-time recovery and Multi-AZ failover. On EC2 those become your team's job, and so does every major-version upgrade.
  • Does Azure have a managed database like Amazon RDS?
    Yes: Azure Database for PostgreSQL and Azure Database for MySQL, two Flexible Server services, plus Azure SQL Database for SQL Server. On PostgreSQL, Flexible Server currently supports PostgreSQL 11 to 18, with 19 in preview, which helps if your RDS instance still runs an old major version.
  • Is Amazon Aurora cheaper than RDS?
    It depends on your I/O. Aurora Standard charges $0.20 per million I/O requests on top of storage, while RDS gp3 includes a baseline. In AWS's own example, a 1,000 GB database reading 350 pages a second pays $181.44 a month in read I/O alone, which is when I/O-Optimized starts to pay.
  • How do I migrate off Amazon RDS with little downtime?
    Use logical replication. For PostgreSQL, dump the schema with pg_dump, create a publication on RDS and a subscription on the new database, let it sync, then switch the connection string. For a bulk copy, exporting a snapshot to Amazon S3 costs $0.013 per GB of snapshot size in AWS's RDS for PostgreSQL example.
  • Can I stop an RDS instance to save money?
    Yes, for up to seven days at a time. While it is stopped you pay storage, provisioned IOPS, backups and a public IPv4 address if it has one. Instances with a read replica, or that are read replicas, cannot be stopped at all, so the replica setup has to go first.
  • Are Amazon RDS backups free?
    Up to a point: backups are free up to the size of your provisioned storage in the region, and the free allowance is counted per account and per region. Above it, snapshot storage costs $0.095 per GB-month for PostgreSQL in US East (N. Virginia), and the default retention is 7 days.
  • Can Snowflake or BigQuery replace Amazon RDS?
    No for the application database, yes for reporting. They are analytics warehouses, built for large scans, not for thousands of small writes a second. Keep a transactional database and copy data out: AWS's zero-ETL integration with Redshift charges $0.01 per GB for the initial export. See our Amazon Redshift alternatives page for that side.
  • Do RDS Reserved Instances transfer if I leave?
    No. You pay for every hour of the one- or three-year term whether the instance runs or not, on No Upfront and Partial Upfront alike. Time your migration for the end of the term, and buy any new commitment on the alternative only after the pilot.
Hack'celeration Lab

Get the next breakdown in your inbox

No spam. Unsubscribe anytime.