Managed Databases, Simplified

Standard and High Memory plan Managed Databases for MySQL and PostgreSQL are available with 1 to 3 database nodes.

Managed Databases can be deployed with storage ranging from 10 GB up to 7 TiB for MySQL and 15 TiB for PostgreSQL plans.

Regular 15-day PITR automated backups are included on Standard and High Memory plans with Extended 31-day backup retention available as an option.

Managed Databases utilise the databases’s native streaming replication features to replicate the data to the hot standby nodes in real time. In normal operation, DNS entries will point to a primary node and one of the replicas in will be automatically promoted in case of a primary failure. Using plans with at least two nodes is highly recommended.

Yes indeed, the replica nodes offer a perfect use case for load balancing the Managed Database cluster by splitting read and write operations between multiple nodes.

Of course, you are able to create and manage users and their permissions directly through the database engine’s own interface by using the primary user for management.

Yes, at-rest data encryption covers both active service instances as well as service backups stored in cloud Object Storage. Service instances and the underlying Cloud Servers use full volume encryption with a randomly generated ephemeral key per each instance and each volume.

Restores are always done to a new instance, never on top of an existing one. Restoring a backup to a temporary instance allows you to view the data without interruption to your database services.

No. Unlike rigid legacy plans that bundle resources, our architecture completely decouples compute from storage. You can scale your disk capacity dynamically without being forced to pay for unnecessary vCPU or RAM upgrades. Storage is priced symmetrically across all production tiers.

Neither. Hyperscalers frequently cap your storage bandwidth based on your compute tier, forcing vCPU upgrades just to unlock more I/O. We run on our proprietary MaxIOPS™ storage, delivering completely raw, unthrottled performance directly out of the box. There are no variable IOPS provisioning surcharges.

No. We do not believe production resilience should scale linearly into a financial penalty. We engineer automatic, compounding discounts directly into our node topologies. In a 2-node HA setup, your standby replica automatically receives a 10% discount on compute and storage. In a 3-node HA+ setup, your second node receives a 10% discount, and your third read replica receives a 30% discount.

No. High-write applications on hyperscalers often trigger massive, unforeseen billing overages as write-ahead logs (WAL) quickly exceed “free” backup ceilings. We completely eliminated this variable pricing. All Standard and Memory-Optimized plans include a 15-day Point-in-Time Recovery (PITR) at no extra cost and extended 31-day PITR for a flat fee.

Instead of unpredictable usage-based pricing, our Extended Backup Tier (31 Days PITR) is a simple, predictable flat fee tied strictly to your storage tier. For example, any database utilizing between 80 GiB and 400 GiB of storage pays a flat rate of €29 (or $34) per month for 31-day PITR, regardless of transaction volume.

Yes. Provided that you’re running a 2x or 3x cluster, you can scale the resources in a Managed Database up or down in a few clicks from the control panel, and the process runs without taking your database offline. 

Managed Databases are available across UpCloud’s global data centre network, so you can place your database close to your application and your users. Check the Data Centers page for the full list of our locations.

Yes, Managed Databases can connect to your cloud servers over UpCloud’s private utility network or private SDN, keeping traffic off the public internet. There’s a step-by-step guide in How to connect Managed Databases to SDN Private Networks.

Valkey is compatible with Redis OSS 7.2.4, so most applications built for Redis will work with little to no change. It’s licensed under BSD-3 and maintained under the Linux Foundation, which gives you an open source path forward without vendor lock-in.

There are guides for the most common paths, including migrating a MySQL database to UpCloud and How to migrate PostgreSQL database to UpCloud . If your setup is more involved, UpCloud’s support team can help plan the migration.

Yes. Managed Databases can be provisioned and configured through the UpCloud API or using your choice of OpenTofu,  Terraform, or Pulumi, so they fit straight into an existing infrastructure-as-code workflow. See How to configure Managed Databases using Terraform or How to get started with Pulumi.

You can move up to a larger plan at any time as your data grows, right up to the top tier for your chosen engine. There’s no need to plan for peak capacity up front.

Yes, all new signups are able to enter a trial before becoming a full UpCloud Customer. For the latest offers and deals check out our homepage.