CloudBeaver CE for railway.app

Template Header

Deploy CloudBeaver CE on Railway with one click.

Deploy and Host CloudBeaver CE on Railway

CloudBeaver CE is the open-source, web-based SQL client from the DBeaver team. This template packages the official dbeaver/cloudbeaver Docker image so you can deploy a fully working instance on Railway in a single click, without installing a desktop database client or managing a server yourself.

About Hosting CloudBeaver CE

CloudBeaver CE runs entirely in the browser: connect to PostgreSQL, MySQL, SQLite, MongoDB, and many other databases through one shared web UI. Hosting it on Railway means Railway builds the Docker image, terminates TLS on a public domain, and keeps the container restarted and healthy — you only manage the data sources you connect to.

Why Deploy CloudBeaver CE on Railway

Zero infrastructure management — no VM or Docker host to patch or size
Instant HTTPS — Railway issues a public domain with TLS out of the box
Persistent storage — a Railway volume keeps connections, users, and settings across redeploys
Automatic rebuilds — Renovate keeps the pinned upstream image current, Railway redeploys on push
Team access — invite teammates to the same Railway project instead of sharing local installs

Common Use Cases

Giving a team shared, browser-based access to shift/prod databases without VPN-only desktop tools
A lightweight admin UI for a database already running on Railway (Postgres, MySQL, MongoDB, …)
Ad-hoc SQL exploration and reporting during development or debugging
Onboarding new engineers with one shared login instead of installing a desktop SQL client each

Dependencies for CloudBeaver CE

The official dbeaver/cloudbeaver Docker image (pinned tag, see Dockerfile)
A Railway volume mounted at /opt/cloudbeaver/workspace for persistent configuration and data
Network access to whichever databases you connect to from within CloudBeaver

✨ Features

Web-based UI for browsing, querying, and managing SQL/NoSQL databases
Supports PostgreSQL, MySQL, SQLite, MongoDB, and many other drivers
Multi-user access with role-based permissions

🚀 Quick Start

Click "Deploy on Railway"
Set the environment variables listed below
Attach a volume at /opt/cloudbeaver/workspace before sending production traffic
Wait for the build and open the generated URL

⚙️ Configuration

Environment variables

# This template needs no required variables.

Set real credentials as Railway variables, never in a file inside this repository.

Optional

PORT: HTTP port CloudBeaver CE binds to (default: 8978). Railway sets this for you; leave it alone unless you also change the domain's target port.

💾 Persistence

railway.toml declares requiredMountPath = "/opt/cloudbeaver/workspace". Attach a Railway volume to that path before production traffic, otherwise all data is lost on every redeploy.

🐳 Local Development

git clone https://github.com/vergissberlin/railwayapp-cloudbeaver-ce.git
cd railwayapp-cloudbeaver-ce
cp .env.example .env
docker compose up -d

Then open http://localhost:8978.

🪲 Bug Reporting

Found a bug? Create an issue or open a pull request with a fix.

🤝 Contributing

See CONTRIBUTING.md.

📝 License

MIT — see LICENSE.

🔒 Security

All credentials are supplied as environment variables, never committed
Railway terminates TLS for the generated domain
Renovate keeps the pinned upstream image up to date

Railway runtime defaults

railway.toml ships these defaults:

Healthcheck path: /
Restart policy: ON_FAILURE with up to 10 retries
Dockerfile-based build

The image entrypoint (railway-entrypoint.sh) maps $PORT to CLOUDBEAVER_WEB_SERVER_PORT and then delegates to the upstream entrypoint, so the upstream initialisation still runs. Overriding the start command in Railway skips both steps.