Star Comms Premium

Run the net like you
own the spectrum.

Premium takes the same Star Comms your crew already runs and adds the org-level tools: more nets, custom org flair themes, dedicated shards, overlay broadcasts, and a real API for automation.

20 Premium Channels + Flair

Double your operation from 10 to 20 nets and give the client your org's own look.

Deep dive ↓ 50 Dedicated Shards

Your own routing node. Your hardware. Up to 50 nets and UDP voice.

Deep dive ↓ API Owner API

Scoped keys, live events, webhooks, metrics, and full op automation.

Deep dive ↓

Start the rundown

Pillar 01 — Premium Channels

Unlock 20 simultaneous nets.

Free orgs run up to 10 radio nets. Premium doubles the board to 20 and unlocks custom org flair theming, so the client can carry your org's colors, logo, and background during events.

How it works

The Discord account that owns your org server supports Star Comms on Patreon and gets the supporter role in the Star Comms Discord.
The owner claims Premium for the org — entitlement is verified against that supporter role automatically.
The net ceiling lifts from 10 to 20 instantly. The client Admin panel can add, rename, and manage the larger board without changing the member flow.
Custom org flair becomes available for the client, including branded palettes, logos, and backgrounds.
Entitlement re-verifies itself on a schedule with a grace window, so a billing hiccup never drops your nets mid-op.

No separate license keys, no manual renewals. If the supporter role is there, Premium is on.

Pillar 02 — Dedicated Shards

Your org's own routing node.

A dedicated shard is a private Star Comms routing process for one Discord guild, running on hardware you control — a home server, a VPS, a rack box at the org leader's house. Voice packets route through your shard. Identity stays with central.

CENTRAL STAR COMMS

Discord OAuth + role checks
Guild config + entitlements
Shard tokens + API key validation
Automatic fallback routing

YOUR SHARD

Live client connections
WebSocket + UDP voice routing
Owner API /api/v1/...
Events, metrics, ACARS

YOUR CREW

Windows / Linux clients
Auto shard routing
Central fallback if shard drops
Auto-return on recovery

50nets per shard

UDPlow-latency voice path

1guild per shard token

0Discord secrets on your box

What you actually run

One process. Windows operators get a signed installer and a control panel app; Linux operators get a single-file Node or Bun bundle. The shard registers its public URL with central, polls for guild config, and starts routing. npm run shard if you like terminals; the control panel if you don't.

The security model

Central issues one secret scsh_ token bound to exactly one Discord guild. Your shard stores only that token and a public URL. It never sees bot tokens, Discord client secrets, website credentials, or other orgs' traffic. Every joining client is validated against central before a single packet routes.

Failure is boring

Shard goes down? Clients quietly fall back to central routing and the op keeps moving. Central probes your shard every 15 seconds and steers everyone back the moment it's healthy. No rejoin drills, no panic in command net.

UDP voice routing

Dedicated shards run their own UDP voice router for the lowest-latency path, while mixed WebSocket and UDP clients on the same net still hear each other. Old clients keep working through every migration.

ACARS broadcasts

Premium shards can push ACARS-style text alerts straight onto every connected client's overlay — rally points, retreat calls, scheduled jumps — from the admin client or the API.

Entitlement, hands-free

Shard entitlement is tied to the owner's Patreon supporter role and re-verified automatically with a grace period. No 30-day manual date extensions, no surprise cutoffs mid-event.

Pillar 03 — Owner API & Integrations

Automate the entire operation.

Every dedicated shard ships with the Owner API: scoped scok_ bearer keys your org's developers use to build Discord bots, website status panels, attendance dashboards, and full op automation against /api/v1/....

ops-bot — live shard telemetry

$ curl -H "Authorization: Bearer scok_••••••••" https://shard.yourorg.net/api/v1/status
{ "operation": "open", "nets": 14, "connected": 87, "transmitting": ["Command Net"] }

$ curl -X POST .../api/v1/assignments/bulk -d '{"action":"assign","assignments":[...]}'
{ "applied": 42, "skipped": 0 }

$ curl -X POST .../api/v1/acars -d '{"text":"Rally at OM-1 in 5 minutes.","senderName":"Ops Bot"}'
{ "delivered": true, "clients": 87 }

Scoped keys, not master keys

Each integration gets its own key with only the scopes it needs. Keys are hashed at central, shown once, bound to one guild, and revocable at any time — from the shard control panel or the desktop client's Advanced API Integration tab.

Read

read:status operation, nets, occupancy read:roster connected operators read:assignments live assignment map read:metrics talk-time + Prometheus read:events SSE streams + webhooks read:audit API audit trail

Write

write:assignments assign, bulk, temporary TTL write:nets create, rename, remove write:operation open / close the op write:acars overlay broadcasts write:presets save + apply op layouts write:rules role-to-net auto assignment

Live events, two ways

Open a Server-Sent Events stream or register signed webhooks for user.joined, ptt.start, operation.opened, assignments.changed, and more. Every webhook delivery is HMAC-SHA256 signed so your endpoint can verify it came from your shard.

Operation presets

Save "Friday Convoy", "Fleet Night", or "Training Op" as a preset — nets, assignments, open state — and apply the whole layout with one API call before the first ship lifts off.

Metrics that brief well

Talk-time per user and net, occupancy sampling, uptime — as JSON or a Prometheus endpoint your Grafana already understands. Attendance dashboards and after-action reviews build themselves.

Website status, safely

A deterministic public status token powers read-only embeds and a prebuilt HTML widget for your org's website — so you never put a privileged key in browser JavaScript.

Role-to-net rules

Map Discord roles to nets once and let the shard auto-assign members as they join. Role-organized orgs get repeatable comms without an admin dragging chips every op.

Guardrails included

120 requests/minute per key, ACARS cooldowns, webhook failure quarantine, body-size limits, and a rolling audit log. The API is built to be handed to an org developer without fear.

What orgs build with it

/comms status

A Discord ops bot that posts who's connected and which nets are active.

Org site widget

Live status panel on the org homepage with net occupancy.

Auto-staging

A scheduler that applies the Friday preset and opens the op at 20:00 sharp.

Attendance board

Talk-time and presence exports for after-action reviews and promotions.

Event alerts

PTT-driven notifications when command net goes quiet or a VIP joins.

Free vs Premium vs Dedicated Shard

Capability	Free	Premium	Dedicated Shard
Simultaneous radio nets	10	20	50
Per-net PTT, spatial routing, overlay	Included	Included	Included
Chirps and static	Included	Included	Included
Custom org flair theming	—	Included	Included
Voice routing hardware	Shared central	Shared central	Your own node + UDP
ACARS overlay broadcasts	—	—	Included
Owner API + webhooks + metrics	—	—	Included
Central fallback safety net	n/a	n/a	Automatic

Ready to remove the ceiling?

Premium activates through Patreon.
Shards are issued in the Discord.

Support Star Comms on Patreon to unlock Premium for your org, then open a ticket in the Discord to get your dedicated shard token and the shard installer.

Support on Patreon Get a shard in the Discord

Run the net like youown the spectrum.