i am not sure i would trust a two month old project "based on a three month old proof of concept" over a product that has been around for years, but it is good to know it is there
What to trust? Closed hardware/software that goes to trash if something goes wrong, or opensource that you can send an agent to debug if there are issues? I'm not trying to diminish JetKVM's product - for $35 its a steal if you don't want to bother with DIY and time involved, but I'd strongly disagree that opensource is less trustworthy than closed product.
Also they say they are open sourcing the reference implementation of the "JetKVM OS Services" and the firmware of the "JetKVM Mini".
My point is more that it is way easier to make mistakes in source than it is to review said source in a project like this. So, to me, it is kind of risky to use something very green that is meant to be used as a network appliance more or less.
Maintainer (espkvm) here. :) Thanks for the mention ;)
It started as a firmware for myself: I wanted a KVM, but not a Linux system inside one. A colleague talked me into publishing it and it grew from there. It runs on ESP32-P4 dev boards, no custom hardware.
I am not saying it is better than JetKVM. What I find more interesting is that the Mini landed on the same chip. Their stack is completely different from the Linux JetKVM, so it must be a rewrite from scratch - a sign the idea of a KVM without an OS holds up.
