Skip to content

How is Waveshift deployed?

A Waveshift deployment is created end-to-end by wsctl. The partner engineer runs wsctl in an empty directory, walks through three short configuration dialogs, and clicks Deploy → All. The orchestrator, supporting services, and a first Control Hub (if requested) are all provisioned in about 10–15 minutes for a clean run.

Waveshift deployment process

The six stages

  1. Bootstrap — wsctl opens in an empty deployment directory. Pick AWS profile and identity account.
  2. Configure — Three dialogs: Infrastructure (region, domain), Waveshift (console subdomain, instance type, image versions), and Kasm (optional).
  3. Deploy → All — Saga-driven AWS rollout: infrastructure, certificates, Waveshift, Kasm. Live traffic-light status.
  4. First boot — Orchestrator initialises Postgres, applies the licence JWT (if one was supplied), and creates the default admin account.
  5. Add Control Hub (optional) — wsctl node-site create creates a Site and provisions its Infrastructure Access Server; wsctl hub configure then pushes WG keys to the Hub.
  6. Ready — Users can sign in to the Web Console and provision Egress Servers.

Each deploy step is idempotent: wsctl records every resource it creates in wsctl.json, so a failed run resumes from the last completed step on retry. Partners don't hand-write Terraform, don't manage AWS credentials manually (SSO is fine), and don't touch certificate issuance — all automated.

See also