Managed Database Overview

Plans and Pricing

There are two kinds of database cluster plans you can choose from: single node clusters and high availability clusters.

  • Single node clusters begin at $15/month for a single node cluster with 1GB of RAM. Single node clusters are not highly available, but they feature automatic failover. These clusters are a good fit for preliminary development and testing.

  • High availability clusters begin at $50/month ($0.074/hour) for the 2GB RAM/2 vCPU plan when you add at least one matching standby node for automatic failover. Get more detail about high availability configurations.

All plans include automatic backups with a one week retention policy and point-in-time restoration. You can scale node sizes, add standby nodes for automatic failover, and add read-only nodes at any time.

Inbound data transfer is included in the price of the cluster. Outbound data transfer billing is waived until January 1, 2020, at which time it will be billed at $0.01/GB.

Regional Availability

At least one datacenter in every region supports managed databases. Our regional availability matrix has more detail about our datacenter regions and product availability. Managed databases will not be offered in NYC2, AMS2, or SFO1.

Features

  • Read-only nodes. You can add read-only nodes in geographically disparate data centers.

  • Automatic updates. You can select a date and time during which weekly automatic updates for the database engine and operating system will occur to keep the service stable and secure.

  • Daily point-in-time backups. Databases are automatically backed up every day, which lets you restore data to any point within the previous seven days.

  • High availability with automated failover. In the event of a failure, managed databases with a standby node will automatically switch data handling to the standby node to prevent unplanned downtime.

  • End-to-end security. Data is encrypted at rest with LUKS and in transit with SSL.

  • Database engines. DigitalOcean Managed Databases currently support PostgreSQL. We are actively working on additional engines.

  • Metrics, logs, and query insights. Monitoring data is included in the control panel, both for the servers running the cluster and for the databases themselves. Learn more about cluster monitoring and database monitoring.

Limits

  • By default, you are limited to 3 clusters per account or team.

  • Each cluster is limited to 5 read-only nodes.

  • You cannot delete the default database and user.

  • When you restore from a backup, you must restore to a new node and re-add any read-only or standby nodes. See How to Restore from Backups for details.

  • Point-in-time-recovery (PITR) is limited to the last 7 days.

PostgreSQL Limits

  • Support for PostgreSQL v10 and v11 only.

  • We support selected extensions. See Supported PostgreSQL Extensions for a comprehensive list.

  • Each cluster allows 25 backend connections per 1 GB of RAM minus 3 connections per node that are reserved for maintenance. If you have a high number of concurrent connections, we recommend looking into connection pooling.

    Plan Size Available Backend Connections
    1 GB RAM 22
    4 GB RAM 97
    8 GB RAM 197
    16 GB RAM 397
    32 GB RAM 797
    64 GB RAM 1,597
  • Connection pooling with PgBouncer is supported to increase the number of available concurrent client connections.

  • Alerting on PostgreSQL metrics is not yet available.

Known Issues

  • You must use a third-party client to manage access control lists (ACLs). You can add users and databases from the DigitalOcean Control Panel.

  • You can’t use DigitalOcean’s Cloud Firewalls with managed databases. Until support is available, you can restrict access to nodes by their incoming IPv4 addresses.

  • Databases do not currently integrate with private networking. This means that data between your databases and Droplets must travel over the public network. However, clusters are encrypted at rest with LUKS (Linux Unified Key Setup) and in transit with SSL.

  • Point-in-time-recovery (PITR) operations are limited to the last 7 days. The date picker doesn’t restrict you from choosing an earlier date, and you will receive an error if you try to recover from a date outside of the 7-day window.