Amazon Aurora vs TigerData
SEPT 2026 auditA comparison of Amazon Aurora and TigerData 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 TigerData if…
Time-series and analytics workloads that want to stay in Postgres — TimescaleDB's compression is the reason the storage line is affordable at volume.
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.
- TigerData: The advertised storage price assumes 5x compression, so a workload that does not compress that well pays materially more than the figure suggests.
Neither quite fits? Every other option, ranked by iScore: Amazon Aurora alternatives · TigerData alternatives
22 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
TigerData 0
At a glance.
| Criterion | Amazon Aurora | TigerData |
|---|---|---|
| Pricing | ||
| Free tier | No — capped Free plan plus time-limited credits | Yes — Free services are in beta, us-east-1 only, and go read-only at the storage limit. |
| 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. | Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month. |
| 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. | Compute and storage are billed separately and hourly rather than as one plan price — compute from $30 a month, storage at $0.177 per GB-month, with the headline storage figure resting on an assumed 5x compression ratio. |
| 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. | Up to 16 TB per service on the Performance (entry) plan, billed on actual usage; 64 TB on Scale and Enterprise |
| Memory (entry plan) | No plan tiers: memory comes with the Aurora Capacity Unit, and AWS states 1 ACU has approximately 2 GiB of memory. The smallest capacity you can set is 0.5 ACUs; the AWS Free Tier Free plan caps a cluster at 4 ACUs and the Paid plan at 256. | Up to 32 GB per service on the Performance (entry) plan; 128 GB on Scale and 256 GB on Enterprise |
| Execution | ||
| Managed connection pooling | Supported — through Amazon RDS Proxy, a separate feature of the service | Supported — pgBouncer pooler added per service in Console, in session or transaction mode. |
| 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. | 13 AWS regions (US, Canada, Sao Paulo, Ireland, London, Frankfurt, Zurich, Mumbai, Singapore, Sydney, Tokyo) and 4 Azure regions for Tiger Cloud services |
| 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. | Enterprise SLAs, with no percentage published on the pricing page. |
| 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 with TimescaleDB, aimed at time-series, real-time analytics and events. A self-managed edition exists for on-prem and private cloud. |
| 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. | max_connections settable 25-500 on services from 0.5 CPU / 2 GiB to 4 CPU / 16 GiB, and 25-2000 from 8 CPU / 32 GiB up; fixed at 25 on shared CPU |
| 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. | Billed while running: all active standard services are charged even when not in use, and unused ones must be paused or deleted manually |
| Database branching | Limited — clones, not a branch workflow | Supported — Service forks, created at current state, last snapshot, or a timestamp in the plan recovery window. |
| 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. | 3 days on Performance, with cross-region backups available for disaster recovery on higher tiers. |
| 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. | One full backup weekly plus daily incrementals, kept for the plan recovery period; Enterprise can set 14-180 days; cross-region copies always kept 14 days |
| Rewind in place | Limited — Aurora MySQL edition only | Not supported — Recovery is to a PITR fork you point the app at; the original service stays untouched. |
| 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; the annual report is available to customers on the Scale or Enterprise pricing plans by support ticket. |
| HIPAA | Listed as a HIPAA-eligible service on AWS's own reference page. | The Tiger Cloud Enterprise plan is Health Insurance Portability and Accountability Act (HIPAA) compliant. Enterprise plan only. |
| 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. | Complies with EU GDPR; all customer data is processed under Tiger Data's GDPR-compliant Data Processor Addendum, which applies to all customers. |
| 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. | Both active databases and backups are encrypted at rest (and in transit) with the industry-standard AES-256 algorithm. |
| 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. | Project-level role-based access with Owner, Admin, Developer and Viewer roles; database-level roles are managed separately per service. |
| 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. | VPC peering leaves no public internet access to the service; AWS PrivateLink private endpoints route traffic over the AWS network. |
| 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. | Managed Service for TimescaleDB (TimescaleDB hosted with Aiven): each service virtual machine is dedicated to a single customer, never multi-tenanted. Read on the MST security docs; scope is MST, not the Tiger Cloud platform. |
Where they differ.
Free tier
- Amazon Aurora
- No — capped Free plan plus time-limited credits
- TigerData
- Yes — Free services are in beta, us-east-1 only, and go read-only at the storage limit.
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
- About Tiger Cloud services | Tiger Data Docs ↗
“You create free and standard services in Tiger Console. A standard service comes with the full range of features according to your pricing plan. A free service comes at zero cost and gives you limited features and resources. [...] Free services come with pre-configured CPU and memory, are hosted in us-east-1 region, and offer limited resources with a basic feature scope.”
Read 2026-09-13 · official docs · Report a correction
Kind of free offer
- Amazon Aurora
- Introductory free tier
- TigerData
- 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
- About Tiger Cloud services | Tiger Data Docs ↗
“You create free and standard services in Tiger Console. A standard service comes with the full range of features according to your pricing plan. A free service comes at zero cost and gives you limited features and resources. [...] Free services come with pre-configured CPU and memory, are hosted in us-east-1 region, and offer limited resources with a basic feature scope.”
Read 2026-09-13 · official docs · 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.
- TigerData
- Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month.
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 — TigerData ↗
“Performance Compute starts at $ 30 / month Storage priced at $0.177 / GB-month [...] Scale Most popular Compute starts at $ 36 / 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.
- TigerData
- Compute and storage are billed separately and hourly rather than as one plan price — compute from $30 a month, storage at $0.177 per GB-month, with the headline storage figure resting on an assumed 5x compression ratio.
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 — TigerData ↗
“Pay as you go hourly Compute starts at $30/month Storage priced at $0.177/GB-month [...] Effective storage price is based on 5x compression (average customer savings).”
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.
- TigerData
- Up to 16 TB per service on the Performance (entry) plan, billed on actual usage; 64 TB on Scale and Enterprise
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
- Billing and account management | Tiger Data Docs ↗
“Storage limit per service Up to 16 TB Up to 64 TB Up to 64 TB”
Read 2026-09-13 · official pricing · Report a correction
Memory (entry plan)
- Amazon Aurora
- No plan tiers: memory comes with the Aurora Capacity Unit, and AWS states 1 ACU has approximately 2 GiB of memory. The smallest capacity you can set is 0.5 ACUs; the AWS Free Tier Free plan caps a cluster at 4 ACUs and the Paid plan at 256.
- TigerData
- Up to 32 GB per service on the Performance (entry) plan; 128 GB on Scale and 256 GB on Enterprise
Sources (2) →Sources ↓
- Amazon Aurora Pricing — Amazon Web Services ↗
“1 ACU has approximately 2 GiB of memory with corresponding CPU and networking, similar to that used in Aurora provisioned instances. [...] With Aurora serverless , the minimum database capacity you can set is 0.5 ACUs. [...] 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-13 · official pricing · Report a correction
- Billing and account management | Tiger Data Docs ↗
“Memory limit per service Up to 32 GB Up to 128 GB Up to 256 GB”
Read 2026-09-13 · official pricing · Report a correction
Regions
- Amazon Aurora
- 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.
- TigerData
- 13 AWS regions (US, Canada, Sao Paulo, Ireland, London, Frankfurt, Zurich, Mumbai, Singapore, Sydney, Tokyo) and 4 Azure regions for Tiger Cloud services
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
- Supported regions | Tiger Data Docs ↗
“Tiger Cloud services run in the following Amazon Web Services (AWS) regions: [...] Tiger Cloud services run in the following Microsoft Azure regions:”
Read 2026-09-13 · 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.
- TigerData
- Enterprise SLAs, with no percentage published on the pricing page.
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
- Tiger Data Pricing ↗
“mission-critical reliability and monitoring cross-region backups for disaster recovery enterprise SLAs production support (24x7, 1 hour response time for sev 1 issues)”
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.
- TigerData
- PostgreSQL with TimescaleDB, aimed at time-series, real-time analytics and events. A self-managed edition exists for on-prem and private cloud.
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 — TigerData ↗
“TimescaleDB Enterprise Self-managed TimescaleDB for on-prem, edge and private cloud Open source TimescaleDB Time-series, real-time analytics and events”
Read 2026-09-06 · official site · 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.
- TigerData
- max_connections settable 25-500 on services from 0.5 CPU / 2 GiB to 4 CPU / 16 GiB, and 25-2000 from 8 CPU / 32 GiB up; fixed at 25 on shared CPU
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
- Connection pooling | Tiger Data Docs ↗
“You can set max_connections within the following ranges, based on your service memory and CPU configuration: Configuration Minimum Maximum Shared memory and CPU 25 25 From 0.5 CPU / 2 GiB to 4 CPU / 16 GiB 25 500 8 CPU / 32 GiB and more 25 2000”
Read 2026-09-13 · official docs · 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.
- TigerData
- Billed while running: all active standard services are charged even when not in use, and unused ones must be paused or deleted manually
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
- Billing and account management | Tiger Data Docs ↗
“You are charged for all active standard services in your account, even if you are not actively using them. To reduce costs, pause or delete your unused services.”
Read 2026-09-13 · official pricing · Report a correction
Database branching
- Amazon Aurora
- Limited — clones, not a branch workflow
- TigerData
- Supported — Service forks, created at current state, last snapshot, or a timestamp in the plan recovery window.
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
- Fork services | Tiger Data Docs ↗
“Fork a service to create isolated database branches for testing and development [...] A fork is an exact copy of a service at a specific point in time, with its own independent data and configuration”
Read 2026-09-13 · official docs · 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.
- TigerData
- 3 days on Performance, with cross-region backups available for disaster recovery on higher tiers.
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 — TigerData ↗
“Point-in-time-recovery to 3 days Performance Insights Basic support (9-5 ET)”
Read 2026-09-06 · official pricing · 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.
- TigerData
- One full backup weekly plus daily incrementals, kept for the plan recovery period; Enterprise can set 14-180 days; cross-region copies always kept 14 days
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
- Back up and recover services | Tiger Data Docs ↗
“Tiger Cloud automatically creates one full backup every week, and incremental backups every day in the same region as your service. [...] on Enterprise you can set a retention period of up to 180 days for each service. [...] Cross-region backups are always kept for 14 days.”
Read 2026-09-13 · official docs · Report a correction
Rewind in place
- Amazon Aurora
- Limited — Aurora MySQL edition only
- TigerData
- Not supported — Recovery is to a PITR fork you point the app at; the original service stays untouched.
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
- Back up and recover services | Tiger Data Docs ↗
“you recover it with a point-in-time recovery (PITR) fork: a copy of your service as it was at a moment before the problem started. You then point your app at the fork. The original service stays untouched.”
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.
- TigerData
- SOC 2 Type 2 compliant; the annual report is available to customers on the Scale or Enterprise pricing plans by support ticket.
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
- About security in Tiger Cloud | Tiger Data Docs ↗
“Tiger Cloud is SOC 2 Type 2 compliant. [...] The annual SOC 2 report is available to customers on the Scale or Enterprise pricing plans. Open a support ticket to get access to it.”
Read 2026-09-13 · official docs · Report a correction
HIPAA
- Amazon Aurora
- Listed as a HIPAA-eligible service on AWS's own reference page.
- TigerData
- The Tiger Cloud Enterprise plan is Health Insurance Portability and Accountability Act (HIPAA) compliant. Enterprise plan only.
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
- About security in Tiger Cloud | Tiger Data Docs ↗
“The Tiger Cloud Enterprise plan is Health Insurance Portability and Accountability Act (HIPAA) compliant.”
Read 2026-09-13 · official docs · 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.
- TigerData
- Complies with EU GDPR; all customer data is processed under Tiger Data's GDPR-compliant Data Processor Addendum, which applies to all customers.
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
- About security in Tiger Cloud | Tiger Data Docs ↗
“Tiger Data complies with the European Union's General Data Protection Regulation (GDPR) [...] All customer data is processed in accordance with Tiger Data's GDPR-compliant”
Read 2026-09-13 · official docs · 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.
- TigerData
- Both active databases and backups are encrypted at rest (and in transit) with the industry-standard AES-256 algorithm.
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
- About security in Tiger Cloud | Tiger Data Docs ↗
“Your data on Tiger Cloud is encrypted both in transit and at rest. Both active databases and backups are encrypted. [...] Data encryption uses the industry-standard AES-256 algorithm.”
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.
- TigerData
- Project-level role-based access with Owner, Admin, Developer and Viewer roles; database-level roles are managed separately per service.
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
- Control user access to projects | Tiger Data Docs ↗
“Tiger Cloud creates a project with built-in role-based access [...] A Developer can build, deploy, and operate services across projects, but does not have administrative privileges over users, roles, or billing.”
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.
- TigerData
- VPC peering leaves no public internet access to the service; AWS PrivateLink private endpoints route traffic over the AWS network.
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
- About security in Tiger Cloud | Tiger Data Docs ↗
“When using VPC peering, no public Internet-based access is provided to the service. [...] Tiger Cloud enables you to connect to your services through a private endpoint in AWS using AWS PrivateLink.”
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.
- TigerData
- Managed Service for TimescaleDB (TimescaleDB hosted with Aiven): each service virtual machine is dedicated to a single customer, never multi-tenanted. Read on the MST security docs; scope is MST, not the Tiger Cloud platform.
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
- Security (Managed Service for TimescaleDB) | Tiger Data Docs ↗
“Your MST services are located on one or more virtual machines. Each virtual machine is dedicated to a single customer, and is never multi-tenanted.”
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 TigerData?
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.
TigerData: Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month.
Free tier: Amazon Aurora or TigerData?
Amazon Aurora: No — capped Free plan plus time-limited credits
TigerData: Yes — Free services are in beta, us-east-1 only, and go read-only at the storage limit.
Storage (entry plan): Amazon Aurora or TigerData?
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.
TigerData: Up to 16 TB per service on the Performance (entry) plan, billed on actual usage; 64 TB on Scale and Enterprise
Should I choose Amazon Aurora or TigerData?
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 TigerData if Time-series and analytics workloads that want to stay in Postgres — TimescaleDB's compression is the reason the storage line is affordable at volume.
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.