Connectivity between dev environments

Documentation for the non-Tailscale approach will be out soon!

Tailscale Setup

1. If you don’t have Tailscale created, sign up for an account here:

2. Go to the admin panel and generate an auth key from here: Be sure to set the following permissions:

        - Reusable

        - Ephemeral

   Save a copy of this key! You will need this key in the next section.

3. Enable MagicDNS here:

4. Get the name of the MagicDNS nameserver and save a copy.

Here, the nameserver is

DevZero Setup

1. Open up environments tab on the bottom left, select the template you would like to enable connection to Tailscale for, or create a new template. Find the environment.

2. Take that auth key, and set it as an environment variable for the environment template that needs to connect to remote resources. Give it an appropriate name, say TAILSCALE_AUTH_KEY.

Environment variables panel for a template

2. Add an entry into the scriptpolicy section of the environment template.


All newly generated machines will show up in the tailscale console (here:, and be connected to the tailnet.

Connect to another devbox

This is how you can construct the path to call an application on a devbox:

Example call from Devbox A:

Connectivity between dev environments
Enable TCP communication between running developer environments using Tailscale.
Source Code Management Integrations
DevZero supports GitHub (Cloud and On-Prem) and Gitlab.
The usage of tokens, passwords, and keys are a critical part to most development environments.
Basic Template Policy
Templates control how a DevZero “devbox” is created so that code is cloned, packages installed and custom commands are run.