Reliability
Backup retention, point-in-time recovery, and read replicas — the three questions that decide how much data a mistake can cost you, and whether you can read from a database without adding load to the one your app writes to. Every figure is sourced from the provider's own documentation; a blank cell means undocumented, not "no."
| Provider | Backup retention | Point-in-time recovery | Read replicas |
|---|---|---|---|
| Aiven | By plan: none on Hobbyist, 2 days on Startup, 14 on Business, 30 on Premium. The magnitude is Startup's 2 days, the entry paid plan. Aiven's high-availability page states 2 days for Hobbyist where the backups page states none — the backups page is the more specific of the two and is what is recorded here. | Bounded by the plan's backup history, so 2 days on the entry paid plan and 30 at the top. Granularity is fine within that: full backups daily with write-ahead logs copied every 5 minutes or per new file, whichever comes first. | Supported |
| Alibaba Cloud | ECS automatic snapshot policies: retention set in days, or snapshots kept permanently, with expired snapshots deleted automatically; several policies can run on one disk, and snapshots can be replicated to another region with their own retention. | Not documented | Not documented |
| 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. | 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. | Supported — 15 per cluster, a quota AWS will not raise |
| Amazon RDS | Between 0 and 35 days, set per DB instance; 0 disables automated backups entirely. The default depends on how the instance was created — one day via the API or CLI, seven days via the console — so there is no single default to quote. Multi-AZ DB clusters cannot be set below 1 day. | Any point inside the configured backup retention period, so up to 35 days. Transaction logs are uploaded to S3 every five minutes, which is what bounds how close to now the latest restorable time can be. | Supported — 15 per primary, raisable on request |
| Civo | Documented only for CivoStack Enterprise Private Regions: instance snapshots on demand, and snapshot schedules (minimum interval 10 minutes) that keep at most 10 snapshots per resource, deleting the oldest. No instance backup product is described for the public cloud, and Civo's terms make the backup policy for instances the customer's responsibility. | Not documented | Not documented |
| Cloudways | Automated off-site server backups run daily and are kept for one week by default. Retention can be set from 1 to 4 weeks. Off-site backup storage is billed at $0.033/GB per server. | Not documented | Not documented |
| Crunchy Bridge | 10 days, included in the cluster price rather than sold as a tier, and extendable by configuring additional daily, weekly, monthly and yearly backups to keep. | Any minute inside the 10 days of retained backups. The WAL is streamed every 60 seconds or 16 MB, whichever comes first, and a restore produces a fork of the cluster rather than replacing it. | Supported |
| DreamHost | Daily automated backups on every shared plan. DreamHost does not state how many are kept. | Not documented | Not documented |
| Firebase | No automatic backups: scheduled backups are a Blaze-plan feature you configure, with up to one daily and one weekly schedule per database and a retention period you set of up to 14 weeks. Backup storage and restores are billed, with no free quota. | 7 days once point-in-time recovery is enabled; it is off by default and PITR data is billed as storage. Without PITR, documents can still be read at any timestamp within the past hour. | Not documented |
| Flywheel | Nightly backups. Flywheel does not state a retention period on the pricing page. | Not documented | Not documented |
| Hostinger | Weekly backups on the Premium plan; daily on Unlimited. Hostinger does not state how many are kept. | Not documented | Not documented |
| Hostinger VPS | Automatic weekly backups included, plus manual snapshots. Hostinger does not state how many weekly backups are kept. | Not documented | Not documented |
| IONOS VPS | No backups included. The optional Cloud Backup package (from $0.065/GB/month on the VPS page) lets the customer set the retention period in the backup schedule; IONOS states no default or maximum. | Not documented | Not documented |
| Kamatera | 14 days: the paid daily-backup add-on backs a server up once a day at 00:00 (by data-centre location) and keeps each backup for 14 days. | Not documented | Not documented |
| Neo4j | Daily backups, 7-day retention on the entry-paid (Professional) tier. Business Critical adds 30-day retention with hourly point-in-time restore; Virtual Dedicated Cloud gets hourly backups with 60-day retention. | Not included on the entry-paid (Professional) tier — point-in-time restore is a Business Critical feature, with hourly granularity and 30-day retention. | Limited — Secondaries are a Business Critical and Virtual Dedicated Cloud feature; not on Free or Professional. |
| Neon | 1 day of history on paid plans by default and 6 hours on Free, configurable up to 7 days on Launch or 30 days on Scale. Neon notes that widening the window raises storage cost, so the ceiling is a paid choice rather than an included allowance. | History window of 6 hours up to 1 GB-month on Free, up to 7 days on Launch, up to 30 days on Scale | Supported |
| Nhost | Automated backups and point-in-time recovery from Pro ($25/month). The free Starter plan lists neither. | Not documented | Not documented |
| Nile | Three backups taken daily; restore is request-based through support and available on paid tiers only. No retention window is published. | Not documented | Not documented |
| Oracle Cloud | Block Volume backup policies: Oracle-defined Bronze (monthly, kept twelve months; yearly, kept five years), Silver (adds weekly, kept four weeks) and Gold (adds daily, kept seven days), or user-defined policies with configurable retention. | Not documented | Not documented |
| PlanetScale | Automatic backups every 12 hours on production and development branches, retained 2 days by default. Custom schedules and manual backups can set a longer period, and are charged for it. | Point-in-time recovery through write-ahead log archiving. WAL is kept for as long as the oldest backup, so the default schedule gives a 2-day window and a longer retention extends it. | Supported — Two replicas come with the High Availability shape, across three availability zones. |
| Pressable | Hourly and daily backups. Pressable does not state a retention period on the pricing page. | Not documented | Not documented |
| Prisma Postgres | Daily backups with 7-day retention on Starter and Pro, 30 days on Business. The free plan has none. | Not documented | Not documented |
| RackNerd | None by default: VPS services do not include managed backups unless a separate backup service is purchased, and RackNerd states no retention period for one. | Not documented | Not documented |
| rsync.net | 7 daily snapshots below 10 TB, and 7 days plus 4 weeks above it. Snapshots are taken and held by rsync.net rather than scheduled by the customer, though the page says every account can set a custom schedule. | Not documented | Not documented |
| ScaleGrid | Up to five backups per deployment on ScaleGrid's dedicated hosting plans. | PostgreSQL PITR: backups every 10 minutes by default, transaction logs retained 7 days; supported on Azure, DigitalOcean, EC2 and OCI only. | Supported — Converting a standalone deployment to a replica set: 2 + 1 quorum or 3 nodes, in datacenter regions you pick. |
| SimpleBackups | Customer-defined on every paid tier, described only as flexible retention and schedule rather than as a fixed number of days. | Not documented | Not documented |
| SnapShooter | Daily only on the entry plan; daily, weekly and monthly rotation from the $39 Startup plan upward. Retention rotation is a paid feature rather than a default. | Not documented | Not documented |
| 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. | 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. | Supported |
| 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 | 3 days on Performance, with cross-region backups available for disaster recovery on higher tiers. | Supported |
| 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. | 10 days on Developer. 1 day on the free plan, 30 days on Scaler and 90 days on Pro. | Limited — Embedded replicas run inside your app; managed multi-region Data Edge replica locations are deprecated for new users. |
| UpCloud | Simple Backup plans, charged at +10% to +60% of the server plan price, keep daily backups for 1 or 7 days, weekly backups for 4 weeks and monthly backups for 12 months. Flexible Backups use a custom schedule with retention from 1 day up to 3 years. On-demand backups are kept until deleted. | Not documented | Not documented |
Sources (45) →Sources ↓
- Aiven for PostgreSQL® backups — Aiven docs ↗
“Backup retention time by plan The number of stored backups and the backup retention time depends on the service plan that you have selected. Plan Type Backup Retention Time Hobbyist None Startup 2 days Business 14 days Premium 30 days”
Read 2026-09-09 · official docs
- Use read replicas — Aiven for PostgreSQL® — Aiven docs ↗
“Create and use Aiven for PostgreSQL® read-only replicas Use Aiven for PostgreSQL® read-only replicas to reduce the load on the primary server and optimize query response”
Read 2026-09-09 · official docs
- Automatic snapshot policy - Elastic Compute Service - Alibaba Cloud Documentation Center ↗
“Custom retention with automatic deletion on expiration Set a retention period in days, or choose to retain snapshots permanently. Snapshots are automatically deleted upon expiration without manual intervention [...] After cross-region replication is enabled, snapshots are periodically replicated to the destination region, and you can set a separate retention period for the new snapshots in the destination region.”
Read 2026-09-27 · official docs
- 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
- 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
- Backup retention period — Amazon Relational Database Service User Guide ↗
“If you create a DB instance using the Amazon RDS API or the AWS CLI and if you don't set the backup retention period, the default backup retention period is one day. If you create a DB instance using the console, the default backup retention period is seven days. [...] You can set the backup retention period of a DB instance to between 0 and 35 days. Setting the backup retention period to 0 disables automated backups. For a Multi-AZ DB cluster, you can set the backup retention period to between 1 and 35 days.”
Read 2026-09-09 · official docs
- Restoring a DB instance to a specified time for Amazon RDS — Amazon Relational Database Service User Guide ↗
“RDS uploads transaction logs for DB instances to Amazon S3 every five minutes. To see the latest restorable time for a DB instance, use the AWS CLI describe-db-instances command and look at the value returned in the LatestRestorableTime field for the DB instance. [...] You can restore to any point in time within your backup retention period.”
Read 2026-09-09 · official docs
- Snapshot schedules - Cloud API Documentation - Civo.com ↗
“Where configured on a CivoStack Enterprise Private Region, users can create schedules of snapshots [...] If the schedule ends up creating a snapshot exceeding the maximum number, the oldest snapshot is deleted. Maximum of 10 .”
Read 2026-09-27 · official docs
- How to Configure a Server-level Backup | Cloudways Help Center ↗
“Those default preferences include taking the server-level backup at any time between 1 am to 5 am (UTC) daily and retaining it for a week. [...] Backup Retention: Set Backup Retention from 1 week to 4 weeks.”
Read 2026-09-27 · official docs
- Backups — Crunchy Bridge Documentation ↗
“10 days of these backups will be retained by the platform automatically. [...] By default, Crunchy Bridge automatically captures and retains the most recent 10 days' worth of backups for each cluster. That is included in the price of each cluster.”
Read 2026-09-09 · official docs
- Read replicas — Crunchy Bridge Documentation ↗
“Your read replica in Crunchy Bridge is required to be the same storage size, but can be a different instance size. You can also provision read replicas across regions and infrastructure provider if you wish to have greater resilience should a specific cloud provider or region fail.”
Read 2026-09-09 · official docs
- Web Hosting — DreamHost ↗
“Web Hosting Launch [...] Daily Automated Backups”
Read 2026-09-06 · official pricing
- Back up and restore data | Firestore | Firebase ↗
“Backups let you configure backup schedules to take daily or weekly backups of the specified database. [...] This feature requires the Blaze pricing plan. [...] For each database, you can configure up to one daily backup schedule and up to one weekly backup schedule. [...] Set this to a value up to 14 weeks”
Read 2026-09-25 · official docs
- Point-in-time recovery (PITR) overview | Firestore | Firebase ↗
“PITR data is retained for 7 days in the PITR window. [...] The PITR feature is disabled by default. [...] Regardless of whether PITR is enabled or not, you can read (but not export) documents at any microsecond-granularity timestamp within the past hour”
Read 2026-09-25 · official docs
- WordPress Hosting Pricing and Plans — Flywheel ↗
“Nightly backups”
Read 2026-09-06 · official pricing
- Web Hosting — Hostinger ↗
“Premium [...] Free weekly backups [...] Unlimited [...] Daily backups + easy data restore”
Read 2026-09-06 · official pricing
- VPS Hosting — Hostinger ↗
“Keep your VPS hosting data safe with automatic weekly backups, plus manual snapshots you can use to revert your server if something goes wrong.”
Read 2026-09-05 · official site
- Important Backup Package Information - IONOS Help ↗
“With a backup package, you can back up and restore your Virtual Private Server, VPS, Cloud Server, or Dedicated Server. [...] When configuring the schedule, you can specify the desired retention period and compression level for your backups.”
Read 2026-09-25 · official docs
- Redundant Daily Backups | Kamatera ↗
“Backups are kept for 14 days. A small monthly fee ensures that your servers are included in our daily backups, performed at 00:00, based on the data center location.”
Read 2026-09-25 · official site
- Neo4j Pricing ↗
“Daily backups, 7-day retention Available on Azure, AWS, and Google Cloud [...] Daily backups with 30-day retention and hourly point-in-time restore [...] Hourly backups with 60-day retention”
Read 2026-09-13 · official pricing
- Point-in-time restore — Neon Docs ↗
“Neon retains a history of changes for your branches, with defaults of 6 hours on Free plan and 1 day on paid plans. [...] You can configure it up to 7 days on Launch or 30 days on Scale plans.”
Read 2026-09-07 · official docs
- Neon plans — Neon Docs ↗
“History window 6 hours, up to 1 GB-month Up to 7 days Up to 30 days”
Read 2026-09-05 · official pricing
- Neon Read Replicas — Neon Docs ↗
“Neon read replicas are independent computes designed to perform read operations on the same data as your primary read-write compute. Neon's read replicas do not replicate or duplicate data. Instead, read requests are served from the same storage”
Read 2026-09-05 · official docs
- Nhost Pricing ↗
“10 gb database 50 gb storage 50 gb egress automated backups point in time recovery bring your own services managed grafana (metrics & alerting) email support”
Read 2026-09-14 · official pricing
- Backup and Restore ↗
“This is available for paid tiers only. We hope to make this process self-serve soon. [...] We take three backups daily to ensure your data is well-protected.”
Read 2026-09-13 · official docs
- Backup Policies | Oracle Cloud Infrastructure Documentation ↗
“The bronze policy includes monthly incremental backups, run on the first day of the month. These backups are retained for twelve months. This policy also includes an incremental backup, run yearly during the first part of January. This backup is retained for five years. [...] The gold policy includes daily incremental backups, retained for seven days, along with weekly incremental backups, run on Sunday and retained for four weeks. [...] Custom (user-defined) backup policies include configurable frequency, retention”
Read 2026-09-25 · official docs
- Back up and restore — PlanetScale Docs ↗
“All PlanetScale Postgres databases include automatic scheduled backups that run every 12 hours for production and development branches. Default backups are created automatically and don't require any setup. There are no additional charges for these backups. [...] The default, included backup schedule retains backups for 2 days. You can set a custom retention period for custom backup schedules and manual one-off backups.”
Read 2026-09-05 · official docs
- Pricing — PlanetScale ↗
“High Availability - 1 primary + 2 replicas across 3 availability zones”
Read 2026-09-14 · official pricing
- Managed WordPress Plans & Pricing — Pressable ↗
“Hourly & Daily Backups”
Read 2026-09-06 · official pricing
- Pricing — Prisma ↗
“Backups Free — Starter Daily, 7-day retention Pro Daily, 7-day retention Business Daily, 30-day retention”
Read 2026-09-06 · official pricing
- Terms of Service - RackNerd ↗
“Unless a separate backup service or written agreement is purchased or issued by RackNerd, VPS, Hybrid Server, Dedicated Server / Bare Metal Server, and Colocation services do not include managed backups by default.”
Read 2026-09-25 · official site
- rsync.net - Simple Pricing ↗
“7 days + 4 weeks snapshots”
Read 2026-09-15 · official pricing
- ScaleGrid Pricing ↗
“ScaleGrid offers up to five backups per deployment on ScaleGrid's dedicated hosting plans.”
Read 2026-09-11 · official pricing
- PostgreSQL Point In Time Recovery (PITR) — ScaleGrid Docs ↗
“by default, they are scheduled to happen every 10 minutes, and transaction logs will be retained for a duration of 7 days [...] Point In Time Recovery is supported on the following cloud providers: Azure, DigitalOcean, EC2, and OCI.”
Read 2026-09-13 · official docs
- Scale MySQL Standalone to Replica Set — ScaleGrid Docs ↗
“Easily upgrade your fully managed MySQL Database at ScaleGrid from a standalone deployment to a highly available replica set, and customize your geographic distribution in the cloud. [...] Select your number of nodes: 2 + 1 Quorum or 3.”
Read 2026-09-13 · official docs
- SimpleBackups Pricing ↗
“Flexible Retention & Schedule”
Read 2026-09-15 · official pricing
- SnapShooter Pricing ↗
“Daily, Weekly, Monthly Retention”
Read 2026-09-15 · official pricing
- 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
- Read Replicas — Supabase Docs ↗
“Read Replicas are additional databases kept in sync with your Primary database. [...] Replication is asynchronous to ensure that transactions on the Primary aren't blocked. There is a delay between an update on the Primary and the time that a Read Replica receives the change. This delay is called "replication lag." You can only read data from a Read Replica.”
Read 2026-09-05 · official docs
- 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
- Pricing — TigerData ↗
“Point-in-time-recovery to 3 days Performance Insights Basic support (9-5 ET)”
Read 2026-09-06 · official pricing
- 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
- Pricing — Turso ↗
“Point-In-Time Restore Free 1 day Developer 10 days Scaler 30 days Pro 90 days”
Read 2026-09-06 · official pricing
- 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
- Backups | UpCloud Docs ↗
“Simple Backup is charged on top of the Cloud Server's plan price, as a percentage of the plan price. [...] Each scheduled backup is kept for a set duration according to the selected retention period starting from 1 day and up to 3 years. [...] On-demand backups are never automatically deleted and will be kept until manually deleted.”
Read 2026-09-25 · official docs