Star Comms Premium

Dedicated shards.
Two ways to run them.

Premium unlocks through the Command Net Supporter Patreon tier. You get a private routing shard for your Discord org — up to 50 channels, Global PTT, Public Net, Org Link, and ACARS. Choose Centrally Hosted when you want Star Comms to run the box, or Self Hosted when you want full control.

Compare hosting paths

Hosting paths

Centrally Hosted or Self Hosted.

Both paths start with Command Net Supporter on Patreon, then a dedicated Star Comms routing node with 50 channels. The difference is who runs the host — and how much control you keep over uptime and hardware.

Centrally Hosted

Star Comms runs the shard

Managed capacity without installing a host. Your admins still run the net.

  • 50 channels
  • Full API Access
  • Full URI Access
  • ACARS
  • Global PTT
  • Public Net
  • Org Link
  • Managed uptime by Star Comms
Best for

Non-technical orgs running 10–20 person operations that just need more capacity.

Open centrally hosted setup
Self Hosted

You run the shard host

Full integrations on your Windows or Linux box. You own uptime and routing.

  • Full API Access
  • Full URI Access
  • ACARS
  • Global PTT
  • Public Net
  • Org Link
  • 50 channels
  • Full control over uptime
  • Better control of routing capabilities
Better for

Large orgs running consistent large combined-arms operations that want full control of their services.

Self-hosted setup instructions

How shards work

Your org's own routing node.

A dedicated shard is a private Star Comms routing process for one Discord guild. Voice packets route through the 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 on Self Hosted
  • Events, metrics, ACARS
YOUR CREW
  • Windows / Linux clients
  • Auto shard routing
  • Central fallback if shard drops
  • Auto-return on recovery

What Self Hosted runs

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.

What Centrally Hosted runs

Star Comms provisions and operates the shard after Command Net Supporter entitlement checks (Patreon linked to Discord in the Star Comms support server). You keep normal shard admin controls without installing a host or managing ports.

The security model

Central issues one secret scsh_ token bound to exactly one Discord guild. A Self Hosted shard stores only that token and a public URL. It never sees bot tokens, Discord client secrets, website credentials, or other orgs' traffic.

Automatic fallback

If the shard goes down, clients fall back to central routing so the op can continue. Central probes the shard every 15 seconds and returns traffic when it is healthy again.

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.

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, on Self Hosted, the API.

Self Hosted — Owner API

Full automation when you run the host.

Both Self Hosted and Centrally Hosted shards expose the full Owner API: scoped scok_ bearer keys, URI launch links, service listeners, webhooks, and metrics. Self Hosted adds full control over uptime and routing on your own hardware.

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

What Self Hosted 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 Centrally Hosted vs Self Hosted

Capability Free Centrally Hosted Self Hosted
Simultaneous radio nets105050
Per-net PTT, spatial routing, overlayIncludedIncludedIncluded
Global PTT / Public Net / Org Link—IncludedIncluded
ACARS overlay broadcasts—IncludedIncluded
Voice routing hardwareShared centralStar Comms hosted + UDPYour own node + UDP
Owner API—Full API AccessFull API Access
URI launch links—Full URI AccessFull URI Access
Uptime / routing controlSharedManaged by Star CommsFull control
Central fallback safety netn/aAutomaticAutomatic

Get Premium

Premium activates through Command Net Supporter.
Then pick Centrally Hosted or Self Hosted.

Subscribe to Command Net Supporter on Patreon, join the Star Comms Discord, and link Patreon to Discord so the role syncs. Then choose Centrally Hosted when you want Star Comms to run the host, or Self Hosted when you want full control of uptime and routing on your own hardware.