# TigerData

Canonical: https://inetgeek.com/databases/tigerdata/

Managed TimescaleDB — Postgres for time-series and real-time analytics — priced with compute and storage billed separately.

## Who it suits

Time-series and analytics workloads that want to stay in Postgres — TimescaleDB's compression is the reason the storage line is affordable at volume.

Consider something else if The advertised storage price assumes 5x compression, so a workload that does not compress that well pays materially more than the figure suggests.

## iScore

69 / 100 (80% interval 63–75), rank 4 of 14 in databases — interval overlaps the next rank, so this is an ordering, not a finding.

inetGeek's own reading, computed from sourced facts against category peers by disclosed rules. Not a provider claim. Intervals are 80%; a provider with few documented facts is pulled toward the category middle rather than scored on what little is known.
Read this score with care:
- Capacity and limits is thin: 1 of 7 criteria are scored, so it sits near the category middle with a wide interval (40–52). Read the interval, not the point.
- Adoption is thin: 0 of 1 criteria are scored, so it sits near the category middle with a wide interval (8–99). Read the interval, not the point.
- Documented but not scored, because the page states it as text with no comparable number or a yes/limited/no (a one-time, usage-based or other-vendor price, or a per-site choice): backup_retention, entry_plan_memory, entry_plan_storage, max_connections, read_replicas, regions. Read them on the provider page; the score neither rewards nor penalises what it could not compare.

Method: https://inetgeek.com/iscore/. Full output with every criterion's basis: https://inetgeek.com/scores.json. Every databases peer ranked: https://inetgeek.com/databases/tigerdata/alternatives/

- Price: 70 (58–81), weight 25%, 4 of 6 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: egress_overage_price, free_expires
- Capacity and limits: 46 (40–52), weight 20%, 1 of 7 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: backup_retention, entry_plan_memory, entry_plan_storage, max_connections, read_replicas, regions
- Capabilities: 75 (69–82), weight 20%, 4 of 5 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: scale_to_zero
- Trust and compliance: 80 (74–86), weight 15%, 9 of 13 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: audit_logs, customer_managed_keys, iso27001, pci_dss
- Evidence: 98 (98–98), weight 10%, 4 of 4 criteria scored
- Adoption: 53 (8–99), weight 10%, 0 of 1 criteria scored

## What the documentation says

### Pricing

- Free tier: Yes — Free services are in beta, us-east-1 only, and go read-only at the storage limit. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/service-management), read 2026-09-13)
- Kind of free offer: Free tier ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/service-management), read 2026-09-13)
- Credit card to start: No ([source](https://www.tigerdata.com/pricing), read 2026-09-21)
- Entry paid plan: Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month. ([source](https://www.tigerdata.com/pricing), read 2026-09-06)
- Pricing model: 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. ([source](https://www.tigerdata.com/pricing), read 2026-09-06)

### Limits

- Storage (entry plan): Up to 16 TB per service on the Performance (entry) plan, billed on actual usage; 64 TB on Scale and Enterprise ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/pricing-and-account-management), read 2026-09-13)
- Memory (entry plan): Up to 32 GB per service on the Performance (entry) plan; 128 GB on Scale and 256 GB on Enterprise ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/pricing-and-account-management), read 2026-09-13)

### Execution

- Managed connection pooling: Supported — pgBouncer pooler added per service in Console, in session or transaction mode. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/service-management/connection-pooling), read 2026-09-13)

### Infrastructure

- Regions: 13 AWS regions (US, Canada, Sao Paulo, Ireland, London, Frankfurt, Zurich, Mumbai, Singapore, Sydney, Tokyo) and 4 Azure regions for Tiger Cloud services ([source](https://www.tigerdata.com/docs/get-started/supported-regions), read 2026-09-13)
- Uptime SLA: Enterprise SLAs, with no percentage published on the pricing page. ([source](https://www.tigerdata.com/pricing), read 2026-09-14)

### Data

- Engine: PostgreSQL with TimescaleDB, aimed at time-series, real-time analytics and events. A self-managed edition exists for on-prem and private cloud. ([source](https://www.tigerdata.com/pricing), read 2026-09-06)
- Connection limit: 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 ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/service-management/connection-pooling), read 2026-09-13)
- When idle: Billed while running: all active standard services are charged even when not in use, and unused ones must be paused or deleted manually ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/pricing-and-account-management), read 2026-09-13)
- Database branching: Supported — Service forks, created at current state, last snapshot, or a timestamp in the plan recovery window. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/service-management/fork-services), read 2026-09-13)
- Point-in-time recovery: 3 days on Performance, with cross-region backups available for disaster recovery on higher tiers. ([source](https://www.tigerdata.com/pricing), read 2026-09-06)
- Read replicas: Supported ([source](https://www.tigerdata.com/pricing), read 2026-09-06)
- Backup retention: 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 ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/high-availability/backup-restore), read 2026-09-13)
- Rewind in place: Not supported — Recovery is to a PITR fork you point the app at; the original service stays untouched. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/high-availability/backup-restore), read 2026-09-13)

### Storage

- Storage price: $0.177 per GB-month on Performance and $0.212 on Scale. TigerData notes the effective price assumes 5x compression, which is an average rather than a guarantee. ([source](https://www.tigerdata.com/pricing), read 2026-09-06)

### Support

- Support on entry paid plan: Basic support, 9-5 ET, on the entry plan. Enterprise adds production support at 24x7. ([source](https://www.tigerdata.com/pricing), read 2026-09-14)
- Response time commitment: 1 hour for Sev 1, on Enterprise only. The entry plan publishes opening hours, 9-5 ET, which is not a response commitment. ([source](https://www.tigerdata.com/pricing), read 2026-09-14)

### Compliance

- SOC 2: SOC 2 Type 2 compliant; the annual report is available to customers on the Scale or Enterprise pricing plans by support ticket. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/security/overview), read 2026-09-13)
- HIPAA: The Tiger Cloud Enterprise plan is Health Insurance Portability and Accountability Act (HIPAA) compliant. Enterprise plan only. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/security/overview), read 2026-09-13)
- GDPR / data residency: Complies with EU GDPR; all customer data is processed under Tiger Data's GDPR-compliant Data Processor Addendum, which applies to all customers. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/security/overview), read 2026-09-13)
- Encryption at rest: Both active databases and backups are encrypted at rest (and in transit) with the industry-standard AES-256 algorithm. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/security/overview), read 2026-09-13)
- Role-based access control: Project-level role-based access with Owner, Admin, Developer and Viewer roles; database-level roles are managed separately per service. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/security/members), read 2026-09-13)
- Private networking / VPC: VPC peering leaves no public internet access to the service; AWS PrivateLink private endpoints route traffic over the AWS network. ([source](https://www.tigerdata.com/docs/deploy/tiger-cloud/tiger-cloud-aws/security/overview), read 2026-09-13)
- Dedicated infrastructure: 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. ([source](https://www.tigerdata.com/docs/deploy/mst/security), read 2026-09-13)

## Compared with

- [TigerData vs Neon](https://inetgeek.com/compare/neon-vs-tigerdata/)
- [TigerData vs Aiven](https://inetgeek.com/compare/aiven-vs-tigerdata/)
- [TigerData vs Amazon Aurora](https://inetgeek.com/compare/amazon-aurora-vs-tigerdata/)
- [TigerData vs Amazon RDS](https://inetgeek.com/compare/amazon-rds-vs-tigerdata/)
- [TigerData vs Crunchy Bridge](https://inetgeek.com/compare/crunchy-bridge-vs-tigerdata/)
- [TigerData vs Neo4j](https://inetgeek.com/compare/neo4j-vs-tigerdata/)
- [TigerData vs Nile](https://inetgeek.com/compare/nile-vs-tigerdata/)
- [TigerData vs PlanetScale](https://inetgeek.com/compare/planetscale-vs-tigerdata/)
- [TigerData vs Prisma Postgres](https://inetgeek.com/compare/prisma-postgres-vs-tigerdata/)
- [TigerData vs ScaleGrid](https://inetgeek.com/compare/scalegrid-vs-tigerdata/)
- [TigerData vs Supabase](https://inetgeek.com/compare/supabase-vs-tigerdata/)
- [TigerData vs Turso](https://inetgeek.com/compare/tigerdata-vs-turso/)