Amazon Aurora vs Turso
SEPT 2026 auditA comparison of Amazon Aurora and Turso 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 Turso if…
Applications that want a database per tenant or per user — 100 databases on the free plan and unlimited above it make that a shape you can actually build.
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.
- Turso: It is SQLite, not Postgres: the metered units are rows read and written rather than compute, and the extension ecosystem you may be relying on is not there.
Neither quite fits? Every other option, ranked by iScore: Amazon Aurora alternatives · Turso alternatives
21 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
Turso 0
At a glance.
| Criterion | Amazon Aurora | Turso |
|---|---|---|
| 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. | $4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58. |
| 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. | Per database, metered on rows rather than compute time: 500 million rows read and 10 million written a month on the free plan, 2.5 billion and 25 million on Developer, with overage at $1 per billion rows read and $1 per million written. |
| 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. | 9 GB on Developer, then $0.75 per GB. The free plan includes 5 GB; Scaler is 24 GB at $0.50 and Pro 50 GB at $0.45. |
| 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. | Six AWS locations in the Platform API's location list: Tokyo (ap-northeast-1), Mumbai (ap-south-1), Ireland (eu-west-1), N. Virginia (us-east-1), Ohio (us-east-2) and Oregon (us-west-2). Read from the documented GET /v1/locations sample response; the same six AWS regions are offered for PrivateLink. |
| 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. | SQLite, via libSQL — Turso's own fork. Not Postgres or MySQL, so the query surface and the client libraries differ from every other database on this site. |
| 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. | Databases are archived after 10 days of inactivity on the free plan; an unarchive call through the CLI or Platform API brings the group back. Turso publishes no archival window for paid plans. |
| 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. | 10 days on Developer. 1 day on the free plan, 30 days on Scaler and 90 days on Pro. |
| Read replicas | Supported — 15 per cluster, a quota AWS will not raise | Limited — Embedded replicas run inside your app; managed multi-region Data Edge replica locations are deprecated for new users. |
| 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. | Continuous rather than scheduled: backups are taken at every COMMIT and kept for the plan's restore window — 24 hours on Free, 10 days on Developer, 30 on Scaler, 90 on Pro. Turso publishes no separate backup retention setting. |
| Rewind in place | Limited — Aurora MySQL edition only | Not supported — PITR restores forward into a fresh database; the existing database cannot be rewound in place. |
| 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. | Volume-level encryption at rest is described as part of Turso's SOC 2 standards; the docs point to Turso's trust center for details. |
| HIPAA | Listed as a HIPAA-eligible service on AWS's own reference page. | Turso states it is HIPAA compliant and will provide a HIPAA compliance BAA letter to Pro plan and Enterprise users on request. |
| 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. | A database confined to EU locations never leaves the EU; the exception is backups, which are stored in S3 in the us-east-2 region. |
| 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. | All databases in Turso Cloud are encrypted at rest at the volume level, which Turso describes as part of its SOC 2 standards. |
| Customer-managed keys | Three KMS key types: an AWS owned key by default, an AWS managed key, or a customer managed key stored in your account that you own and fully control. AWS KMS charges apply for a customer managed key. | BYOK on Pro and Enterprise: each database can be encrypted with a key you supply, and Turso never sees or stores the keys. |
| 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 hold one of three roles - admin, member or viewer - and only an admin or owner can change a member's role. |
| Private networking / VPC | Clusters sit behind security groups with network access off by default; a non-public instance is reachable over Site-to-Site VPN or Direct Connect. DB clusters launch into a VPC at no additional cost. | AWS PrivateLink VPC endpoints keep traffic to Turso databases inside AWS's private network; offered in six AWS regions. |
| Dedicated infrastructure | With dedicated VPC tenancy an Aurora DB cluster runs on dedicated hardware; all Aurora PostgreSQL instance classes except burstable db.t3/db.t4g support it. | Pro and Enterprise can use their own S3 / S3-Express buckets so data lives in their infrastructure; compute in your own account is roadmap, not shipped. |
Where they differ.
Free tier
- Amazon Aurora
- No — capped Free plan plus time-limited credits
- Turso
- 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
- Turso Pricing ↗
“Start free, no credit card required.”
Read 2026-09-13 · official pricing · Report a correction
Kind of free offer
- Amazon Aurora
- Introductory free tier
- Turso
- 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
- Turso Pricing ↗
“Start free, no credit card required.”
Read 2026-09-13 · 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.
- Turso
- $4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58.
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
- Pricing — Turso ↗
“Developer $ 4.99 /month Get Developer Scaler $ 24.92 /month Get Scaler Pro $ 416.58 /month”
Read 2026-09-06 · 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.
- Turso
- Per database, metered on rows rather than compute time: 500 million rows read and 10 million written a month on the free plan, 2.5 billion and 25 million on Developer, with overage at $1 per billion rows read and $1 per million written.
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 — Turso ↗
“Monthly Rows Read Free 500 Million Developer 2.5 Billion + $1 / Billion Scaler 100 Billion + $0.80 / Billion [...] Monthly Rows Written Free 10 Million Developer 25 Million + $1 / Million”
Read 2026-09-06 · 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.
- Turso
- 9 GB on Developer, then $0.75 per GB. The free plan includes 5 GB; Scaler is 24 GB at $0.50 and Pro 50 GB at $0.45.
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 — Turso ↗
“Storage Free 5GB Developer 9GB + $0.75 / GB Scaler 24GB + $0.50 / GB Pro 50GB + $0.45 / GB”
Read 2026-09-06 · 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.
Six AWS locations in the Platform API's location list: Tokyo (ap-northeast-1), Mumbai (ap-south-1), Ireland (eu-west-1), N. Virginia (us-east-1), Ohio (us-east-2) and Oregon (us-west-2). Read from the documented GET /v1/locations sample response; the same six AWS regions are offered for PrivateLink.
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
- List Locations - Turso Platform API ↗
“"aws-ap-northeast-1" : "AWS AP NorthEast (Tokyo)" , "aws-ap-south-1" : "AWS AP South (Mumbai)" , "aws-eu-west-1" : "AWS EU West (Ireland)" , "aws-us-east-1" : "AWS US East (Virginia)" , "aws-us-east-2" : "AWS US East (Ohio)" , "aws-us-west-2" : "AWS US West (Oregon)"”
Read 2026-09-13 · official docs · 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.
- Turso
- SQLite, via libSQL — Turso's own fork. Not Postgres or MySQL, so the query surface and the client libraries differ from every other database on this site.
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
- Pricing — Turso ↗
“Embedded Replicas Database Branching Backups & Recovery Platform API Turso Database Quickstart”
Read 2026-09-06 · official site · 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.
- Turso
- Databases are archived after 10 days of inactivity on the free plan; an unarchive call through the CLI or Platform API brings the group back. Turso publishes no archival window for paid plans.
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
- Unarchive Group - Turso Platform API ↗
“Databases get archived after 10 days of inactivity for users on a free plan. You can unarchive inactive groups using the API.”
Read 2026-09-13 · official docs · Report a correction
Database branching
- Amazon Aurora
- Limited — clones, not a branch workflow
- Turso
- 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 — Turso ↗
“Embedded Replicas Database Branching Backups & Recovery [...] Do Database Branches cost money?”
Read 2026-09-06 · official site · 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.
- Turso
- 10 days on Developer. 1 day on the free plan, 30 days on Scaler and 90 days on Pro.
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
- Pricing — Turso ↗
“Point-In-Time Restore Free 1 day Developer 10 days Scaler 30 days Pro 90 days”
Read 2026-09-06 · official pricing · Report a correction
Read replicas
- Amazon Aurora
- Supported — 15 per cluster, a quota AWS will not raise
- Turso
- Limited — Embedded replicas run inside your app; managed multi-region Data Edge replica locations are deprecated for new users.
Sources (2) →Sources ↓
- Quotas and constraints for Amazon RDS — Amazon Relational Database Service User Guide ↗
“Read replicas per primary Each supported Region: 15 Yes The maximum number of read replicas per primary DB instance. This quota cant be adjusted for Amazon Aurora.”
Read 2026-09-09 · official docs · Report a correction
- Embedded Replicas - Turso Documentation ↗
“Embedded Replicas keep a local read replica of a Turso Cloud database: reads run locally from the file in microseconds, and writes are sent to the cloud primary and then reflected back to the replica.”
Read 2026-09-13 · 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.
- Turso
- Continuous rather than scheduled: backups are taken at every COMMIT and kept for the plan's restore window — 24 hours on Free, 10 days on Developer, 30 on Scaler, 90 on Pro. Turso publishes no separate backup retention setting.
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
- Point-in-Time Recovery - Turso Documentation ↗
“Free plan users can restore to any point in time within the last 24 hours. Developer, Scaler, and Pro users can restore to any point in time within the last 10, 30, or 90 days, respectively.”
Read 2026-09-13 · official docs · Report a correction
Rewind in place
- Amazon Aurora
- Limited — Aurora MySQL edition only
- Turso
- Not supported — PITR restores forward into a fresh database; the existing database cannot be rewound in place.
Sources (2) →Sources ↓
- Backtracking an Aurora DB cluster — Amazon Aurora User Guide ↗
“With Amazon Aurora MySQL-Compatible Edition, you can backtrack a DB cluster [...] Backtracking "rewinds" the DB cluster to the time you specify. [...] If you mistakenly perform a destructive action, such as a DELETE without a WHERE clause, you can backtrack the DB cluster to a time before the destructive action”
Read 2026-09-09 · official docs · Report a correction
- Point-in-Time Recovery - Turso Documentation ↗
“Restoring from a PITR creates a new database. You will need to update your application to use the new database connection string. [...] You cannot restore from a PITR to a database that already exists.”
Read 2026-09-13 · 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.
- Turso
- Volume-level encryption at rest is described as part of Turso's SOC 2 standards; the docs point to Turso's trust center for details.
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
- BYOK Encryption - Turso Documentation ↗
“All databases are encrypted-at-rest at the volume level in the Turso Cloud, as part of our SOC2 standards. See our trust center for details.”
Read 2026-09-13 · official docs · Report a correction
HIPAA
- Amazon Aurora
- Listed as a HIPAA-eligible service on AWS's own reference page.
- Turso
- Turso states it is HIPAA compliant and will provide a HIPAA compliance BAA letter to Pro plan and Enterprise users on request.
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
- Turso is for Healthcare ↗
“Turso is HIPAA compliant We can provide HIPAA compliance BAA letter for Pro plan and Enterprise users upon request”
Read 2026-09-13 · 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.
- Turso
- A database confined to EU locations never leaves the EU; the exception is backups, which are stored in S3 in the us-east-2 region.
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
- Turso's Trust Center - FAQ ↗
“By creating a database that only spans locations in the European Union, your data will never leave the European Union. The exception are backups. Backups are stored in S3, in the us-east-2 region.”
Read 2026-09-13 · 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.
- Turso
- All databases in Turso Cloud are encrypted at rest at the volume level, which Turso describes as part of its SOC 2 standards.
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
- BYOK Encryption - Turso Documentation ↗
“All databases are encrypted-at-rest at the volume level in the Turso Cloud, as part of our SOC2 standards.”
Read 2026-09-13 · official docs · Report a correction
Customer-managed keys
- Amazon Aurora
- Three KMS key types: an AWS owned key by default, an AWS managed key, or a customer managed key stored in your account that you own and fully control. AWS KMS charges apply for a customer managed key.
- Turso
- BYOK on Pro and Enterprise: each database can be encrypted with a key you supply, and Turso never sees or stores the keys.
Sources (2) →Sources ↓
- Encrypting Amazon Aurora resources — Amazon Aurora User Guide ↗
“However, you can choose from three encryption types based on your security and compliance needs: [...] Customer managed key (CMK) – The key is stored in your account and is created, owned, and managed by you. You have full control over the KMS key (AWS KMS charges apply).”
Read 2026-09-13 · official docs · Report a correction
- BYOK Encryption - Turso Documentation ↗
“For Pro, and Enterprise customers, there is the option to encrypt the databases with a key that you provide (Bring-Your-Own-Key Encryption, or BYOK) [...] Turso never sees or stores your encryption keys.”
Read 2026-09-13 · official docs · 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.
- Turso
- Organization members hold one of three roles - admin, member or viewer - and only an admin or owner can change a member's role.
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
- Update Member Role - Turso Platform API ↗
“The new role to assign to the member. Available options : admin , member , viewer [...] updating member roles is only allowed for admin or owner”
Read 2026-09-13 · official docs · Report a correction
Private networking / VPC
- Amazon Aurora
- Clusters sit behind security groups with network access off by default; a non-public instance is reachable over Site-to-Site VPN or Direct Connect. DB clusters launch into a VPC at no additional cost.
- Turso
- AWS PrivateLink VPC endpoints keep traffic to Turso databases inside AWS's private network; offered in six AWS regions.
Sources (2) →Sources ↓
- Infrastructure security in Amazon Aurora — Amazon Aurora User Guide ↗
“Security groups control the access that traffic has in and out of a DB cluster . By default, network access is turned off to a DB cluster . [...] If your DB instance is in a VPC but isn't publicly accessible, you can also use an AWS Site-to-Site VPN connection or an Direct Connect connection to access it from a private network.”
Read 2026-09-13 · official docs · Report a correction
- Turso Cloud Private Endpoints ↗
“Set up an AWS VPC endpoint to securely access Turso databases through AWS PrivateLink, keeping all traffic within AWS's private network. [...] us-east-1 us-east-2 us-west-2 eu-west-1 ap-south-1 ap-northeast-1”
Read 2026-09-13 · official docs · Report a correction
Dedicated infrastructure
- Amazon Aurora
- With dedicated VPC tenancy an Aurora DB cluster runs on dedicated hardware; all Aurora PostgreSQL instance classes except burstable db.t3/db.t4g support it.
- Turso
- Pro and Enterprise can use their own S3 / S3-Express buckets so data lives in their infrastructure; compute in your own account is roadmap, not shipped.
Sources (2) →Sources ↓
- Security with Amazon Aurora PostgreSQL - Amazon Aurora User Guide ↗
“The supported VPC tenancy depends on the DB instance class used by your Aurora PostgreSQL DB clusters. With default VPC tenancy, the DB cluster runs on shared hardware. With dedicated VPC tenancy, the DB cluster runs on a dedicated hardware instance. [...] All other Aurora PostgreSQL DB instance classes support both default and dedicated VPC tenancy.”
Read 2026-09-13 · official docs · Report a correction
- Durability Guarantees - Turso Documentation ↗
“Pro and Enterprise customers can use their own S3 / S3-express buckets, guaranteeing that data lives inside their infrastructure. In our future roadmap, compute will also be runnable inside your account, for a full BYOC solution”
Read 2026-09-13 · official docs · 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 Turso?
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.
Turso: $4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58.
Free tier: Amazon Aurora or Turso?
Amazon Aurora: No — capped Free plan plus time-limited credits
Turso: Yes
Storage (entry plan): Amazon Aurora or Turso?
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.
Turso: 9 GB on Developer, then $0.75 per GB. The free plan includes 5 GB; Scaler is 24 GB at $0.50 and Pro 50 GB at $0.45.
Should I choose Amazon Aurora or Turso?
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 Turso if Applications that want a database per tenant or per user — 100 databases on the free plan and unlimited above it make that a shape you can actually build.
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.