PPelicanNET
Deploy

Stand up your comms server

A read-through of everything it takes to get your org's PelicanNET net live — from the Discord layout to the first radio check. Each step is something you do; the parts we handle for you (bringing the relay online, VPN peers) are noted but managed by PelicanNET.

Prefer it guided? The interactive Setup Wizard walks these same steps one at a time with built-in tools — a bot-invite builder, encrypted token submission, and live verification that ticks itself when your relay comes online. This page is the plain-English companion.

01 Create your Discord comms server

One move builds the whole PelicanNET layout — command net, five squad channels, roles, permissions.

Start a brand-new server

Creates a fresh Discord server already loaded with the full PelicanNET structure.
⚡ Create from the template

Or add it to a server you already run

Authorize the PelicanNET setup bot and it builds the category, channels, roles and permissions into your existing server. It needs Administrator to create the command roles — you can remove it once setup finishes.
Use the "Add to my server" tool →

02 Assign member roles

Channels stay hidden until people have a role.

In Server Settings → Members, give everyone a role: leadership the command roles, your leads the Squad Lead role, everyone else the member role. The PelicanNET channels appear the moment a role is assigned.

Squad Lead matters. Cross-squad relay keys are silently dead for anyone without the Squad Lead Discord role — assign it to every lead now.

03 Invite the six relay bots

One CommandNet bot + five squad bots (Alpha–Echo).

  1. In the Discord Developer Portal, open each bot application → General Information → Application ID.
  2. Build each invite with only the four voice permissions a relay needs — permission value 36701184 (never Administrator). The Setup Wizard's invite builder does this for you from the Client IDs.
  3. After authorizing, give each bot the Relay Bot role and confirm it can see its matching voice channel (View Channel + Connect + Speak + Use Voice Activity).
36701184

04 Bring the relay online

You submit your bot tokens; we provision the relay.

Submit your six relay bot tokens through the Setup Wizard — they're encrypted in your browser before they're sent, so only ciphertext is ever stored (Developer Portal → each bot → Bot → Reset Token).

Submit tokens in the wizard →
What happens next (our side): PelicanNET provisions your relay, the six bots connect, and they start sending a live heartbeat. The wizard's "Bring the relay online" step watches that signal and ticks itself the moment all bots are on station — you don't run anything.

05 Install your seat kit

You fly a seat too — connect the VPN and your control surface.

  1. Connect WireGuard first — buttons and keys do nothing until the tunnel is green (the relay only accepts traffic from inside the VPN).
  2. Grab your kit and the plugin / Comms Deck app from Downloads, then follow the seats & keys guide.
  3. Your seat-<id>.key is the only secret — never share it.
Open Downloads Install the deck apps → Seats & keys guide

06 Onboard your officers

Each officer needs VPN access to reach the relay.

Every officer creates their own WireGuard tunnel and sends you their public key (44 characters, ends in = — never the private key). Submit each one through Officer Onboarding.

Open Officer Onboarding
What happens next (our side): we add each officer as a VPN peer and send back a [Peer] snippet for them to paste into their tunnel. They connect, run ping 10.0.0.1 to confirm, and they're on the net.

07 Run the first radio check

Go / no-go before wheels-up.

Open the raid-night checklist and run the net check top to bottom — five squad uplinks, the broadcast check, and one cross-pair. Don't launch with a dead leg.

Open the raid-night checklist