Outerbase Studio keeps six SQLite targets in a browser tab and routes MySQL to a desktop app
A lightweight Database GUI in your browser. It supports connecting to Postgres, MySQL, and SQLite.
At a glance
- What is it?
- A TypeScript Next.js application at version 0.10.2 that reaches Turso, LibSQL, local SQLite files, Cloudflare D1, rqlite, StarbaseDB and Val.town from a browser tab, while MySQL and PostgreSQL sit behind an Electron wrapper and stay marked beta with limited features. The driver split, not the SQL editor, is what decides where this tool fits.
- Who is it for?
- Pick it when the data lives in one of the SQLite family targets and you want to stay inside a tab. Pass on it if you need PostgreSQL or MySQL parity, since both carry beta with limited features in this project.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Activity is slowing. The repository last received commits 7 months ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- outerbase/studio6,016 ★ · +38
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| outerbase/studio | 6k | 6k |
38 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Six SQLite targets open in the tab, two are routed to the Electron shell
The browser build reaches the SQLite-based targets: Turso/LibSQL, SQLite local files, Cloudflare D1, rqlite, StarbaseDB, and Val.town. MySQL and PostgreSQL are listed separately as beta with limited features, and the project sends them to the desktop app instead. That app is a lightweight Electron wrapper around the web version, built so drivers that are not feasible in a browser environment can still work. Windows and Mac builds are published from a separate outerbase/studio-desktop releases page, which means the two halves of the product ship and version on their own schedules.
Two storage modes for connections, and the shared one stays underspecified
Connections either stay in local browser storage on the machine that created them, which keeps them off a server but ties the list to one browser profile, or they get written to a server so the same set opens on several devices. Between those two sits the part that matters for self hosting, and it is the part with the thinnest documentation. The README names no host to point at, no auth scheme, no key format, and no statement about whether the stored payload is encrypted at rest or how it rotates. Shared connections across devices are a real reason to choose this tool, so probe that path before a whole team commits to it.
The data editor stages every change before anything is committed
Writes are not immediate. The data editor stages all changes and previews them before committing, so a bulk edit is reviewable rather than instant, and the project states the table handles thousands of rows and columns without bogging down. Next to it, the query editor offers auto-completion and function hint tooltips, runs several queries at the same time, and shows their results together, which matters when you want a shape query beside the rows it came from. The schema editor covers the other job: creating, modifying, and removing table columns in a few clicks with no SQL typed. What none of the three pages document is a transaction boundary, an undo path, or what a half applied change leaves behind.
Port 3008 in development, a standalone server.js inside the image
Everything moves through npm scripts, and the container fixes the order of operations. The Dockerfile copies package*.json, installs, copies the source, builds, then a second stage copies only /app/.next/standalone plus public and .next/static into a fresh node:20-alpine image whose command is node server.js. On a workstation, next dev -p 3008 is the loop, node build-dialect.js regenerates dialect data ahead of a build, and tsc --noEmit --skipLibCheck alongside jest covers the staged check. Cloudflare is a first class target: open-next.config.ts and wrangler.jsonc sit at the top level, and both preview and deploy shell out to opennextjs-cloudflare.
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
RUN npm run buildThe final stage is where the trimming happens, and it is also where surprises live, because only the standalone output survives into the second image.
The LibSQL client is pinned twice, once through overrides
package.json carries one pin worth noticing. @libsql/client appears in dependencies at ^0.5.3 and then again in an overrides block at the same range, which is the normal way to force a version down a dependency tree, so the LibSQL wire protocol level is deliberately held in place. The rest of the tree explains the shape of the interface: @codemirror/lang-sql for the editor, @codemirror/merge for diffs, @dagrejs/dagre for graph layout, @dnd-kit for sortable pieces, a long tail of @radix-ui primitives, and @phosphor-icons/react for iconography. @next/mdx and @mdx-js/loader are also in the dependency list, next to a top-level docs/ directory.
v0.10.2 shipped in March 2025 while develop moved in March 2026
Tags and branch have drifted apart. The three most recent tags are v0.9.1 on 2025-01-16, v0.9.2 on 2025-01-22, and v0.10.2 on 2025-03-31, and the version field in package.json still reads 0.10.2. The default branch is develop, its last push was 2026-03-25, and the repository is not archived. Nothing at the top level resembles a changelog, so there is no in repo record of what the newer commits touched or whether a release is close. The practical consequence is straightforward: cloning develop gives you source that no tagged build matches, and a self hosted deployment from the branch is your own risk to carry.
No exposed port, no .env.example, no changelog at the top level
Here is the self hosting gap in full. The root listing carries CODE_OF_CONDUCT.md and SECURITY.md but no .env.example, no changelog, and no CONTRIBUTING file. The Dockerfile declares no exposed port and takes no configuration arguments, so binding a service and passing settings into it are both left to the operator. For a first look that needs no infrastructure, the hosted try-it at libsqlstudio.com is the shortest route, including a playground client carrying the chinook template, while the README badge button pushes a Cloudflare Workers deploy instead.
Editorial conclusion
Pick it when the data lives in one of the SQLite family targets and you want to stay inside a tab. Pass on it if you need PostgreSQL or MySQL parity, since both carry beta with limited features in this project. Before a team depends on it, check the server side connection sharing yourself: no host, auth scheme, or encryption story is documented. Pin your build, because the newest tag is v0.10.2 from 2025-03-31 while the default branch received its last push on 2026-03-25.
Frequently asked questions
Does Outerbase Studio run MySQL and PostgreSQL inside the browser?
No. Both are marked beta with limited features, and drivers that are not feasible in a browser environment are what the Windows and Mac Electron desktop app exists to cover.
Which databases can Outerbase Studio open without installing anything?
Turso/LibSQL, SQLite local files, Cloudflare D1, rqlite, StarbaseDB, and Val.town. A hosted try-it sits at libsqlstudio.com, including a playground client loaded with the chinook template.
What version of Outerbase Studio is in the repository right now?
package.json declares 0.10.2, and the newest release tag is v0.10.2 dated 2025-03-31. The default branch is develop, and its last push was 2026-03-25.
Can Outerbase Studio share connection profiles across several devices?
The connection manager can write connections to a server so they open on multiple devices, or keep them locally in the browser. No host, authentication scheme, or at rest encryption detail is given for the server mode, so verify it directly.
Do data edits in Outerbase Studio hit the database immediately?
No. The data editor stages changes and previews them before committing, the query editor runs several queries at once and shows their results together, and the schema editor adds, changes, and drops columns without typed SQL.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/outerbase-studio)Star history chart for your README
[](https://hysenlabs.com/projects/outerbase-studio)Was this useful?