GameComms alpha: multi-net voice for orgs

Hey all,

I fly with Morningstar Dynamics and I have been working solo on a project called GameComms since around the ASD worm patch. It is in alpha right now and I am looking for people willing to kick the tires and tell me what is broken or missing.

The short version

GameComms is a voice and coordination tool designed for gaming orgs. Star Citizen teams are what got me building it, but nothing about it is SC-only. Any organized group could use it.

You can try the alpha at app.gamecomms.com and read more about the project at https://www.gamecomms.com/.

Where things stand

The basics are up and running: orgs with roles, text channels, voice rooms, and DMs. Voice is WebRTC-backed with a real media server, so you get proper room presence and screen sharing where the browser supports it.

The part I am most focused on is multi-net push-to-talk. Inside a single voice room you can set up multiple nets like General, Commander, and Joint Ops. Each net controls who can listen and who can talk based on role, and you can add per-member overrides on top of that. Every net gets its own PTT keybind (Alt+1, Alt+2 out of the box, or bind whatever you want). Open mic is also an option if the net allows it. Priority transmission is working too, so command traffic ducks everything else and cuts through cleanly. Broadcast-all lets someone with the right permissions talk across every net at once. All of this is enforced server-side on the media path, not just in the UI, so a modified client cannot easily get around the permission model.

Joining up

Orgs generate invite links that can be locked to a specific role, given an expiration, and capped on uses. New signups and existing users both work through the same link. There is also a public server listed in the discovery tab. Drop into general chat there if you want to ask questions or leave feedback. Each org decides whether joining is instant or requires an application.

What I am asking for

Right now I just want real users putting real load on it so I can find the rough edges. Self-hosted deployment is on the roadmap for orgs that want full control, but that comes later.

I am also putting together a Kickstarter to fund the push to a polished release. When that is ready there will be a signup for notifications. Zero obligation.

One last thing

This community is a big part of why I started building tools like this in the first place. The needs are real and I want to keep solving them. Appreciate you reading this far. Fly safe.