---
title: "Deploy Tailscale for Drizzle"
description: "Put an existing Drizzle Studio or Gateway on your tailnet"
category: "Other"
url: https://railway.com/deploy/tailscale-for-drizzle
---

# Deploy Tailscale for Drizzle

Put an existing Drizzle Studio or Gateway on your tailnet

**[Deploy Tailscale for Drizzle on Railway](https://railway.com/template/tailscale-for-drizzle)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/tailscale-for-drizzle/manifest.json

- **Creator:** Drizzle
- **Category:** Other

## Template content

### Tailscale

- **Image:** ghcr.io/drizzle-team/railway-tailnet:v0.1.3

## Documentation

# Deploy and Host Tailscale for Drizzle on Railway

Tailscale for Drizzle adds a private address to a Drizzle Studio or Drizzle Gateway service that you already run on Railway. Only devices on your tailnet can reach it.

## About Hosting Tailscale for Drizzle

This template adds one Tailscale service to a project that already runs Drizzle Studio or Drizzle Gateway from the plain template. Deploy the browser service first, then deploy this template into the same project. The Tailscale service joins your tailnet as its own machine and forwards its port to your existing browser service over Railway's private network. It adds no public domain.

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.

On the deploy form, fill `TS_FORWARD_1`: type `4983:`, then type `${{` and pick `RAILWAY_PRIVATE_DOMAIN` of your Drizzle Studio or Drizzle Gateway service, then type `:4983`. The tutorial shows the full value.

## Common Use Cases

- Adding private access to a database browser you already deployed.
- Removing a browser's public domain once your tailnet reaches it.
- Reaching your database directly over the tailnet, alongside the browser.

## Dependencies for Tailscale for Drizzle Hosting

- An existing Drizzle Studio or Drizzle Gateway service in the same project.
- A [Tailscale](https://tailscale.com/) account.

### Deployment Dependencies

- [Tailscale](https://tailscale.com/)
- [Railway Documentation](https://docs.railway.app)

### Why Deploy Tailscale for Drizzle on Railway?

You need the Railway Hobby plan or higher. The Free plan allows one volume per project. This template needs one more volume than your project already uses, for the Tailscale service.

Follow the full walkthrough in [Add Tailscale to Drizzle Studio or Gateway on Railway](https://orm.drizzle.team/docs/tutorials/railway-tailscale-existing-project). It covers the deploy form, the sign-in step, and how to point the forward at your browser service.

## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/tailscale-for-drizzle