Drizzle Studio

We never wanted to build a database browser

Can't believe this either.

Live demo
Alex Blokh
Alex Blokh
Co-founder of Drizzle
Product manager of Drizzle Studio
Book a call

Three years ago, when we shipped the first major version of Drizzle ORM and started gaining traction, our main audience — coming from Prisma — had two requirements: Relational Queries syntax and a local database browser.

We had commercial development experience and got things done with Beekeeper, Postico or TablePlus, so we declined multiple times, suggesting they just use the industry default tools. They were very insistent, and we gave up. How much time could it even take, we thought.

And we’ve built one. Drizzle Studio is a modern database browser — browse and edit your data, explore your schema and run SQL, with zero setup on top of your existing database. It now comes in five flavours:

Local Studiofreedrizzle-kit studio in your Drizzle project
Drizzle Gatewayfreeself-hosted Studio for your infrastructure, deployed as a Docker container or a binary
Chrome extensionfreebrowse serverless databases right in their vendor consoles
Studio ComponentB2B offeringembeddable Studio for your own product
Desktop appcoming soona native database browser, no terminal required

What you can do

Under the hood

At its core Drizzle Studio is a UI component which renders database content and gives you primitives to manipulate both data and schema. Being written in TypeScript lets us plug it in basically everywhere with zero friction:

Drizzle Studio family — for infra, for platforms and for local development

Drizzle Studio for local development

This is the original one, where it all started — and as of today, it has 120K monthly users. It’s meant to cover your development needs on a local env: rapidly open a particular database and manage everything you need in there.

With the introduction of Schema Management, we started to deviate from the original schema in code first idea towards a more conventional database browser, where the database itself is the source of truth.

It’s free forever and grabs everything it needs from your drizzle.config.ts file. It supports PostgreSQL, MySQL, SQLite, SingleStore, MSSQL and CockroachDB.

Install drizzle-kit, point it at your config and run drizzle-kit studio — the drizzle-kit studio docs walk through the setup, the --port, --verbose and --host flags, and what to do about Safari and Brave blocking localhost.

The hosted version of Studio is meant for local development and is not meant to be exposed on a remote machine — for that we have Drizzle Gateway.

Drizzle Gateway

Drizzle Gateway is a free self-hosted Drizzle Studio on steroids. It’s a single Docker image (or a standalone binary) that connects to all your databases at once and lives in your infrastructure like any other dockerised application — in your VPC, behind your bastion, with all the benefits that come with it.

Unlike drizzle-kit studio, Gateway doesn’t need a Drizzle project — you add database connections right in the UI, keep them in a persistent volume, share it with your team and protect access with a master password and per-user passcodes.

It was originally a paid service, but when Warhammer devs reached out to us we realised the friction of it being paid just doesn’t pay off, and eventually made it free. It’s now at 350k container downloads on the GitHub registry.

Deploy on Railway
# pull latest version
docker pull ghcr.io/drizzle-team/gateway:latest

# persistent volume is required for the configuration file
docker volume create drizzle-gateway

# start the gateway
docker run -d \
  --name drizzle-gateway \
  --restart always \
  -p 4983:4983 \
  -e PORT=4983 \
  -e MASTERPASS=your_master_password \
  -v drizzle-gateway:/app \
  ghcr.io/drizzle-team/gateway:latest

Once it’s running, Gateway is available at http://localhost:4983. It works on both arm and amd architectures, and standalone binaries are available for macOS and Linux — see gateway.drizzle.team for installation options and the changelog.

Drizzle Studio Chrome extension

Our Chrome extension renders the database browser right on top of your vendor’s UI — no local setup, no connection strings. It’s the thing you build when you can’t get inside a vendor’s console the official way, but you use their product every day and desperately need a proper in-place database browser.

It works with PlanetScale, Cloudflare D1 and Vercel Postgres.

Drizzle Studio button injected into the PlanetScale branches page

It’s at ~3.3k weekly users, so it does seem people needed one.

We also have sqlite.drizzle.studio to browse SQLite files right in your browser.

Drizzle Studio Component

Drizzle Studio Component is our paid B2B offering — a pre-bundled, completely framework agnostic and 100% secure web component of Drizzle Studio which you can embed into your UI — React Vue Svelte VanillaJS etc.

It’s an extremely powerful UI element that can elevate your offering if you provide Database as a SaaS or data centric SaaS solutions based on SQL, and it works just as well for private non-customer facing in-house usage.

It’s highly customisable: we have an advanced theming platform where you can see the component in your own colors before you talk to us, an opt-in SQL query runner and we can add various partner-specific customisations on demand 👍

While Studio for local development is free forever and meant to just enrich the Drizzle ecosystem, this one has been our main source of sustainable income — the one that fueled Drizzle open source development, up until PlanetScale happened.

You might’ve already seen one in a database or agentic platform you use 👇

Database platforms using Drizzle Studio
AI powered platforms for building apps and websites
Startups using Drizzle Studio
Platforms that used Studio before

We also have a set of companies using embeddable Drizzle Studio for internal use cases.

Launch posts: Neon · SQLite Cloud · Replit · Deno · Create.xyz

Interested?

Alex Blokh
Alex Blokh
Co-founder of Drizzle
Product manager of Drizzle Studio
Book a call

You can read a detailed overview on npm — @drizzle-team/studio is just a markdown file, there’s nothing to install there. We’re also around in DMs on Twitter and in the Discord #drizzle-studio channel.

Drizzle Studio desktop app

Everything Studio does, as a native application — no terminal, no drizzle-kit invocation, just open it and connect. It’s in the works, and it’s the one flavour you can’t try yet.

Follow us on Twitter or join Discord #drizzle-studio-desktop to hear when it ships.

FAQ

Is Drizzle Studio open source?

No. Drizzle ORM and Drizzle Kit are fully open sourced, while Studio is not.

Drizzle Studio for local development is free to use forever to enrich the Drizzle ecosystem, open sourcing it would’ve broken our ability to provide B2B offerings and monetise it, unfortunately.

Can I deploy Studio to my VPS?

Yes — that’s exactly what Drizzle Gateway is for. The hosted local.drizzle.studio version is meant for local development only.

Does Studio send my data anywhere?

No. Both drizzle-kit studio and Gateway run the database connection on your machine or in your infrastructure, your data never leaves it.

What’s next?

We ship Drizzle Studio updates every month — follow them on the announcements page.

Subscribe on Twitter and welcome to our Discord!