One DBeaver, configured once, opened by twelve

Every new analyst repeats the same afternoon: install DBeaver, hunt down the JDBC driver, request read-only credentials, paste them into a config file that now lives on a laptop forever.

Do it once instead. One container runs DBeaver with every connection profile set up: read-only credentials, the right drivers, the saved queries. The team gets the display URL, locked behind the container's proxy permissions. Anyone who opens it is sitting at the configured tool, querying within a minute of joining.

The credentials never leave the server. When someone leaves the team, you revoke their access to the URL; there's no laptop to wipe, no config file to chase.