Amazon Aurora vs Supabase
SEPT 2026 auditA comparison of Amazon Aurora and Supabase built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Amazon Aurora if…
Teams on AWS who want a Postgres or MySQL cluster that can throw off a copy-on-write clone of production in minutes, keep up to fifteen readers behind it, and pause to nothing between bursts in serverless mode.
Editorial · Palash Bagchi · approved
Choose Supabase if…
Teams who want Postgres plus auth, storage and generated APIs from one vendor on a fixed monthly bill, and who would otherwise assemble those pieces themselves.
Editorial · Palash Bagchi · approved
Consider something else if…
- Amazon Aurora: You want the upstream database rather than a compatible one, or a branch workflow rather than a clone. AWS documents cloning as a way to build a test environment, not as something you do per pull request.
- Supabase: You want only a database. Much of the $25 covers a platform you may not use, and free projects are paused after a week of inactivity, which is not the same as scaling to zero.
Neither quite fits? Every other option, ranked by iScore: Amazon Aurora alternatives · Supabase alternatives
19 sourced criteria separate them — see where, with sources, below.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Amazon Aurora 0
Supabase 0
At a glance.
| Criterion | Amazon Aurora | Supabase |
|---|---|---|
| Pricing | ||
| Free tier | No — capped Free plan plus time-limited credits | Yes |
| Kind of free offer | Introductory free tier | Free tier |
| Entry paid plan | No plan fee and no minimum commitment — Aurora charges for what you use. AWS's own worked example prices serverless compute at $0.12 per ACU-hour on Aurora Standard in US East (N. Virginia), and the smallest capacity you can set is 0.5 ACUs; storage and I/O are billed separately. | $25/month for Pro, including the first project and $10/mo of compute credits — enough to cover one Micro instance, so this runs a small project rather than being a fee on top of it. Additional projects from $10/mo. |
| Pricing model | Pay per use with no plan fee: instances plus storage plus I/O, or ACU-hours in serverless mode. AWS's own worked example prices serverless compute at $0.12 per ACU-hour on Aurora Standard and $0.156 on Aurora I/O-Optimized in US East (N. Virginia) — the difference being whether I/O is metered separately or folded into a higher compute and storage rate. Provisioned instances also offer Reserved Instance pricing, and usage may qualify for Database Savings Plans against a committed hourly spend. | Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size |
| Limits | ||
| Storage (entry plan) | No included allowance on the pay-as-you-go Paid plan: storage scales automatically up to 256 TiB and is metered per GB-month — $0.10 per GB-month for Aurora Standard in AWS's US East (N. Virginia) example. The AWS Free Tier Free plan caps a cluster at 1 GiB. | 8 GB disk per project on the Pro plan; 500 MB on Free |
| Execution | ||
| Managed connection pooling | Supported — through Amazon RDS Proxy, a separate feature of the service | Supported — Shared pooler on every plan, IPv4-only; the dedicated pooler is paid plans only. |
| Infrastructure | ||
| Regions | 34 AWS regions, the same list for the MySQL- and PostgreSQL-compatible editions. Counted from the two availability tables in Aurora's own docs, which publish the regions and no total. | 17 specific AWS regions across the Americas, Europe, Asia-Pacific and South America, plus broader 'general region' groupings that place the project on an available AWS region within an area. General regions do not support read replicas or API management. |
| Uptime SLA | 99.99% for a cluster deployed across two or more Availability Zones; 99.9% for a single-AZ cluster. Both are service-credit thresholds. | Uptime SLAs are an Enterprise line item. No uptime percentage appears anywhere on the pricing page; Team lists "priority email support & SLAs" without a figure. |
| Data | ||
| Engine | MySQL- and PostgreSQL-compatible. Aurora is AWS's own engine rather than a hosted build of either, so compatibility is the claim being made — existing code, tools and applications are stated to work, which is not the same as being the upstream database. | PostgreSQL |
| Connection limit | Derived from memory, not set per plan. On Aurora serverless the default follows the maximum ACU setting — 90 connections on MySQL and 189 on PostgreSQL at 1 ACU, 135/823 at 4 ACUs, 1,000/1,669 at 8 ACUs — and a minimum capacity of 0 or 0.5 ACUs caps PostgreSQL at 2,000. | 60 direct and 200 pooled connections on the Micro instance included with Pro; both scale with instance size |
| When idle | Pauses only in serverless mode with minimum capacity set to zero ACUs: the instance auto-pauses after an idle interval you choose — 300 seconds (five minutes) by default and at minimum, up to 86,400 seconds (one day) — and resumes automatically when a connection request arrives. | Free projects are paused after one week of inactivity and must be restored manually; paid projects are not paused |
| Database branching | Limited — clones, not a branch workflow | Supported |
| Point-in-time recovery | Any point inside the backup retention period, so up to 35 days. Aurora's backups are continuous and incremental against the cluster volume rather than periodic snapshots plus log replay, which is why AWS states no performance impact while they are taken. | Point-in-time recovery is a paid add-on on Pro, Team and Enterprise, and needs at least a Small compute add-on alongside it. Worst-case recovery point is 2 minutes. Without it, restores go back only to a daily backup. |
| Read replicas | Supported — 15 per cluster, a quota AWS will not raise | Supported |
| Backup retention | 1 to 35 days. Unlike an RDS DB instance it cannot be set to 0 — Aurora backs the cluster volume up continuously and there is no way to turn that off. | Daily backups: 7 days on Pro, 14 days on Team, up to 30 days on Enterprise. Free projects get no automatic backups at all — Supabase tells free users to export their own data with the CLI. |
| Compliance | ||
| SOC 2 | Assessed by third-party auditors under multiple AWS compliance programs, SOC among them; the docs name SOC, not SOC 2. Reports download via AWS Artifact. AWS names the SOC program, not a SOC 2 type. | SOC 2 Type 2 compliant; report available to Enterprise and Team customers via the dashboard. |
| ISO 27001 | Covered under AWS's account-wide ISO/IEC 27001:2022 certification — not scoped per-service the way SOC, HIPAA and PCI DSS are on AWS's own site. | ISO 27001 certified; certificate available to Enterprise and Team customers via the dashboard. |
| HIPAA | Listed as a HIPAA-eligible service on AWS's own reference page. | HIPAA compliant; customers may store PHI after signing a BAA and meeting shared-responsibility obligations. |
| GDPR / data residency | AWS customers can process personal data on all AWS services in compliance with GDPR, and choose the storage type and geographic region for their data. | Projects hosted in EU regions keep primary database data in-region; a DPA is available. |
| Encryption at rest | On by default: all new database clusters created on or after February 18, 2026 are encrypted at rest with AES-256 under an AWS KMS key. | AES-256 at rest and TLS in transit; sensitive tokens/keys get application-level encryption before storage. |
| Role-based access control | IAM identity-based policies and roles govern who may act on Aurora resources, and IAM database authentication can be used to sign in to the DB cluster. | Organization members can be granted access to specific resources, including read-only and billing-only roles. |
Where they differ.
Free tier
- Amazon Aurora
- No — capped Free plan plus time-limited credits
- Supabase
- Yes
Sources (2) →Sources ↓
- Amazon Aurora pricing — Amazon Web Services ↗
“New AWS customers can get started with Aurora PostgreSQL serverless at no cost with the AWS Free Tier. You get $100 in AWS credits at sign-up to be used across eligible AWS services, including Aurora, for up to 12 months, in both Free and Paid plans, and you can earn an additional $100 in credits, for a total of $200. Free plan gives you access to Aurora PostgreSQL serverless instances with up to 4 ACUs and 1 GiB of storage per cluster.”
Read 2026-09-09 · official pricing · Report a correction
- Pricing & Fees — Supabase ↗
“500 MB database size”
Read 2026-09-05 · official pricing · Report a correction
Kind of free offer
- Amazon Aurora
- Introductory free tier
- Supabase
- Free tier
Sources (2) →Sources ↓
- AWS Free Tier ↗
“The account closes on its own 6 months after you open it or when your credits run out, whichever comes first. You won't be charged unless you convert to a Paid plan.”
Read 2026-09-13 · official pricing · Report a correction
- Pricing & Fees — Supabase ↗
“500 MB database size”
Read 2026-09-05 · official pricing · Report a correction
Entry paid plan
- Amazon Aurora
- No plan fee and no minimum commitment — Aurora charges for what you use. AWS's own worked example prices serverless compute at $0.12 per ACU-hour on Aurora Standard in US East (N. Virginia), and the smallest capacity you can set is 0.5 ACUs; storage and I/O are billed separately.
- Supabase
- $25/month for Pro, including the first project and $10/mo of compute credits — enough to cover one Micro instance, so this runs a small project rather than being a fee on top of it. Additional projects from $10/mo.
Sources (2) →Sources ↓
- Amazon Aurora Pricing — Amazon Web Services ↗
“With Aurora, you only pay for what you use. Aurora charges for database instances and storage, along with any optional features you choose to enable. [...] With Aurora serverless , the minimum database capacity you can set is 0.5 ACUs. [...] 5 ACUs * $0.12 per ACU-hour * 30/60 hour”
Read 2026-09-13 · official pricing · Report a correction
- Supabase Pricing ↗
“$25/month [...] First project included. Additional projects from $10/mo. [...] Paid plans include $10/mo in compute credits, enough to cover one Micro instance.”
Read 2026-09-14 · official pricing · Report a correction
Pricing model
- Amazon Aurora
- Pay per use with no plan fee: instances plus storage plus I/O, or ACU-hours in serverless mode. AWS's own worked example prices serverless compute at $0.12 per ACU-hour on Aurora Standard and $0.156 on Aurora I/O-Optimized in US East (N. Virginia) — the difference being whether I/O is metered separately or folded into a higher compute and storage rate. Provisioned instances also offer Reserved Instance pricing, and usage may qualify for Database Savings Plans against a committed hourly spend.
- Supabase
- Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size
Sources (2) →Sources ↓
- Amazon Aurora pricing — Amazon Web Services ↗
“Aurora charges for database instances and storage, along with any optional features you choose to enable. Aurora PostgreSQL and Aurora MySQL offer On-Demand and Reserved Instance pricing. [...] We want to calculate the compute costs of running this workload on Aurora serverless with the database cluster configured as Aurora Standard and Aurora I/O-Optimized in US East (N. Virginia). [...] 5 ACUs * $0.12 per ACU-hour * 30/60 hour $0.30 [...] 5 ACUs * $0.156 per ACU-hour * 30/60 hour $0.39”
Read 2026-09-09 · official pricing · Report a correction
- Pricing & Fees — Supabase ↗
“First project included. Additional projects from $10/mo. [...] Paid plans include $10/mo in compute credits, enough to cover one Micro instance.”
Read 2026-09-05 · official pricing · Report a correction
Storage (entry plan)
- Amazon Aurora
- No included allowance on the pay-as-you-go Paid plan: storage scales automatically up to 256 TiB and is metered per GB-month — $0.10 per GB-month for Aurora Standard in AWS's US East (N. Virginia) example. The AWS Free Tier Free plan caps a cluster at 1 GiB.
- Supabase
- 8 GB disk per project on the Pro plan; 500 MB on Free
Sources (2) →Sources ↓
- Amazon Aurora Pricing — Amazon Web Services ↗
“Free plan gives you access to Aurora PostgreSQL serverless instances with up to 4 ACUs and 1 GiB of storage per cluster. You can upgrade to the Paid plan at any time to increase capacity up to 256 ACUs and automatically scale storage up to 256 TiB. [...] We want to calculate the storage and I/O cost of running this workload with Aurora Standard and Aurora I/O-Optimized storage in US East (N. Virginia). [...] 80 GB * $0.10 per GB-month (30 days)”
Read 2026-09-13 · official pricing · Report a correction
- Pricing & Fees — Supabase ↗
“8 GB disk size per project”
Read 2026-09-05 · official pricing · Report a correction
Regions
34 AWS regions, the same list for the MySQL- and PostgreSQL-compatible editions. Counted from the two availability tables in Aurora's own docs, which publish the regions and no total.
17 specific AWS regions across the Americas, Europe, Asia-Pacific and South America, plus broader 'general region' groupings that place the project on an available AWS region within an area. General regions do not support read replicas or API management.
Sources (2) →Sources ↓
- Regions and Availability Zones — Amazon Aurora User Guide ↗
“Aurora MySQL Region availability The following table shows the AWS Regions where Aurora MySQL is currently available and the endpoint for each Region. Region Name Region Endpoint Protocol US East (Ohio) us-east-2 rds.us-east-2.amazonaws.com HTTPS US East (N. Virginia) us-east-1 rds.us-east-1.amazonaws.com HTTPS [...] Aurora PostgreSQL Region availability”
Read 2026-09-09 · official docs · Report a correction
- Available regions — Supabase Docs ↗
“Each Supabase project is deployed to one primary region. [...] General regions deploy to an available AWS region within that broader area, which may not match a specific jurisdiction. For example, the "Europe" general region includes London and Zurich, which are not EU member states. Region selection is a data-location control, not proof of regulatory compliance. [...] General regions aren't yet supported for read replicas or management via the API.”
Read 2026-09-05 · official docs · Report a correction
Uptime SLA
- Amazon Aurora
- 99.99% for a cluster deployed across two or more Availability Zones; 99.9% for a single-AZ cluster. Both are service-credit thresholds.
- Supabase
- Uptime SLAs are an Enterprise line item. No uptime percentage appears anywhere on the pricing page; Team lists "priority email support & SLAs" without a figure.
Sources (2) →Sources ↓
- Amazon Aurora Service Level Agreement ↗
“make each Multi-AZ Cluster available with a Monthly Uptime Percentage as shown in the table below during any monthly billing cycle [...] Less than 99.99% but equal to or greater than 99.0% 10% [...] make each Single-AZ Cluster available with a Single-AZ Uptime Percentage [...] Less than 99.9% but equal to or greater than 99.0% 10%”
Read 2026-09-14 · official site · Report a correction
- Supabase Pricing ↗
“Custom Designated support manager Uptime SLAs Supports AWS PrivateLink”
Read 2026-09-14 · official pricing · Report a correction
Engine
- Amazon Aurora
- MySQL- and PostgreSQL-compatible. Aurora is AWS's own engine rather than a hosted build of either, so compatibility is the claim being made — existing code, tools and applications are stated to work, which is not the same as being the upstream database.
- Supabase
- PostgreSQL
Sources (2) →Sources ↓
- What is Amazon Aurora? — Amazon Aurora User Guide ↗
“Amazon Aurora (Aurora) is a fully managed relational database engine that's compatible with MySQL and PostgreSQL. [...] The code, tools, and applications you use today with your existing MySQL and PostgreSQL databases can be used with Aurora.”
Read 2026-09-09 · official docs · Report a correction
- Connect to your database — Supabase Docs ↗
“The session mode connection string connects to your Postgres instance through the shared pooler.”
Read 2026-09-14 · official docs · Report a correction
Connection limit
- Amazon Aurora
- Derived from memory, not set per plan. On Aurora serverless the default follows the maximum ACU setting — 90 connections on MySQL and 189 on PostgreSQL at 1 ACU, 135/823 at 4 ACUs, 1,000/1,669 at 8 ACUs — and a minimum capacity of 0 or 0.5 ACUs caps PostgreSQL at 2,000.
- Supabase
- 60 direct and 200 pooled connections on the Micro instance included with Pro; both scale with instance size
Sources (2) →Sources ↓
- Performance and scaling for Aurora serverless — Amazon Aurora User Guide ↗
“The default value for this parameter is derived from a formula based on the memory size of the DB instance. [...] Maximum ACUs Default maximum connections on Aurora MySQL Default maximum connections on Aurora PostgreSQL 1 90 189 4 135 823 8 1,000 1,669 [...] However, when you specify a minimum capacity of 0 or 0.5 ACUs on PostgreSQL-compatible DB instances, the maximum value of max_connections is capped at 2,000.”
Read 2026-09-13 · official docs · Report a correction
- Pricing & Fees — Supabase ↗
“1 GB RAM / 2-core ARM CPU / Connections: Direct 60, Pooler 200”
Read 2026-09-05 · official pricing · Report a correction
When idle
- Amazon Aurora
- Pauses only in serverless mode with minimum capacity set to zero ACUs: the instance auto-pauses after an idle interval you choose — 300 seconds (five minutes) by default and at minimum, up to 86,400 seconds (one day) — and resumes automatically when a connection request arrives.
- Supabase
- Free projects are paused after one week of inactivity and must be restored manually; paid projects are not paused
Sources (2) →Sources ↓
- Scaling to Zero ACUs with automatic pause and resume for Aurora serverless — Amazon Aurora User Guide ↗
“Aurora serverless DB instances can automatically pause after a period with no user connections, and automatically resume when a connection request arrives. [...] To enable the auto-pause behavior for all the Aurora serverless DB instances in an Aurora cluster, you set the minimum capacity value for the cluster to zero ACUs. [...] The minimum interval that you can set is 300 seconds (five minutes). That's the default if you don't specify an interval. The maximum interval that you can set is 86,400 seconds (one day).”
Read 2026-09-13 · official docs · Report a correction
- Pricing & Fees — Supabase ↗
“Free projects are paused after 1 week of inactivity. Limit of 2 active projects.”
Read 2026-09-05 · official pricing · Report a correction
Database branching
- Amazon Aurora
- Limited — clones, not a branch workflow
- Supabase
- Supported
Sources (2) →Sources ↓
- Cloning a volume for an Amazon Aurora DB cluster — Amazon Aurora User Guide ↗
“Aurora uses a copy-on-write protocol to create a clone. This mechanism uses minimal additional space to create an initial clone. [...] Aurora cloning is especially useful for quickly setting up test environments using your production data, without risking data corruption.”
Read 2026-09-09 · official docs · Report a correction
- Pricing & Fees — Supabase ↗
“Branching [...] $0.01344 per branch, per hour”
Read 2026-09-05 · official pricing · Report a correction
Point-in-time recovery
- Amazon Aurora
- Any point inside the backup retention period, so up to 35 days. Aurora's backups are continuous and incremental against the cluster volume rather than periodic snapshots plus log replay, which is why AWS states no performance impact while they are taken.
- Supabase
- Point-in-time recovery is a paid add-on on Pro, Team and Enterprise, and needs at least a Small compute add-on alongside it. Worst-case recovery point is 2 minutes. Without it, restores go back only to a daily backup.
Sources (2) →Sources ↓
- Backing up and restoring an Aurora DB cluster — Amazon Aurora User Guide ↗
“Aurora automated backups are continuous and incremental, so you can quickly restore to any point within the backup retention period. No performance impact or interruption of database service occurs as backup data is being written.”
Read 2026-09-09 · official docs · Report a correction
- Database Backups — Supabase Docs ↗
“Point-in-Time Recovery (PITR) allows you to back up a project at shorter intervals, giving you the option to restore to any chosen point with up to seconds of granularity. [...] Pro, Team and Enterprise Plan projects can enable PITR as an add-on. Projects that want to use PITR must also use at least a Small compute add-on to ensure smooth functioning. [...] in the worst case scenario, PITR achieves a Recovery Point Objective (RPO) of two minutes.”
Read 2026-09-05 · official docs · Report a correction
Backup retention
- Amazon Aurora
- 1 to 35 days. Unlike an RDS DB instance it cannot be set to 0 — Aurora backs the cluster volume up continuously and there is no way to turn that off.
- Supabase
- Daily backups: 7 days on Pro, 14 days on Team, up to 30 days on Enterprise. Free projects get no automatic backups at all — Supabase tells free users to export their own data with the CLI.
Sources (2) →Sources ↓
- Backing up and restoring an Aurora DB cluster — Amazon Aurora User Guide ↗
“Aurora backs up your cluster volume automatically and retains restore data for the length of the backup retention period. [...] You can specify a backup retention period from 1–35 days when you create or modify a DB cluster.”
Read 2026-09-09 · official docs · Report a correction
- Database Backups — Supabase Docs ↗
“We automatically back up all Pro, Team, and Enterprise Plan projects on a daily basis. [...] Pro Plan projects can access the last 7 days of daily backups. Team Plan projects can access the last 14 days of daily backups, while Enterprise Plan projects can access up to 30 days of daily backups. [...] We recommend that free tier plan projects regularly export their data using the Supabase CLI db dump command and maintain off-site backups.”
Read 2026-09-05 · official docs · Report a correction
SOC 2
- Amazon Aurora
- Assessed by third-party auditors under multiple AWS compliance programs, SOC among them; the docs name SOC, not SOC 2. Reports download via AWS Artifact. AWS names the SOC program, not a SOC 2 type.
- Supabase
- SOC 2 Type 2 compliant; report available to Enterprise and Team customers via the dashboard.
Sources (2) →Sources ↓
- Compliance validation for Amazon Aurora — Amazon Aurora User Guide ↗
“Third-party auditors assess the security and compliance of Amazon Aurora as part of multiple AWS compliance programs. These include SOC, PCI, FedRAMP, HIPAA, and others. [...] You can download third-party audit reports using AWS Artifact.”
Read 2026-09-13 · official docs · Report a correction
- Supabase Security ↗
“Supabase is SOC 2 Type 2 compliant.”
Read 2026-09-12 · official site · Report a correction
ISO 27001
- Amazon Aurora
- Covered under AWS's account-wide ISO/IEC 27001:2022 certification — not scoped per-service the way SOC, HIPAA and PCI DSS are on AWS's own site.
- Supabase
- ISO 27001 certified; certificate available to Enterprise and Team customers via the dashboard.
Sources (2) →Sources ↓
- ISO/IEC 27001:2022 Compliance — AWS ↗
“AWS has certification for compliance with ISO/IEC 27001:2022, 27017:2015, and 27018:2019. These certifications are performed by independent third-party auditors.”
Read 2026-09-12 · official site · Report a correction
- Supabase Security ↗
“Supabase is ISO 27001 certified.”
Read 2026-09-12 · official site · Report a correction
HIPAA
- Amazon Aurora
- Listed as a HIPAA-eligible service on AWS's own reference page.
- Supabase
- HIPAA compliant; customers may store PHI after signing a BAA and meeting shared-responsibility obligations.
Sources (2) →Sources ↓
- HIPAA Eligible Services Reference — AWS ↗
“The services listed below are eligible to create, receive, process, maintain, or transmit electronic protected health information (ePHI). [...] Amazon Aurora AWS B2B Data Interchange AWS Backup AWS Batch Amazon Bedrock Amazon Bedrock”
Read 2026-09-13 · official site · Report a correction
- Supabase Security ↗
“Supabase is HIPAA compliant.”
Read 2026-09-12 · official site · Report a correction
GDPR / data residency
- Amazon Aurora
- AWS customers can process personal data on all AWS services in compliance with GDPR, and choose the storage type and geographic region for their data.
- Supabase
- Projects hosted in EU regions keep primary database data in-region; a DPA is available.
Sources (2) →Sources ↓
- GDPR — Amazon Web Services ↗
“AWS customers can use all AWS services to process personal data [...] in compliance with the GDPR. [...] Customers have control of their customer data. With AWS, customers can: Determine where their customer data will be stored, including the type of storage and geographic region of that storage.”
Read 2026-09-12 · official site · Report a correction
- Supabase Security ↗
“Supabase supports GDPR-compliant deployments. Projects hosted in EU regions keep your primary database data in-region, and a Data Processing Agreement (DPA) is available for customers who need a formal data processing contract under GDPR.”
Read 2026-09-14 · official site · Report a correction
Encryption at rest
- Amazon Aurora
- On by default: all new database clusters created on or after February 18, 2026 are encrypted at rest with AES-256 under an AWS KMS key.
- Supabase
- AES-256 at rest and TLS in transit; sensitive tokens/keys get application-level encryption before storage.
Sources (2) →Sources ↓
- Encrypting Amazon Aurora resources — Amazon Aurora User Guide ↗
“are encrypted at rest using industry standard AES-256 encryption. This encryption happens automatically in the background, securing your data without requiring any action from you. [...] Amazon Aurora uses an AWS Key Management Service key to encrypt these resources.”
Read 2026-09-13 · official docs · Report a correction
- Supabase Security ↗
“All customer data is encrypted at rest with AES-256 and in transit via TLS.”
Read 2026-09-12 · official site · Report a correction
Role-based access control
- Amazon Aurora
- IAM identity-based policies and roles govern who may act on Aurora resources, and IAM database authentication can be used to sign in to the DB cluster.
- Supabase
- Organization members can be granted access to specific resources, including read-only and billing-only roles.
Sources (2) →Sources ↓
- Identity and access management for Amazon Aurora — Amazon Aurora User Guide ↗
“AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be authenticated (signed in) and authorized (have permissions) to use Amazon RDS resources. [...] An IAM role is an identity within your AWS account that has specific permissions. [...] You can authenticate to your DB cluster using IAM database authentication.”
Read 2026-09-13 · official docs · Report a correction
- Supabase Security ↗
“Members of organizations in Supabase can be granted access to specific resources.”
Read 2026-09-12 · official site · Report a correction
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
Documented by only one.
These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing — except where we say we read the other provider's own page on a given date and it does not state it. Those rows lean, and the provider can correct them with a link.
Questions this comparison answers.
Entry paid plan: Amazon Aurora or Supabase?
Amazon Aurora: No plan fee and no minimum commitment — Aurora charges for what you use. AWS's own worked example prices serverless compute at $0.12 per ACU-hour on Aurora Standard in US East (N. Virginia), and the smallest capacity you can set is 0.5 ACUs; storage and I/O are billed separately.
Supabase: $25/month for Pro, including the first project and $10/mo of compute credits — enough to cover one Micro instance, so this runs a small project rather than being a fee on top of it. Additional projects from $10/mo.
Free tier: Amazon Aurora or Supabase?
Amazon Aurora: No — capped Free plan plus time-limited credits
Supabase: Yes
Storage (entry plan): Amazon Aurora or Supabase?
Amazon Aurora: No included allowance on the pay-as-you-go Paid plan: storage scales automatically up to 256 TiB and is metered per GB-month — $0.10 per GB-month for Aurora Standard in AWS's US East (N. Virginia) example. The AWS Free Tier Free plan caps a cluster at 1 GiB.
Supabase: 8 GB disk per project on the Pro plan; 500 MB on Free
Should I choose Amazon Aurora or Supabase?
Pick Amazon Aurora if Teams on AWS who want a Postgres or MySQL cluster that can throw off a copy-on-write clone of production in minutes, keep up to fifteen readers behind it, and pause to nothing between bursts in serverless mode.
Pick Supabase if Teams who want Postgres plus auth, storage and generated APIs from one vendor on a fixed monthly bill, and who would otherwise assemble those pieces themselves.
Comments are hosted by EchoThread, which sets cookies and offers social sign-in. Like the analytics on this site, it does not load until you accept — see the privacy page.