49d62f8eb0
|
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| .vscode | ||
| bin | ||
| cmd | ||
| internal | ||
| resource | ||
| tools | ||
| ui | ||
| .gitignore | ||
| .golangci.yml | ||
| CODE_OF_CONDUCT.md | ||
| DEVELOPMENT.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| audio_handlers.go | ||
| audio_session_provider.go | ||
| block_device.go | ||
| block_device_linux.go | ||
| block_device_notlinux.go | ||
| cloud.go | ||
| config.go | ||
| dc_metrics.go | ||
| dev_deploy.sh | ||
| display.go | ||
| go.mod | ||
| go.sum | ||
| hidrpc.go | ||
| hw.go | ||
| jiggler.go | ||
| jsonrpc.go | ||
| log.go | ||
| main.go | ||
| mdns.go | ||
| native.go | ||
| native_linux.go | ||
| native_notlinux.go | ||
| network.go | ||
| ota.go | ||
| prometheus.go | ||
| publish_source.sh | ||
| serial.go | ||
| session_provider.go | ||
| terminal.go | ||
| test_usbgadget | ||
| timesync.go | ||
| usb.go | ||
| usb_mass_storage.go | ||
| version.go | ||
| video.go | ||
| web.go | ||
| web_tls.go | ||
| webrtc.go | ||
| wol.go | ||
README.md
JetKVM is a high-performance, open-source KVM over IP (Keyboard, Video, Mouse, Audio) solution designed for efficient remote management of computers, servers, and workstations. Whether you're dealing with boot failures, installing a new operating system, adjusting BIOS settings, or simply taking control of a machine from afar, JetKVM provides the tools to get it done effectively.
Features
- Ultra-low Latency - 1080p@60FPS video with 30-60ms latency using H.264 encoding. Smooth mouse, keyboard, and audio for responsive remote control.
- First-Class Audio Support - JetKVM now supports bidirectional, low-latency audio streaming using a dual-subprocess architecture with ALSA and Opus integration via CGO. Features both audio output (PC→Browser) and audio input (Browser→PC) with dedicated subprocesses for optimal performance and isolation.
- Free & Optional Remote Access - Remote management via JetKVM Cloud using WebRTC.
- Open-source software - Written in Golang (with CGO for audio) on Linux. Easily customizable through SSH access to the JetKVM device.
Contributing
We welcome contributions from the community! Whether it's improving the firmware, adding new features, or enhancing documentation, your input is valuable. We also have some rules and taboos here, so please read this page and our Code of Conduct carefully.
I need help
The best place to search for answers is our Documentation. If you can't find the answer there, check our Discord Server.
I want to report an issue
If you've found an issue and want to report it, please check our Issues page. Make sure the description contains information about the firmware version you're using, your platform, and a clear explanation of the steps to reproduce the issue.
Development
JetKVM is written in Go & TypeScript, with some C for low-level integration. Audio support uses a sophisticated dual-subprocess architecture with CGO, ALSA, and Opus integration for bidirectional streaming with complete process isolation.
The project contains two main parts: the backend software (Go, CGO) that runs on the KVM device, and the frontend software (React/TypeScript) that is served by the KVM device and the cloud.
For comprehensive development information, including setup, testing, debugging, and contribution guidelines, see DEVELOPMENT.md.
For quick device development, use the ./dev_deploy.sh script. It will build the frontend and backend and deploy them to the local KVM device. Run ./dev_deploy.sh --help for more information.
Backend
The backend is written in Go and is responsible for KVM device management, audio/video streaming, the cloud API, and the cloud web. Audio uses dedicated subprocesses for both output and input streams, with CGO-based ALSA and Opus processing, IPC communication via Unix sockets, and comprehensive process supervision for reliability.
Frontend
The frontend is written in React and TypeScript and is served by the KVM device. It has three build targets: device, development, and production. Development is used for the cloud version on your local machine, device is used for building the frontend for the KVM device, and production is used for building the frontend for the cloud.