Technology & capabilities
The engineering behind the teamwork.
A desktop workspace for communications and operations, built around services your community can run and records it can control.
V8 development overview · Release availability is build-specific.
| Desktop shell | Rust / Tauri |
|---|---|
| Interface | React / TypeScript / Genesis UI |
| Application server | Rust |
| Shared contracts | Generated Rust → TypeScript types |
| Voice & screen sharing | LiveKit SFU / coturn relay |
Architecture
One workspace. Two connection paths.
Application state and real-time media use separate services. Voice does not pass through the Rust application server.
On each member’s PC
LynxDock desktop app
Rust and Tauri shell, React and TypeScript interface.
It opens separate connections to each service.
1Application state
Desktop app → Rust application server
Desktop appRust application serverPermissions, operation state, recordsTyped RPC over WebSocket: permissions, shared operation state, action revisions and persistent records.
2Real-time media
Desktop app → LiveKit SFU
Desktop appLiveKit SFUVoice and screen-share distributionVoice and screen-share tracks, distributed by the selective forwarding unit.
3Media via TURN
Desktop app → coturn (TURN relay) → LiveKit SFU
Desktop appcoturn (TURN relay)Relays the connectionLiveKit SFUSame media serviceUsed when a direct connection to the media service needs help to get through the network.
Shared contracts
Client types are generated from Rust definitions. Automated checks catch stale generated output and help keep the two sides aligned.
Capabilities
What the system brings together.
Capabilities described in the V8 development record. Each tester release has its own qualification and supported configuration.
A shared tactical picture
Units, wings, objectives, routes and waypoints, with orders, alerts and reported readiness in one operation.
Logistics with context
Stock by location, reservations and transfers, plus requests for refuel, repair, medical, recovery and escort support.
Connected communications
Text channels, voice, screen sharing and presence, with communications associated with team assignments.
Role-aware communities
Role-based access, member profiles and per-community preferences, alongside a personal view of assignments and outstanding actions.
An in-game companion
A click-through overlay for supported windowed or borderless setups, using a separate window without game injection or memory reading.
A record to learn from
Operation timelines, acknowledgments, board snapshots and replay keep the plan and reported outcomes available for review.
Hosting
Control, with a clear operating model.
LynxDock Host helps with setup, access, diagnostics and recovery. The administrator remains responsible for running the services.
Application & records
Provide the server, storage, backups, updates and community administration.
Voice & connectivity
Plan for media capacity, bandwidth, service credentials and network reachability. A relay adds connectivity, not free bandwidth.
Resource requirements
CPU, memory, GPU use and capacity depend on the build and workload. No fixed usage figures or user-count guarantees are claimed here.
Expectations
What to expect, plainly.
Plans and reports, not game telemetry.
Players supply operational information. LynxDock does not automatically move game inventory or verify that an objective was completed.
Integrations have their own scope.
Star Citizen is the current product context. Arma, Squad and Discord connectors are proposals, not shipped integrations.
A development generation, not a release number.
V8 describes product development. Windows compatibility and available features belong to the approved package. Current release-line push-to-talk requires app focus; background input is separate development, unless newer approved release evidence changes that status.
See the system in action
A walkthrough with demonstration data, and time for questions about architecture, hosting and fit.