QuadScale/Documentation
Sign inGet Started

Getting Started

  • Introduction
  • Quick Start
  • Install the Agent
  • Onboarding Guide

Concepts

  • How QuadScale Works
  • Architecture
  • WireGuard Mesh
  • vs Traditional VPN

Identity & Access

  • SSO Integration
  • Access Policies
  • Device Posture
  • Users & Groups

Networking

  • Peer-to-Peer Connectivity
  • NAT Traversal
  • Subnet Routing
  • Exit Nodes
  • DNS Configuration

Operations

  • CLI Reference
  • Audit Logs
  • Monitoring

Integrations

  • Kubernetes
  • Terraform
  • API Overview

Self-Hosting

  • Cloud vs Self-Hosted
  • Deployment Guide

Security

  • Security Model

Documentation

How QuadScale Works

Understand the core concepts behind QuadScale mesh networking.

Control plane

The control plane manages identity, device enrollment, policy evaluation, route advertisements, and coordination between peers. It does not terminate encrypted WireGuard payload traffic.

Data plane

The data plane consists of QuadScale agents running on devices and infrastructure endpoints. Agents establish WireGuard tunnels directly when possible and fall back to relay nodes when NAT or firewall conditions require it.

Connection flow

  • Agent authenticates and registers with the control plane
  • Policy engine evaluates user, group, and device trust
  • Agents attempt direct peer connection using NAT traversal
  • Relay fallback is used only when direct paths fail
  • Audit events are recorded for connectivity and policy decisions

Previous

Onboarding Guide

Next

Architecture

On this page

  • Control plane
  • Data plane
  • Connection flow