Skip to content
LynxDockMenu

Built for communities that play together.

Voice, chat and operations. Your server.

Keep the conversation and the plan in one place. LynxDock brings your community together in a desktop workspace, on a server you control.

Windows closed betaFor invited testers. LynxDock 0.3.1 is the current beta. Its in-app voice test over a secure remote connection, with real listeners, is still outstanding. Request beta access

The LynxDock tactical board during a simulated convoy operation. An assigned-comms banner offers to join the Command net muted; the board shows staging, objective, transit and extraction zones joined by routes, with escort, transport, scout, medical and recovery units placed along them; a side panel lists objectives with their status; a summary card reads en route, 28 of 32 units ready.
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.

1. Assigned comms

Each member is told which voice net their assignment uses and can join it muted in one step, so nobody has to ask where to be.

  1. Assigned comms. Each member is told which voice net their assignment uses and can join it muted in one step, so nobody has to ask where to be.
  2. One shared board. Units, wings, zones, routes and waypoints on a board the whole operation sees, with the current phase and how many units report ready.
  3. Objectives and progress. Objectives are grouped by unit with their status (complete, active or pending), so leaders can see what is left at a glance.

What LynxDock brings together

  • Stay connected.

    Text, voice and shared context.

    Channels, voice nets and screen sharing sit beside the work they are about.

    The product tour
  • Coordinate the operation.

    Rosters, assignments, routes, orders and review.

    One record carries an operation from the first draft to the debrief.

    How it works
  • Run your own space.

    Community server and Host administrator companion.

    Your community's server runs where you choose, and Host helps the person who looks after it.

    LynxDock Host

How it works

From the first plan to the debrief, in one place.

Follow one operation through four steps. Choose a step to see it in the app.

1. Plan

Plan the operation

Draft objectives, routes, waypoints and zones on a shared board, decide the phases, and place the units that will carry them out.

The tactical board in the planning phase: all units gathered in the staging zone, routes drawn to the objective and extraction zones, and every objective still pending.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.

Hosting

Members use the app. The administrator uses Host.

Your community’s server is yours to run. Members connect to it with the LynxDock app; whoever looks after it manages it with LynxDock Host.

Members

The LynxDock app

Everyone in the community installs the Windows desktop app and joins the server with an invitation.

Members connect to the server with the app

Your community server

Runs on infrastructure you control

The application server keeps permissions, operations and records. Voice and screen sharing run on their own media services beside it.

The administrator manages it with Host

Administrator

LynxDock Host

A Windows companion for whoever runs the server: setup, start and stop, diagnostics, access and backups.

Simplified illustration. Members’ connections go to the community server, not through LynxDock Host; Host is the administrator’s tool for managing that server.
What running a server involves

The technical foundation

Built for teamwork. Engineered for control.

A native desktop shell, a dedicated application server and a separate media service. Each has a clear job.

  • 01 / The desktop

    Rust + Tauri

    A Rust desktop shell uses the system WebView for a React and TypeScript interface.

  • 02 / The community

    Your application server

    A Rust service manages permissions, operation state and records on infrastructure your community controls.

  • 03 / The media

    Voice + screen sharing

    LiveKit carries real-time media; coturn provides a relay where direct connectivity needs help.

V8 is the current development generation. Tester availability is tied to an approved build.

Explore the technical capabilities

Beta status

A closed beta, on Windows, by invitation.

LynxDock is tested by invited communities that run their own servers. LynxDock 0.3.1 is the current beta. Its in-app voice test over a secure remote connection, with real listeners, is still outstanding.

Current stage
Closed beta, invited testers
Platform
Windows (x64)
Hosting
Run by each community, on infrastructure it controls
Current tester release
LynxDock 0.3.1, signed; its installers are on the tester hub; its in-app voice test with real listeners over a secure remote connection is still outstanding
Push-to-talk
Foreground-only: the LynxDock window must have focus

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.