Deploy Drizzle Studio with Tailscale

Deploy and Host Drizzle Studio with Tailscale on Railway

Drizzle Studio is a browser-based interface for your database. This template runs it on Railway behind a Tailscale service, so only devices on your tailnet can open it.

About Hosting Drizzle Studio with Tailscale

This template deploys Drizzle Studio, a browser-based interface for your database, together with a Tailscale service. Neither service gets a public domain. The Tailscale service joins your tailnet as its own machine and forwards its port to Drizzle Studio over Railway's private network. Your device reaches Drizzle Studio only through your tailnet. On the deploy form, pick your database service's connection string for DATABASE_URL from the reference list.

You do not generate or paste a key. The Tailscale service prints a sign-in link into its deploy log. You open the link, sign in, and the machine joins your tailnet. The log then prints the address to open in your browser.

Common Use Cases

• Browsing and editing your database schema from a private address.
• Running SQL queries and checking results without a public endpoint.
• Giving your team a shared database browser that stays off the open internet.

Dependencies for Drizzle Studio with Tailscale Hosting

• A database connection: PostgreSQL, MySQL, or MariaDB.
• A Tailscale account.

Deployment Dependencies

• Drizzle Studio
• Tailscale
• Railway Documentation

Why Deploy Drizzle Studio with Tailscale on Railway?

You need the Railway Hobby plan or higher. The Free plan allows one volume per project. Your database needs one volume, and the Tailscale service needs another. Railway hosts both services, so you do not manage servers or certificates.

Follow the full walkthrough in Drizzle Studio and Gateway on Railway with Tailscale built in. It covers the deploy form and the sign-in step.