Outerbase Studio: a browser SQL GUI for SQLite, LibSQL and D1

What Outerbase Studio solves, and for whom

Most SQLite tooling is a desktop binary. That is fine until you want to open the same database from a browser, a colleague's machine, or a hosted environment such as Cloudflare D1 or Turso. Outerbase Studio targets that gap: it is a browser-based GUI for managing SQL databases, and the README states it was initially built for LibSQL and SQLite before widening support. The supported list is explicit. Under SQLite-based databases it names Turso/LibSQL, SQLite local files, Cloudflare D1, rqlite, StarbaseDB and Val.town. MySQL and PostgreSQL appear separately, each tagged beta with limited features. That split is the whole story of the project's audience. If your data lives in a SQLite file or a LibSQL-compatible endpoint, this is a first-class tool. If your data lives in Postgres, you are on the beta path, and the README says so rather than hiding it. The intended user is someone who wants to inspect tables, run ad hoc queries and adjust schema without installing a heavyweight client, and who is comfortable running a Next.js app themselves or clicking a deploy button.

How the browser app, drivers and dialects fit together

The repository layout points to a Next.js application deployed through OpenNext to Cloudflare, with a separate dialect build step. The package.json scripts include next dev on port 3008, an opennextjs-cloudflare build for preview and deploy, and a dialect script that runs node build-dialect.js. The presence of build-dialect.js and a dialect npm script suggests SQL dialect handling is generated or assembled at build time rather than hand-written per database, though the README does not describe the mechanism. Dependencies reinforce the browser-first design: CodeMirror packages for SQL and JSON editing, @libsql/client for LibSQL connections, and a set of Radix UI primitives for the interface. There is also @outerbase/sdk-transform, which the README does not explain. The connection manager is the part with a real architectural choice: the README says connections can be stored locally in your browser, or stored on a server so they are shared across devices. That second option means credentials leave the browser, and the README does not document how they are protected server-side. The desktop app is described as a lightweight Electron wrapper for the web version, existing to enable drivers that are not feasible in a browser environment, specifically MySQL and PostgreSQL. That is an honest admission that the browser build cannot reach those databases directly.

Installing Outerbase Studio and running a first query

The fastest path is the hosted instance. The README links a live browser version and a playground with a Chinook template, so you can open a sample database without installing anything. For self-hosting, the repository ships a Dockerfile that builds the Next.js app and copies the standalone server into a second node:20-alpine image. Note that the build stage runs npm install and npm run build, and the runtime stage starts the standalone server:

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
RUN npm run build

FROM node:20-alpine
WORKDIR /app
COPY --from=builder /app/.next/standalone ./
COPY --from=builder /app/public ./public
COPY --from=builder /app/.next/static ./.next/static
CMD ["node", "server.js"]

If you prefer to run from source, the dev script binds to port 3008:

npm install
npm run dev

After that, open http://localhost:3008 and add a connection. For a local SQLite file the README lists SQLite (local files) as a supported source. For Cloudflare D1 the README offers a deploy button that points at the repository URL, which provisions the app on Workers rather than running it locally. Whichever route you take, the first useful action is the same: open the query editor, run a SELECT, and check that the data editor stages your changes before you commit them.

Where Outerbase Studio is the wrong tool

The README's own labels are the clearest limitation. MySQL and PostgreSQL are beta with limited features, and the desktop app exists because browser drivers for them are not feasible. If your daily work is Postgres administration, you are outside the project's centre of gravity. Connection storage is the second constraint. Storing connections locally in the browser is convenient, but it ties your setup to one browser profile. Storing them on a server enables sharing across devices, and the README does not document access control, encryption at rest, or what happens if that server is exposed. That is a gap you have to close yourself before putting it on a network. The Dockerfile has a related quirk: it copies .next/standalone, which only exists if the Next.js build is configured for standalone output. The Dockerfile as written does not show that configuration, so a build from a fresh clone may not produce the directory the runtime stage expects. Finally, the AGPL-3.0 licence is a real consideration if you plan to host a modified version for other people; the repository ships a LICENSE file and a SECURITY.md, but the README says nothing about commercial terms.

How it differs from DBeaver and Beekeeper Studio

DBeaver and Beekeeper Studio are desktop clients. They install a JVM or an Electron app, they keep credentials on the local machine, and they connect to databases over the drivers bundled with them. Outerbase Studio inverts that: the primary artefact is a web application, and the desktop build is described as a wrapper around the web version rather than the other way round. The practical difference shows up in two places. First, reach. A hosted Outerbase Studio can be opened from any machine that can reach the server, which is useful for Cloudflare D1 and Turso, where the database is already remote and there is no local file to point a desktop client at. Second, the feature set is narrower by design. The README lists a query editor with auto-completion and function hint tooltips, a data editor that stages changes before committing, a schema editor for creating and modifying columns without writing SQL, and the connection manager. There is no mention of the deep driver matrix, ER diagram export or database-specific administration panels that desktop tools accumulate. The trade is deliberate: less breadth, browser access, and a SQLite-family focus.

Maintenance, releases and what the AGPL-3.0 licence means here

The most recent release listed is v0.10.2 from 2025-03-31, following v0.9.2 in January 2025 and v0.9.1 earlier that month. The package.json version matches at 0.10.2, and the default branch is develop rather than main, which is where new work lands. The last push to the repository was on 2026-03-25, so there is activity after the tagged release, but the release cadence itself has been quiet for roughly a year. Treat that as a signal to check the develop branch, not the release page, if you need recent fixes. Upgrade cost is low if you deploy the Docker image yourself: rebuild and restart. It is higher if you use the Cloudflare deploy button, because the build runs through opennextjs-cloudflare and you inherit whatever the current develop branch produces. The licence is AGPL-3.0, which the repository states in its LICENSE file. For internal use that is usually unremarkable. If you modify the code and offer it to users over a network, the AGPL's source-availability condition is the part to read carefully with your own counsel; nothing in the README describes an alternative commercial licence.

Editorial conclusion

Adopt Outerbase Studio if you work mostly with SQLite-family databases and want a self-hosted or Cloudflare-deployed GUI you can also run as a desktop app. Do not adopt it as your only client for MySQL or PostgreSQL production work; the README marks both beta with limited features, and the desktop wrapper exists precisely because browser drivers for them are not feasible. Before committing, verify two things: whether your deployment target matches the Dockerfile's standalone Next.js output, and whether the AGPL-3.0 licence fits how you intend to expose the app to users.

Frequently asked questions

Official sources

1. License: AGPL-3.0
2. outerbase/studio on GitHub
3. Project website
4. README
5. Releases