Development

One client,every database

DBeaver, on a Void Linux desktop of your own.A SQL editor, the schema tree, and drivers for the engine you actually run.

DBeaver 26.2.04 cores · 8 GBOpens in a browser tab

hub://dbeaver

$ dxflow workflow create --identity dbeaver hub://dbeaver --start --link

01Pick a machinecores, memory and a rate per hour

02Create the workflowpulled from the hub, once

03Run it, then stopstopped when the work is done

The application

Connect,then read the schema

The same window for Postgres, MySQL, SQLite, Oracle and the rest.

Drivers for most engines

JDBC drivers download on first use, so a new connection is a form, not a build.

A real SQL editor

Completion from the live schema, multiple result tabs, and an explain plan.

Move data out

Export a query or a table to CSV, JSON or another connection, onto the volume.

How you run it

Every defaultis one override away

The session reads its settings from the environment, so you set them on the start line.

VNC_PASSWORDWhat the tab asks for. It ships as dxflow, and everyone reading this knows that.

PANEL and TASKBARBoth hidden, so the workspace has the whole screen. Show either one to get the desktop back.

AUDIOOff here. Turn it on and the desktop sound is streamed beside the picture.

start it your way

$ dxflow workflow start dbeaver --override env.app.VNC_PASSWORD=something-long

$ dxflow workflow start dbeaver --override env.app.TASKBAR=show --link

The session

The workspacefills the screen

Streamed to your browser, with DBeaver already maximized.

6082Browserin the tab, at /vnc.html

5901VNCin a native client

/volumeStorageyour files, kept between runs

Open it from anywhereStart with --link and the session comes back on an HTTPS address.

Set a password firstVNC_PASSWORD defaults to dxflow, and everyone can read this page.

Good to know

Drivers arrivewhen you first ask

The image carries DBeaver, not every JDBC driver in existence. It fetches the one you need.

The first connection needs network

Pick an engine and DBeaver downloads its driver. After that the driver is on the volume and the session can be closed off.

The workspace persists

Connections, saved SQL and results history live in the Eclipse workspace on /volume, so a restart does not lose them.

Credentials sit on the volume too

A saved connection keeps its password in the workspace. Treat the volume as something worth protecting.

The image

Pulled once,then it stays

DBeaver arrives as one image. This is what comes down the first time, and what the disk should have free for it.

474Mamd64compressed, the way the registry counts it

459Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/dbeaver:latestPublished from the hub, pulled on the first start and kept for the ones after it.

Either architectureamd64 and arm64 are both published, and the machine pulls the one it runs.

What it asks for

What it wants,and what it needs

The definition asks for 4 cores and 8 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.

4 cores · 8 GBAsks forwhat the definition writes down

2 cores · 4 GBRuns onthe least the image comes up on

Not neededGPUit works on the cores alone

The ask is not the floorThe definition writes down what suits the work. The image itself starts on less, which is what the second figure is.

--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

DBeaver asks for 4 cores and 8 GB. Cheapest first.

E2 Standard-4

$0.168/ hour4 cores · 16 GBStart this machine

T4g XLarge

$0.168/ hour4 cores · 16 GBStart this machine

C7g XLarge

$0.181/ hour4 cores · 8 GBStart this machine

Run DBeaver on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start DBeaver Browse workflows