Databases
View and manage databases in Servoy Cloud — download backups, request remote access, and restore databases across environments.
What you can do here
The Databases Overview is not supported for Satellite environments
The database dashboard in the Servoy Cloud Control Center displays all available databases along with key information for each one.
Database details
Each clickable card on the dashboard provides essential information to easily identify the database, including:
Database name
Database icon: representing the type of database (e.g., PostgreSQL, MSSQL, MySQL)
Database version
SQL version
Database status
Download Backup file
To download the backup file of a database from the Cloud Control Center, follow these steps:
Navigate to the Database dashboard from Application > Environments > Environment Details > Database
Find the context menu on the database for which you want to download the backup file.
Click “Download backup file”
Check your email for the Servoy Cloud GPG decryption passphrase.
Refer to our documentation on how to use the passphrase and decrypt the backup file.
Remote Database Access
Request Remote Access
Requires Manage Account permission.
Users can request remote database access via the Database Overview screen. This allows you to perform troubleshooting, data analysis, or other actions requiring direct database access.
To initiate a request, navigate to: Environment Details → Database View → Actions Button → Request Remote Access.
A dialog will appear, allowing you to specify the required access type (readonly, readwrite), provide a whitelisted IP address, and include any relevant notes. Once submitted, a support ticket is created automatically and access will be granted based on the provided details.


Remote access is available for both production and non-production databases (development, staging). Previously this was limited to production only.
View and Manage Remote Access
You can view which IP addresses currently have remote access to a database, and request removal of specific IPs directly from the Control Center.
To access this view:
Go to Database Overview > Environments > Databases
Select your database
Click Actions (top right)
Select View Remote Access
The dialog shows each whitelisted IP with its description and date added. To remove an IP, click Request Removal, provide a reason, and a support ticket is created automatically.

Restore a Database from Another Environment
Why restore a database?
The Cloud Control Center allows you to restore a database from a different environment within the same application. This is useful for syncing lower environments (such as DEV or UAT) with data from higher ones (such as PREPROD or PROD). This operation is restricted to ensure it is performed only when appropriate and by authorized users.
How to Access the Restore Option
To download the backup file of a database and initiate a restore:
Navigate to Application > Environments > Environment Details > Database.
Locate the database you want to restore.
Open the context menu (⋮) on the target database row.
Click “Restore database from environment.”
Note: This menu item will be disabled if the following restrictions apply.
Restrictions
Production databases cannot be restored.
Only PostgreSQL databases are supported.
Restore is limited to environments within the same application.
You can only restore from higher to lower environments.
You must have production-level permissions
Valid restore paths:
DEV can restore from UAT, PREPROD, or PROD.
UAT can restore from PREPROD or PROD.
PREPROD can restore from PROD.
Restore Process
You will be presented with a wizard to begin the restore
Step 1: Select Source
Select the source environment and database you want to restore from.
Step 2: Confirm and Run
The wizard will show a summary of your choices, including:
Source environment and database
Destination environment and database (your current environment)
Click Confirm & Run to execute the restore.
Duration
The restore process typically takes between 5 and 10 minutes, depending on the size of the database.
Important Notes
The restore process completely overwrites the destination database.
Always review your selections carefully before confirming.
This action can only be performed by users with production-level permissions.
Last updated
Was this helpful?