CLoudBeaver ensures all users receive technical support for the duration of their paid license. Tickets for technical support can be submitted via the website.

Please be aware that technical support ends alongside the expiration of the license period. This occurs even though CLoudBeaver remains usable for users with a Perpetual license type.

CloudBeaver Enterprise is a web application that requires server deployment.

You only need a Linux, macOS, or Windows machine with Docker.

• Install Docker 20.10 or higher

• amd64 or arm64 system.

To install the latest version of CloudBeaver, use the following script:

docker pull dbeaver/cloudbeaver-ee:latest

To run CloudBeaver Enterprise in the terminal:

docker run --name cloudbeaver-ee --rm -ti -p 8080:8978 -v /var/cloudbeaver/workspace:/opt/cloudbeaver/workspace dbeaver/cloudbeaver-ee:latest

Then switch to the browser and open http://localhost:8080/

Add the following parameters:

-d --restart unless-stopped

Instructions on how to deploy via Docker-compose with configuration examples can be found here: https://github.com/dbeaver/cloudbeaver-deploy

This guide covers how to deploy CloudBeaver Community Edition on Google Cloud Platform (GCP) using both the Google Cloud Console and the Google Cloud CLI.

Before you begin, make sure you have:

• A Google Cloud account for accessing GCP services.
• Compute Engine set up in your project.

If you don’t have a GCP account, sign up on the Google Cloud signup page.

To deploy CloudBeaver Community Edition in Google Cloud, you need certain permissions to create and manage resources like virtual machines, disks, and networks. Ensure you have the necessary permissions for your project.

Tip: For a full list of permissions and more information on how to manage them, see the official Google Cloud Permissions documentation.If you don’t have the required permissions, contact your system administrator.

1. Log in to the Google Cloud Console, then go to Compute Engine -> Images. Click [+] Create image.

2. Complete the Create an image form:

   • Enter the image name in the format
     cloudbeaver-ce-server-ubuntu-%version%
     or
     cloudbeaver-ce-server-rhel-%version%
     , depending on the operating system.
   • Select Virtual disk (VMDK, VHD) as the source and enter the following URI:
     cloudbeaver-ce-server/
     in the Virtual disk file field. Click BROWSE to select your version.

Tip: Replace

%version%

with the desired version number, such as

24-2-0

.

3. Click Create. The image import process can take up to 15 minutes.

1. After the image is imported, navigate to the Images tab, find your imported image, and click [+] Create instance.

2. Name your instance and set up the following:

   • Under Machine configuration, choose a machine type with at least 1 CPU and 4GB RAM for optimal CloudBeaver performance.
   • Click Change, select your custom image, and set the disk size to at least 100GB.

3. In the Firewall section, check Allow HTTP traffic and Allow HTTPS traffic to make the instance accessible online.

4. Click Create. Your instance will be ready in a few minutes. Verify by pasting its External IP into your browser.

5. Begin the initial configuration of the CloudBeaver server in your browser.

Tip: For more detailed steps on configuring and managing the server, see the Managing cloud deployed services guide.

1. In the Google Cloud Console, go to Compute Engine and click Activate Cloud Shell to launch the CLI within GCP.

2. Authorize any prompts if needed.

Run this

gcloud beta compute instances create cloudbeaver-ce-server \

--zone=us-central1-a \

--machine-type=e2-medium \

--tags=http-server,https-server \

--image=https://www.googleapis.com/compute/v1/projects/dbeaver-public/global/images/cloudbeaver-ce-ubuntu-24-2-0 \

--create-disk=auto-delete=yes \

--boot-disk-size=100GB --boot-disk-device-name=cloudbeaver-ce-server

You can customize the command as needed. For more details on using the Google Cloud CLI, see the official documentation.

Tip: Replace the

--image

URL with a different version if needed.

1. After the instance is created, retrieve its external IP (needed for accessing the CloudBeaver server):

gcloud compute instances list --filter="name:cloudbeaver-ce-server" --format="get(networkInterfaces[0].accessConfigs[0].natIP)"

This command will return the

2. Use the

   external-ip
   to start configuring and accessing the CloudBeaver interface.

3. In your browser, go to

   http://<external-ip>/
   , where
   <external-ip>
   is the public IP address of your GCP instance.

4. You’ll be redirected to CloudBeaver’s initial configuration wizard to complete the setup.

Tip: For guidance on locating your instance’s public IP address, see GCP: Viewing IP Addresses.

• https://www.googleapis.com/compute/v1/projects/dbeaver-public/global/images/cloudbeaver-ce-ubuntu-%version%
• https://www.googleapis.com/compute/v1/projects/dbeaver-public/global/images/cloudbeaver-ce-rhel-%version%

Tip: Replace

%version%

with the desired version number, such as

24-2-0

. For more information on tags, see CloudBeaver release cycles.

This guide explains how to deploy CloudBeaver Community on Microsoft Azure using the Azure Portal.

Before you begin, ensure you have a Microsoft Azure account for accessing Azure services.

Tip: If you don’t have an Azure account, sign up on the Azure signup page.

1. Log in to the Azure Portal and search for Community images in the search bar.
2. In the search bar on the left side under Community images, enter
   cloudbeaver-ce
   . Select the image for your region from the list and click Create VM.

1. Project details:

   • Subscription: Choose your Azure subscription.
   • Resource group: Create a new group or select an existing one.

2. Instance details:

   • Virtual machine name: Set a unique name for the VM.
   • Size: Choose a VM with at least 2 vCPUs and 4 GiB RAM.

3. Administrator account:

   • Username: Set to
     ubuntu
     .
   • SSH public key source: Generate a new key pair or use an existing one.

4. Inbound port rules:

   • Select inbound ports: Enable ports SSH (22), HTTP (80), and HTTPS (443).

5. Double-check your configuration and click Review + Create to finalize.

1. After the virtual machine is created, retrieve its public IP address:
   • In the Azure Portal, go to Virtual Machines.
   • Select your virtual machine.
   • In the Overview section, find the Public IP address.

2. Use this public IP address to start configuring and accessing the CloudBeaver interface.

3. In your browser, go to

   http://public-ip/
   , where
   <public-ip>
   is the public IP address of your Azure instance.

4. You’ll be redirected to CloudBeaver’s initial configuration wizard to complete the setup.

Tip: For guidance on locating your instance’s public IP address, see Azure: Find IP Address of a VM.

To use this method, you need an account on Amazon Marketplace with the following permissions:

• FAWSMarketplaceRead-only

• aws-marketplace:Subscribe on resource

1. Log in to Amazon Marketplace, find CloudBeaver AWS, and press Continue to Subscribe button.

2. Accept DBeaver Corporation offer by pressing Accept Terms and wait for request processing.

Then press Continue to Configuration.

3. Select CloudBeaver version you need in Software version field, select region, and press Continue to Launch.

4. Select the desired configuration:
   • In the EC2 Instance Type select t2.medium or more.
   • In Security group settings, press Create New Based On Seller Settings. Then press Launch.

5. Great! CloudBeaver instance is successfully deployed on EC2.

6. Click EC2 Console link, and you will see the list of your instances. The new instance will be the last one, and without a name.
   • Click on the empty field to give the instance a name.
   • Click on the Instance ID, and you will see the Instance summary.

7. Click on the open address link in the Public IPv4 DNS section.

7. The page in your default web browser will be opened. You need to agree to use the self-signed certificate and change it later. How to change certificate

That’s all done! CloudBeaver Community instance is ready to use. On the first page, you will see the server configuration wizard.

Tip: For detailed steps on the initial setup and server management, see the Managing cloud deployed services guide.

See Running from Docker

CloudBeaver EE is an advanced version of the CloudBeaver product. It includes many features of the CloudBeaver Community version, plus numerous enterprise-focused features.

Tip: For a practical demonstration of CloudBeaver’s capabilities, please refer to our demo server. For more information, see Demo Server.

• Relational databases
  • Apache Calcite
  • Apache Drill
  • Apache Ignite
  • Apache Phoenix
  • SQL Server
  • Sybase, SAP ASE
  • DB2
  • Snowflake
  • Databricks
  • Vertica
  • Netezza
  • Hive
  • Google Bigquery
  • Intersystems Cache
  • Clickhouse
  • CockroachDB
  • Dremio
  • DuckDB
  • EnterpriseDB
  • Informix
  • MaxDB
  • Neo4j
  • Oceanbase
  • Opensearch (Elasticsearch)
  • SAP HANA
  • Teradata
  • Timescale
  • Trino
  • Yellowbrick
  • Yugabyte
• NoSQL databases
  • MongoDB
  • Cassandra
  • InfluxDB
  • Couchbase
  • CouchDB
  • Redis
• AWS databases
  • RDS/Aurora
  • Athena
  • Redshift
  • DynamoDB
  • DocumentDB
  • Keyspaces
  • Timestream

To upgrade the server, you need to pull a new image from Docker Hub and restart the server.

Before upgrading, ensure you have a backup. In some cases, you won’t be able to downgrade if something goes wrong.

docker pull dbeaver/cloudbeaver-ee:${version.number}

docker restart ${containerId}

By default, the CloudBeaver EE container has the name

To upgrade to the latest version, use

CloudBeaver is a web server which provides a rich web interface.
It consists of two parts:

• Server back-end. It is written in Java and reuses “platform” libraries of DBeaver.
• Front-end part. It is written in TypeScript and JavaScript.

This build process is relatively complicated (and also consists of two parts).

Tip: For a practical demonstration of CloudBeaver Enterprise Edition’s capabilities, please refer to our demo server. For more information, see Demo Server.

• Java 17
• Apache Maven (3.9.0+)
• Node.js (20.x)
• Yarn (1.22.x)
• NPM + Lerna

Important: CloudBeaver includes OpenJDK, which is an open-source version of Java. This means you do not need to purchase a separate Java license to use CloudBeaver.

Add Node.js (version 20.x) and Yarn 1.22.x version repo:

  curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -

  echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list

  curl -sL https://deb.nodesource.com/setup_18.x | sudo -E bash -

Install packages:

sudo apt update

sudo apt install openjdk-17-jdk

sudo apt install maven

sudo apt install yarn

sudo apt install nodejs

sudo apt install npm

• Download and install AdoptOpenJDK
• Download and extract Maven.
• Add path to Maven bin folder in system PATH
• Download and install Node.js. NPM comes along with Node.js, NPX/Lerna will be installed in the build script.

• Download and install Yarn 1.22.x

git clone https://github.com/dbeaver/cloudbeaver.git

cd cloudbeaver/deploy

./build.sh

The final artifacts can be found in

cd cloudbeaver

./run-server.sh

By default, the server listens to port

Note: you must be in the server root directory to run it.
If you need to run it from some other directory, then you can set the environment variable