How tunguard/tanguard-binary works
TunGuard is a self-hosted connectivity control plane with a web dashboard. The principal workflow is an operator provisioning peers, then managing access and connectivity through the dashboard; the runtime also provides mesh links, TCP relay, domain HTTPS, DNS filtering, and SSH access. The graph follows the sampled startup, route, and service relationships. Some UI-to-API and unsampled subsystem links are documented capabilities rather than inspected call sites, so those links are dashed and unverified.
Main entry points: api.go HTTP API · main.go Server Startup · mesh.go P2P Mesh · policy_routes.go Policy Routes
Components 24
Runtime
- Server Startup
main.go - Configuration
config/config.go - HTTP API
api/api.go
Identity and Policy
- Dashboard Auth
auth/webcred.go - API Keys
auth/apikey.go - Policy Routes
api/policy_routes.go - Group Policy
policy/policy.go
Peer Connectivity
- Peer Registry
peers/peer_store.go - WireGuard
wg/wg.go - Peer Monitor
wg/peer_monitor.go - Mesh Routes
api/mesh_routes.go - P2P Mesh
p2p/mesh.go - P2P Transport
p2p/p2p.go
Network Services
- TCP Relay
trp/trp.go - Domain Routes
api/domain_routes.go - Domain HTTPS
domain/domain.go - DNS Routes
api/adguard_routes.go - AdGuard DNS
adguard/adguard.go
Web Dashboard
- Dashboard UI
webui/dashboard.js - Peer Management UI
webui/peers.js - Mesh UI
webui/p2p.js - Policy UI
webui/policy.js - Domain UI
webui/domains.js
Other components
- Operator
Connections 32
- Operator → Dashboard UI: manages
- Dashboard UI → Peer Management UI: opens peers
- Peer Management UI → HTTP API: requests peer operations
- Operator → Peer Management UI: provisions devices
- Server Startup → Configuration: loads
main.go - Server Startup → HTTP API: starts
main.go - Server Startup → WireGuard: starts
main.go - Server Startup → P2P Mesh: starts
main.go - Server Startup → AdGuard DNS: starts
main.go - Server Startup → Dashboard Auth: loads credentials
main.go - Server Startup → Peer Monitor: starts
main.go - HTTP API → Dashboard Auth: guards routes
- HTTP API → API Keys: authenticates automation
- HTTP API → Policy Routes: registers routes
- Policy Routes → Group Policy: manages groups
api/policy_routes.go - Policy Routes → Peer Registry: looks up peers
api/policy_routes.go - Policy UI → HTTP API: manages groups
- HTTP API → Mesh Routes: registers routes
- Mesh Routes → P2P Mesh: controls mesh
api/mesh_routes.go - P2P Mesh → TCP Relay: releases mappings
p2p/mesh.go - TCP Relay → P2P Mesh: sends node commands
trp/trp.go - Mesh UI → HTTP API: manages mesh
- HTTP API → Domain Routes: registers routes
- Domain Routes → Domain HTTPS: manages mappings
api/domain_routes.go - Domain HTTPS → TCP Relay: resolves relay targets
domain/domain.go - Domain HTTPS → AdGuard DNS: uses DNS service
domain/domain.go - Domain UI → HTTP API: manages domains
- HTTP API → DNS Routes: registers routes
- DNS Routes → AdGuard DNS: controls service
api/adguard_routes.go - Dashboard UI → HTTP API: views status
- WireGuard → Peer Registry: uses peer registry
- Peer Monitor → WireGuard: monitors peers