Skip to content

Architecture

The shape of a Waveshift deployment — what runs where, how the control plane talks to the data plane, and what AWS resources get created.

In this section

  • System overview — high-level diagram of the components, the network topology, and the deployment phases.

Components at a glance

Control plane (issues commands, doesn't carry user traffic):

  • Orchestrator — the EC2 instance that runs the control plane. Runs the Web Console, holds the database, dispatches work to the data plane.
  • Console — the Web UI surface of the orchestrator. Served over HTTPS at console.<your-domain>.

Data plane (carries user traffic over WireGuard):

  • Egress Server — on-demand WireGuard server in the AWS region of your choice. Internet exits through this.
  • Infrastructure Server — WireGuard access server bridging a Site's Hub into a region.
  • Hub — GL.iNet Brume 2 router flashed with Waveshift firmware. One per Site.
  • Node — GL.iNet Slate AX router flashed with Waveshift firmware. Plug in, hand to user, every device on its Wi-Fi tunnels through the Site's Egress Server.

Optional:

  • Kasm Workspaces — containerised browser / desktop service on its own EC2 host. Routes egress through any Egress Server.

See also