Query databases and submit change issues across multiple Bytebase clusters without juggling tabs.
Users
16
+8 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#165K
#137K among extensions
Version
1.1.0
updated 10 Sep 2026
Users
monthly, 1 months
Latest, 16 Oct 2026:16 usersMove the mouse over the chart for any month
Ratings count
monthly, 1 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Bytebase Multi-Cluster Helper
If your team runs more than one Bytebase deployment — say production, staging and dev — then looking up a table or changing a column means bouncing between browser tabs, re-checking which environment you're in each time.
This extension puts them in one page.
[SQL query]
Pick a cluster, a project and a database, then write SQL against it.
· Resizable result columns; click an over-wide cell to read it in full in a side drawer, or view a whole column at once
· Copy the result as TSV to paste into a spreadsheet, or export JSON (the export keeps NULL distinct from an empty string, and big integers keep full precision)
· Keep several statements in the editor and run only the one you select
[Submit changes]
Tick databases across several clusters, write the SQL once, and submit a change issue to each cluster in one go, getting back every issue link. A confirmation step lists the environment of every selected database, with production highlighted.
[History, favorites and workspaces]
· Query history is recorded automatically (successful runs only) and can be starred
· Workspaces are named multi-statement scratchpads that autosave, so you can switch away and come back
[About your data]
You enter your own cluster URLs; the extension ships with none.
All requests go only to the URLs you configured. No analytics, no telemetry, no third-party services.
Configuration, history, favorites and drafts are kept on your machine. Synced storage is not used, so none of it reaches your Google account.
Query history records the SQL text and its target only — never the returned data.
[What you need]
One or more self-hosted Bytebase instances and a normal login on those sites. The extension reuses your existing browser session; it never asks for and never accepts a password or API key.