Skip to content
LynxDockMenu

The LynxDock app

One desktop workspace for the whole community.

Text channels, voice and screen sharing sit beside the operations your community runs: rosters, assignments, a shared board, logistics and a record of what happened. Members use the app; whoever runs the community’s server uses LynxDock Host.

Closed beta · Windows (x64) · Push-to-talk is foreground-only (known limitations).

Product tour

Four views of one workspace.

Real screens from an earlier development build, with simulated demonstration data. The current generation refines them.

Communications

Text, voice and screen sharing, beside the work

  • Text channels with formatting, attachments and history, and presence for everyone in the community.
  • Voice channels and operation voice nets, with screen sharing in the same call.
  • Communications follow team assignments: a member is told which net their unit uses and can join it muted.
  • Roles decide who can read, post and speak where.
An operation text channel with call-sign messages from escort, transport, recovery and medical members, a Join voice control above the messages, and the member list with roles and reported status on the right.Demonstration data · earlier interface
Earlier development interface: V5 closed beta (build 0.1.0+5a53bff), captured 20 September 2026 on a staged demo server. Every member, ship and position is simulated demonstration data.

In-game companion

The overlay: your operation, without leaving the game.

A small click-through window shows the operation, open requests and numbered quick actions while you play. It is a separate window: nothing is injected into the game and no game memory is read.

  • Supported setups: games running windowed or borderless. Windows draws nothing above a game in exclusive fullscreen, so there the overlay stays hidden.
  • A companion interface: it shows what members and leaders enter in LynxDock. It does not read game telemetry.
  • Not blanket compatibility: whether it suits a given game and display mode depends on the build and the setup.
The compact in-game overlay: the operation name, six open requests, and a numbered row of quick actions such as Start mission, Log progress, On my way and Take it.
The compact overlay, shown at its actual proportions. Earlier development interface: V5 closed beta (build 0.1.0+5a53bff), captured 20 September 2026 on a staged demo server. Every member, ship and position is simulated demonstration data.
Game overlay settings: how the overlay opens, the interaction binding, quick-action and pointer controls, monitor, position, layout, scale and opacity, and a notice that the game must run windowed or borderless because nothing can draw above exclusive fullscreen.Earlier interface
Earlier development interface: V5 closed beta (build 0.1.0+5a53bff), captured 20 September 2026. The settings explain that the overlay is a click-through window and that it needs windowed or borderless mode.

Questions people ask

Who owns the server and the data?

Your community does. The application server and its records run on infrastructure you control, along with the voice and screen-sharing services. LynxDock Host helps the administrator set it up and look after it; running it, backing it up and keeping it updated stay the administrator’s job. More about Host.

Which games does LynxDock work with?

Star Citizen organisations are the current product context: fleet and convoy planning, ship and crew commitments, logistics and recovery. LynxDock has no game connectors: players enter what is happening, and nothing is read from the game. Arma, Squad and Discord connectors are proposals, not shipped integrations.

How do I join the beta?

The beta is closed and by invitation. Request access on the beta access page. If your community has already invited you, the tester hub has the installers and first steps.

Does push-to-talk work while I'm in a game?

Push-to-talk is foreground-only. The LynxDock window must have focus. Switching away releases a held press. After refocusing, release the key and press it again. Background PTT is separate development work.

This describes how push-to-talk is intended to behave in the current release line.

See LynxDock with your own community in mind.

We'll show you the workspace with demonstration data and talk through what running your own server involves.

Request a demo

We’ll walk you through LynxDock with demonstration data and answer questions about running it for your community. Invited testers looking for installers can go to the tester hub instead.