Migrating production infrastructure? Get up to ₹10,000 in migration credits. Apply now
voroaDocs
Voroa Postgres

Upgrade a database that runs on its own server

Move a database that runs on its own server to a bigger plan: what you pay, how long it is down, how storage grows, and why a plan cannot be made smaller.

What this covers

When you create a PostgreSQL, MySQL or Key Value database and choose a region and provider on the create page, that database runs on a server of its own, sized exactly to the plan you picked. This page explains how to move it to a bigger plan, and what happens while it moves.

The five steps of a database plan upgrade: pay the difference, backup, server restarts on the bigger plan, storage grows, running on the new plan

How to upgrade

  1. Open the database and go to Settings.
  2. In the Size section, select Upgrade.
  3. Pick a bigger plan. Only plans that are bigger than the current one, of the same kind, are listed.
  4. Check the payment summary and pay.

The upgrade starts on its own as soon as the payment is confirmed. The setup log shows each step while it runs.

What you pay

You pay the difference between the old plan and the new one for the days left in the current billing period, with GST, on one invoice. From the next period the new plan’s price applies. If the upgrade cannot be completed before the server changes size, your database stays on its previous plan and a support ticket is opened for the refund automatically. You do not need to do anything.

How long the database is unavailable

The server restarts with the new plan. Your database is unavailable for about 3 minutes. Before the restart, Voroa uses a backup of this database from the last hour, or takes a new one first; if a new backup does not finish, nothing is changed. Connections drop during the restart, so applications should reconnect, as they would after any database restart.

Storage

Storage grows to fit the bigger plan’s disk. You cannot buy storage separately for this kind of database: pick a bigger plan instead.

Why a plan cannot be made smaller

A server’s disk can grow but never shrink, so a plan can be upgraded but not downgraded. To use a smaller plan, create a new database on that plan and move your data to it.

What is not available yet

  • Changing the region of an existing database.

Before you upgrade

  • Pick a quiet time. The database is unavailable for about 3 minutes while the server restarts.
  • Make sure your app reconnects. Most database drivers and connection pools do this on their own; check yours handles a dropped connection without crashing.
  • Only need more disk? On this kind of database a bigger plan is the way, since storage cannot be bought on its own.

Frequently asked questions

Do I lose data when I upgrade?

No. Your data stays on the same disk, which grows to the bigger plan’s size. A backup from the last hour is also in place before anything changes.

What if the upgrade fails?

Your database stays on its previous plan and a support ticket opens for the refund automatically.

Can I move to a different region at the same time?

Not today. The region stays the same on an upgrade.

Last updated November 12, 2026