Self-Hosting Conduit

Conduit is fully open source. You can run your own relay server on any machine that can accept inbound HTTP/WebSocket connections.

When to self-host

  • You need data to stay within your infrastructure
  • You want to run Conduit behind a corporate firewall or VPN
  • You prefer not to depend on a third-party service
  • You want multiple team members sharing one relay without individual accounts

Architecture

webhook provider → your relay server → CLI/VS Code on localhost

Your relay server needs:

  • A public IP or domain name (so webhook providers can reach it)
  • Port 80/443 open for inbound traffic
  • Docker (recommended) or Node.js 20+

What you’ll set up

  1. Deploy the relay — run the relay server with Docker or Node.js
  2. Configure the CLI — point conduit start at your relay
  3. Configure VS Code — point the extension at your relay

Auth modes

Self-hosted relays support two auth modes:

Open relay (RELAY_AUTH_REQUIRED=false) — anyone who can reach your server can use it. Suitable for private networks, VPNs, or single-developer setups.

Registration token (RELAY_REGISTRATION_TOKEN=your-secret) — clients must provide the shared token to register a slug. Simple shared-secret protection without individual accounts.

The default (RELAY_AUTH_REQUIRED=true with no token) mirrors the hosted relay’s auth requirements. Most self-hosters want RELAY_AUTH_REQUIRED=false.