CloudBeaver

Web-based database management for teams, self-hosted on your own server. What you actually get — and what stays locked behind the enterprise tier.

TL;DR

• What it is: Apache 2.0-licensed web database client — the browser-based sibling of the popular DBeaver desktop tool. Your team logs into a shared SQL interface instead of each person installing local software [1][README].
• Who it’s for: Small teams who need a shared, browser-accessible SQL client — analysts, developers, and non-technical operators who query data but don’t need heavyweight change-management workflows [1].
• Cost savings: Commercial CloudBeaver runs $200/user/year. Self-hosted Community Edition is free, though it covers only ~20 databases versus 80+ in the paid build [1][website].
• Key strength: DBeaver’s mature query engine and data editor, now accessible in a browser without per-machine installation. The desktop app has 10 million users — CloudBeaver inherits that SQL editing muscle [README][website].
• Key weakness: The Community Edition is deliberately capped. Audit logs (called “Query Manager”) are paid. Data masking, schema compare, and most NoSQL/cloud warehouse support are enterprise-only. If you need governance features, you’re paying or switching tools [1].

---

What is CloudBeaver

CloudBeaver is DBeaver’s web version. Where DBeaver is a desktop application you install per machine, CloudBeaver runs as a Java server and serves a React/TypeScript frontend in the browser. You deploy one instance; your whole team connects through their browsers without installing anything locally [README].

The GitHub repository describes it plainly as “Cloud Database Manager” with an Apache 2.0 license. That’s the important part for anyone comparing open-source options — Apache 2.0 is permissive with no commercial use restrictions, which puts it ahead of tools using the “Fair-code” or BSL licenses that limit self-hosted commercial use [README].

The project sits at 4,740 GitHub stars — modest for a database tool category where alternatives like Metabase (40K+ stars) and Adminer are well-established, but the star count undersells it because CloudBeaver’s parent brand (DBeaver) is the actual draw. The desktop DBeaver is used by an estimated 10 million people [website]. CloudBeaver is essentially that tool’s server mode.

As of the 26.0.0 release in early 2026, notable additions include LDAP group membership mapping, parameters and variables in the SQL editor, and a batch of security vulnerability patches across several libraries [README]. The development pace is active — releases ship roughly monthly.

---

Why people choose it over alternatives

The Bytebase comparison article [1] — the most thorough third-party analysis available — frames CloudBeaver’s position clearly: it’s a shared SQL client, not a database governance platform.

The case for CloudBeaver over individual desktop tools is straightforward: instead of every analyst on your team installing DBeaver locally, maintaining their own connection configs, and storing credentials on their laptops, you run one CloudBeaver instance. Everyone connects through the browser. Connection strings live in one place. Access is managed centrally. A new hire gets a browser link, not a setup guide [1].

Versus Bytebase. Bytebase targets teams that need review workflows, approval chains, data masking, and audit trails around database changes. CloudBeaver targets teams that need query access without that overhead. The Bytebase article puts it bluntly: “If you want a shared web GUI for everyday querying and editing, CloudBeaver fits. If you need review workflows, granular permissions, masking, and audit trails, that’s Bytebase” [1]. Neither is wrong — they solve different problems. A startup where three developers all have production read access needs CloudBeaver. A fintech with compliance requirements needs Bytebase.

Versus Adminer / phpMyAdmin. These are single-file PHP database tools. They’re lighter and simpler, but they’re closer to emergency-repair utilities than daily-driver SQL clients. CloudBeaver inherits DBeaver’s full data editor — cell-level editing, filtering, sorting, multiple views, GIS data support, data transfer between databases. That’s a serious functional gap versus Adminer [README].

Versus TablePlus. TablePlus is a polished native desktop GUI that costs $59/license one-time (with an optional subscription for updates). It’s excellent for individual developers. It doesn’t have a self-hosted server mode — your team can’t share a TablePlus instance. CloudBeaver is the play when you need a centralized, team-accessible tool rather than per-developer licenses.

The DBeaver brand connection is a double-edged sword. It means the query engine is genuinely mature and the SQL editor is capable — fuzzy autocomplete, variable support, multi-statement execution, and data profiling are all there [README]. But it also means the product’s primary business is commercial DBeaver licenses, and CloudBeaver CE exists partly as a funnel to those paid products [website].

---

Features

Based on the README and release notes:

SQL Editor:

• Parameters and variables in queries, reusable across executions [README]
• Fuzzy search in autocomplete — finds tables even with typos [README]
• SQL preview for bound parameters [README]
• Tab and Enter keys both trigger autocomplete [README]
• Multi-statement scripts with variable support [README]

Data Editor:

• Find and Replace with regex, case-matching, and whole-word options [README]
• Bulk operations on multiple selected rows (add, duplicate, delete, set NULL) [README]
• Column drag-and-drop for reordering [README]
• Large object (LOB) data viewing [README]
• Cell-level editing, custom filters, sorting [README]

Database support (Community Edition):

• ~20 databases: MySQL, PostgreSQL, Oracle, SQLite, SQL Server, MariaDB, and similar common engines [1]
• ClickHouse support included (driver updated to 0.9.7 in 26.0.1) [README]
• Enterprise tier adds 80+ engines: MongoDB, Cassandra, Redis, Redshift, BigQuery, Snowflake, and others [1]

Team and access management:

• LDAP integration with memberOf group mapping (added in 26.0.0) [README]
• Basic team/user groups with per-connection access restrictions [1]
• Session management and inactive user listing in admin panel [README]
• Query Manager (audit log) — paid feature [1]

Deployment:

• Docker image available on Docker Hub [README]
• Java-based server with React/TypeScript frontend [README]
• Live demo at demo.cloudbeaver.io [README]

What’s missing in Community Edition:

• Data masking: not available in any tier (Bytebase has this, CloudBeaver does not) [1]
• SQL review rules: not present — no automated query linting [1]
• Schema comparison: not supported [1]
• GraphQL API: available in CloudBeaver, though described as less mature than alternatives [1]
• Audit log (Query Manager): paid [1]
• Most NoSQL and cloud warehouse connectors: enterprise only [1]

---

Pricing: SaaS vs self-hosted math

CloudBeaver commercial (their managed/licensed product):

• Listed at $200/user/year on the DBeaver website [website]
• Marketed toward financial analysis, data analysis, sales and marketing teams [website]

DBeaver product family for context:

• Enterprise Edition: $250/user/year (full-featured desktop toolkit for DBAs and developers) [website]
• Team Edition: $80–800/user/year (role-based collaboration across teams) [website]

Self-hosted Community Edition:

• Software: $0 (Apache 2.0) [README]
• Server to run it: $5–15/month on any VPS (Hetzner, Contabo, DigitalOcean)
• Java requires more RAM than a Go-based tool — budget at least 2GB RAM for the JVM, preferably 4GB for a team [README]

Concrete math for a 5-person team:

At $200/user/year, five team members on commercial CloudBeaver costs $1,000/year. Self-hosted CE on a $10/month Hetzner VPS costs $120/year — with the caveat that you’re limited to ~20 databases and lose enterprise features like the Query Manager and advanced user governance [1].

If your team primarily queries PostgreSQL, MySQL, and SQLite — the CE database list covers you fine. If you’re accessing Snowflake, BigQuery, or MongoDB as primary data sources, you either pay for the enterprise license or choose a different tool. That’s a hard limit, not a workaround [1].

No usage-based pricing. Unlike Zapier-style tools that charge per operation, CloudBeaver is per-user-per-year or free. That’s sane pricing for a database client.

---

Deployment reality check

CloudBeaver is Java-based, which means the JVM is a real operational consideration — not a dealbreaker, but different from the Go-binary or Node single-container tools that self-hosters are used to [1].

What you need:

• A Linux VPS with 2–4GB RAM minimum (Java heap requires it)
• Docker (the recommended deployment path) [README]
• A domain and reverse proxy (Nginx or Caddy) for HTTPS
• Basic familiarity with Docker Compose

What can go sideways:

First, the database coverage gap is the most common surprise. You deploy CE, get it working, then discover that your MongoDB instance or Redshift cluster requires the Enterprise license. Check the supported database list before deploying if your stack goes beyond the standard RDBMS set [1].

Second, the JVM adds memory pressure. A fresh CloudBeaver instance idles higher than a lightweight Go or Node tool. On a $5/month VPS with 1GB RAM shared with other services, it will struggle. Budget appropriately.

Third, the Community Edition’s access control is “basic team/user groups and per-connection restrictions” [1] — functional for small teams with trusted members, not sufficient for scenarios where you need column-level permissions, data masking, or detailed audit trails. The Bytebase article is direct: CloudBeaver’s governance story is lightweight by design [1].

Realistic setup time for a technical user: 30–60 minutes using the Docker image. The demo server at demo.cloudbeaver.io lets you evaluate before committing.

---

Pros and cons

Pros

• Apache 2.0 license. No commercial use restrictions. Fork it, embed it, deploy it for clients — no legal review needed [README].
• DBeaver’s query engine in a browser. If your team already uses DBeaver desktop, CloudBeaver is the same mature SQL editing experience without per-machine installs [README][website].
• Active development. Monthly releases, recent security patches across multiple CVEs, new SQL editor features — this isn’t abandonware [README].
• LDAP group mapping (added 26.0.0) — enterprise teams can sync CloudBeaver access from existing directory groups without manual user management [README].
• Docker deployment is straightforward. The official image is maintained and documented [README].
• Free tier is genuinely useful for teams querying common databases (PostgreSQL, MySQL, Oracle, SQL Server) without needing governance features [1].
• GIS data support, data transfer between databases — capabilities that consumer-tier database clients don’t have [README].

Cons

• Community Edition covers only ~20 databases. MongoDB, Redis, Snowflake, BigQuery — all enterprise-tier only. For a startup using a modern data stack, this is a real limitation [1].
• Audit logging is paid. The Query Manager (query history / audit log) is not in the free tier [1]. For any team with compliance needs, this matters immediately.
• No data masking in any tier. Bytebase has column-level dynamic masking. CloudBeaver has nothing equivalent — if you need to let analysts see data without exposing PII, CloudBeaver isn’t the tool [1].
• No SQL review rules. No automated checks before a destructive query runs. Your team can drop a table and there’s nothing in CloudBeaver to slow them down [1].
• Java-based — heavier than alternatives. More RAM, longer startup, JVM tuning if you’re resource-constrained [1][README].
• Modest star count (4,740) relative to category. Less community-sourced documentation, fewer third-party tutorials than more established self-hosted database tools.
• The “open source” framing is accurate but the business model is commercial upscell. The website’s primary call-to-action is DBeaver PRO; CloudBeaver CE is part of that funnel [website].

---

Who should use this / who shouldn’t

Use CloudBeaver if:

• Your team regularly queries PostgreSQL, MySQL, or other common SQL databases and you want a shared browser-based client instead of per-developer desktop installs.
• You’re already in the DBeaver ecosystem — developers use DBeaver desktop, and you want a web-accessible version for analysts and ops staff.
• You need a zero-licensing-cost query tool for internal use with basic user access controls.
• LDAP/directory-based user management matters to you (added in 26.0.0).
• You’re comfortable managing a Java application via Docker.

Skip it (pick Bytebase) if:

• You need change review workflows, approval chains, or rollback support for database migrations.
• Data masking is a compliance requirement.
• You need a detailed audit trail of who queried what and when (in CE — Query Manager is paid in CloudBeaver).
• You want SQL review rules to catch destructive queries before they execute.

Skip it (pick Adminer) if:

• You need a single-file emergency tool for occasional database access, not a team-facing production deployment.
• You’re running on minimal infrastructure and can’t spare 2GB+ RAM for a JVM.

Skip it (pick TablePlus or individual DBeaver licenses) if:

• Your team is small enough that per-developer licenses make more sense than running a server.
• Your developers prefer native desktop performance over a browser interface.

Skip it (stay on commercial CloudBeaver) if:

• You need MongoDB, Snowflake, BigQuery, Redis, or other non-standard database support — that’s enterprise territory [1].

---

Alternatives worth considering

• Bytebase — database DevSecOps platform. More governance features (SQL review, data masking, change workflows), 23 databases with deep integration, Go-based (lighter), stronger for teams with compliance needs. Not a SQL client replacement — a different category [1].
• Adminer — single-file PHP database tool. Supports 11+ databases, zero installation friction, but has no team access management and is a utility rather than a daily-driver client [Hostinger list].
• phpMyAdmin — MySQL/MariaDB focused, widely deployed, but UI is dated and scope is narrow.
• TablePlus — excellent native desktop GUI, one-time purchase ($59), no server mode for team sharing.
• DBeaver Desktop — the parent product. More powerful for individual developers; the paid PRO version unlocks everything CloudBeaver Enterprise has, but it’s a local install.
• Metabase — if your use case leans toward analytics dashboards and self-serve BI rather than raw SQL editing, Metabase serves that audience better.
• Redash — query-and-share tool, good at turning SQL into shareable dashboards. Complementary to CloudBeaver rather than a direct replacement.

---

Bottom line

CloudBeaver is a practical tool for a specific job: giving a team browser-based access to a shared SQL client without per-machine desktop installs. The Apache 2.0 license is clean, the DBeaver SQL engine is proven, and the Docker deployment works. If your team queries standard relational databases and doesn’t need governance features, the Community Edition is a legitimate free option that costs you only a VPS and some setup time.

The limits are real: ~20 databases in the free tier, no data masking at any price point, paid audit logs, and enterprise-only NoSQL/cloud warehouse support. Anyone evaluating CloudBeaver for a compliance-sensitive environment will hit those walls fast and need to look at Bytebase instead.

For non-technical founders specifically: if you need to give your analyst or ops person SQL access to your PostgreSQL database without handing them credentials and a desktop app setup guide, CloudBeaver CE on a $10/month VPS is a reasonable solution. If you need to control what they can see in the data — masking, column-level permissions, query review — CloudBeaver isn’t built for that, regardless of pricing tier.

If the deployment part is the blocker, upready.dev can handle it as a one-time setup.

---

Sources

1. Adela, Bytebase Blog — “Bytebase vs. CloudBeaver: a side-by-side comparison for web-based database management” (Apr 14, 2026). https://www.bytebase.com/blog/bytebase-vs-cloudbeaver/
2. Bytebase — Gaming use case page (secondary reference). https://www.bytebase.com/solutions/gaming/
3. Ethan Sholly, selfh.st — “This Week in Self-Hosted (9 August 2024)”. https://selfh.st/weekly/2024-08-09/
4. Hostinger — “VPS Docker Templates | One-Click App Deployment Templates” (Adminer listing referenced). https://www.hostinger.com/vps/docker

Primary sources:

• GitHub repository and README: https://github.com/dbeaver/cloudbeaver (4,740 stars, Apache 2.0 license)
• Official website and product overview: https://dbeaver.com
• Live demo: https://demo.cloudbeaver.io
• Docker Hub: https://hub.docker.com/r/dbeaver/cloudbeaver