twinbird 0.1.4

Manage multiple NetBird instances with isolated configs, sockets, and interfaces

twinbird

Manage multiple NetBird instances on a single machine with isolated configs, daemon sockets, and WireGuard interfaces.

Install

uv tool install twinbird

or

pip install twinbird

Usage

# Start a named instance
twinbird up office --management-url https://mgmt.example.com --setup-key YOUR_KEY

# Check status
twinbird status office

# List all instances
twinbird list

# Stop an instance
twinbird down office

Environment Variables

Instead of passing flags every time:

export TWINBIRD_MANAGEMENT_URL=https://mgmt.example.com
export TWINBIRD_SETUP_KEY=YOUR_KEY
twinbird up office

Variable	Purpose
TWINBIRD_MANAGEMENT_URL	Default management URL
TWINBIRD_SETUP_KEY	Default setup key
TWINBIRD_NETBIRD_BIN	Path to netbird binary (default: netbird on PATH)
TWINBIRD_CONFIG_DIR	Override root config directory

How It Works

Each named instance gets:

• Its own config directory (~/.config/twinbird/<name>/ on Linux, %APPDATA%/twinbird/<name>/ on Windows)
• A unique daemon socket address (Unix socket on Linux/macOS, TCP port on Windows)
• A unique WireGuard interface name (wt<N> on Linux, utun<N> on macOS)

Twinbird starts a separate netbird service run daemon per instance, then connects with netbird up — all fully isolated from the primary NetBird installation.

Requirements

• NetBird installed and on PATH
• Python 3.10+

License

MIT