Stringers
espkvm/espkvm · espkvm

JetKVM open-sourced its firmware 8 days ago, and a front-end engineer has flashed his own ESP32 KVM onto the box: how a hardware side project gets 700 stars

What it is: open-source firmware. An ESP32-P4 dev board plus an HDMI capture board, with no soldering, lets you see another computer's screen in a browser and control its keyboard and mouse, including getting into the BIOS. It doesn't run Linux, and it can be flashed onto a JetKVM Mini.

Why it took off: the author turned someone else's working prototype into a full-featured finished product, then pushed it himself to Hackster, Hackaday, CNX, and r/esp32 within a week in late July, and built a press page for journalists. In November JetKVM open-sourced the Mini's firmware, and within 8 days he had his firmware running on that box, which made it into the JetKVM user community.

CHow to play it Don't build yet another ESP32-P4 KVM. Copy the play: take a hardware project whose prototype already works but whose original author has stopped maintaining it, and finish it into a complete product. Or wait for a big company to release an open-source firmware on a new chip, then ship a third-party firmware for it. At launch, pack your own project page, a hardware media pitch, a Reddit post and a press page into one week.

Grade C: the ESP32-P4 KVM slot is already taken by someone who ships a release every day or two, the libraries that followed each have only 5 stars, and the category benchmark PiKVM took seven years to reach ten thousand stars, so the ceiling is low. The playbook is worth learning, but following it directly isn't worth the effort. What's circulating in small circles
Data (updated daily) · Repo created 2026-07-22 · 701 stars · 7 days +104
GitHub · stars
50060070010-0910-1711-0211-1111-20701
Data 2026-10-09 → 2026-11-20 (43 days, 35 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

espkvm/espkvm is an open-source IP-KVM firmware: an ESP32-P4 dev board plus an HDMI capture board lets you see another computer's screen in a browser and control its keyboard and mouse, including getting into the BIOS. Its foundation is someone else's prototype, which had only 161 stars; it turned that into something usable, and in four months since the repo was created it has shipped 88 versions and reached 700 stars. The stars came mainly from two waves: a week of media exposure the author organized in late July, and a third-party firmware for the JetKVM Mini, which uses the same chip, in November. Below is how it got there, and what someone trying to get stars for their own open-source project can take from it.

Nov 12, a JetKVM Mini on the desk

On Nov 12, 2026, Lithuanian front-end engineer Evgenij Spitsyn (dexif on GitHub) posted a short write-up on his project blog titled "Custom firmware for the JetKVM Mini is ready":

"The JetKVM Mini has an ESP32-P4X inside, the same chip ESP-KVM runs on. JetKVM open-sourced its firmware, so the pinout is known. I have a Mini on my desk, and everything I tried works."

JetKVM is the hottest low-cost IP-KVM finished product of the past couple of years. The Mini it released in September sells for $33–39 (jetkvm.com), and in Nov 4 it open-sourced the Mini's firmware. 8 days later, ESP-KVM could be flashed onto it: video at 1080p50, networking, keyboard and mouse, the small screen, and microSD were all tested, and the blog post includes a video of the flashing and update process, plus a note saying "thanks JetKVM, this approach and the USB descriptors come from your firmware." (The Mini's HDMI audio line isn't wired to the chip, so he added a virtual USB speaker, following JetKVM's approach.) He posted it to r/jetkvm.

The repo had 594 stars that day. Over the following week a post titled "I built a tiny IP KVM for $31 with an ESP32-P4 — no soldering" appeared in r/homelab, from u/Many-Call-4492, who said they had "only recently discovered ESPKVM." From Nov 16 to 18 the count rose by 62 stars over two days, and by the evening of 18 it was 698 (GitHub, 11-18). In the last 7 days it gained 101, against only 16 in the 7 days before that.

What it is: two boards, one ribbon cable

An IP-KVM is remote desktop for a computer that won't boot. A server or NAS sits in a closet, and one day it won't come up: no ping, no SSH. You can't tell whether it's stuck in the BIOS, the kernel crashed, or, as the author put it, "three weeks ago I swapped the RAM, and it's politely waiting for someone to press F1" (from the author's project page on Hackster, 07-29). Without hauling a monitor over there, you can't see anything. An IP-KVM plugs into that machine's HDMI and USB, captures the screen into a browser, and pretends to be its keyboard and mouse.

Most IP-KVMs on the market are basically a small Linux computer: PiKVM runs on a Raspberry Pi, JetKVM on Rockchip. ESP-KVM is different in that there's no Linux inside, just microcontroller firmware of about 1MB. The homepage pitches this as three benefits: a sudden power cut won't corrupt the filesystem, and it's up in about 15 seconds; two firmware partitions, so a failed upgrade rolls itself back; and no shell, no SSH, which means fewer attack surfaces. The tradeoff is video at only 20–27 fps, well short of the 1080p60 that Linux-based setups deliver (per the official FAQ).

The hardware is an ESP32-P4 dev board (the author uses the Waveshare ESP32-P4-ETH, about $20 on Amazon) plus a Geekworm C790 HDMI capture board ($23.90), connected by the ribbon cable that comes with it, so no soldering. CNX Software estimated the whole setup at about $45, and said plainly, "given the price of entry-level IP-KVMs today, you won't save money" (CNX, 07-30). The poster in r/homelab paid $31 all in. So what it sells isn't low cost; it's open source, build-it-yourself, and no OS to install.

The feature list is more than you'd expect from a personal project: H.264 hardware encoding, a virtual CD drive (boot an OS from an SD card, a URL, or a local file), power button control, copying text from the BIOS screen, sending a Telegram or ntfy alert when a given word appears on screen, built-in Tailscale and WireGuard, Home Assistant integration, VNC, and an MCP server for AI agents. It supports 17 different vendors' P4 dev boards, each with a rating; you can flash it in the browser by plugging in USB; and demo.espkvm.io lets you try the console without buying a board.

Its predecessor had only 161 stars. Why does it have 700?

The hardest part wasn't what it did. In June, developer Jonathan Rowny first got the TC32 capture chip running on an ESP4-P358743 and released the prototype p4kvm; in July 3 it hit Hackaday. But he himself called it a proof of concept with "lots of bugs and no security measures" and encouraged others to fork it (CNX, 07-30). p4kvm is at 161 stars now.

Spitsyn built the library and turned it into a finished product in July 22. What separated 161 from 700 comes down to the points below.

Within a week, it showed up everywhere at once. On July 29 he posted a project page he wrote himself on Hackster, with a bill of materials and "walls I hit"; the next day Hackaday and CNX both covered it, and on July 31 Hackster's official news followed, then the RISC-V International weekly, Italian and Philippine electronics sites, and later reposts translated into French, Spanish, Russian, Chinese, Japanese, German and more. On August 7 he posted "I built an open-source IP-KVM out of a cheap ESP32-P32" in r/esp4, which got 204 votes and 36 comments; the same day he opened a Hackaday.io project page. In late August he went to the Home Assistant forum, and in September to the M5Stack forum. By October 9 it had 503 stars, and more than 70% of them came from that launch wave.

A page built specifically for journalists. espkvm.io/press opens with "If you're writing about this project, feel free to use anything useful on this page." For each blurb it offers 4 alternative phrasings, changing on each refresh, with the reason given: "so two people writing about it the same week don't post the same sentence". Quotable numbers, limitations, and images are all laid out ready to use. The official site lists more than a dozen independent articles, including a Chinese piece on smzdm. This move is rare in personal open-source projects.

Credit the original author first. The README's first screen says "The hardest part was solved by jrowny/p4kvm; without it, this project wouldn't exist." Rowny publicly backed the project in his r/esp32 post. The hardware community pays attention to this: a project built on someone else's prototype drew no backlash, and instead gained someone speaking up for it.

Fast updates, and he writes them up. About 286 of the 288 commits are his own; from 9 through November he shipped a version every day or two, each with a blog post written in plain language ("VNC is now as fast as a browser: on the JetKVM Mini, 1080p went from 6–11 fps to 26 fps", 0.86,11-16). His day job is front-end, and both the website and the 44KB console look like a commercial product.

Riding a big company's momentum. On Sep 13 the JetKVM Mini launched and scored 573 points on HN; he replied to the thread as "Maintainer (espkvm) here", and someone in the r/homelab launch thread also recommended it in passing. Once JetKVM open-sourced its firmware, he flashed his own firmware onto it. JetKVM buyers were already looking for IP-KVMs and already owned this hardware, so r/jetkvm was effectively a ready-made target audience.

Going the other way, the misses are worth noting too: someone posted its site on HN and got 3 points; several blog posts he later published each got 2 points. It has also never trended on GitHub.

How the stars came

TimelineStarsWhat happened
07-220Repo created
07-29 ~ 08-07—Self-posted Hackster project page → Hackaday and CNX coverage the same day → Hackster news → self-posted r/esp32 thread, 204 votes
09-13—JetKVM Mini launches; the author replies to the HN thread as maintainer
10-09503The launch wave is mostly over; after that it gains 1–6 stars a day
11-04—JetKVM open-sources Mini firmware
11-125940.83 release: "Third-party firmware can now be installed on the JetKVM Mini", posted to r/jetkvm
11-16617Around the r/homelab "build one for $31" thread
11-18698+62 in two days

(Starting 10-09, these are GitHub's daily star counts; there is no daily data for 7–September, so the ~500 stars at launch is an estimate.)

Who it's competing with

ProjectWhat it isStarsCompared with alternatives
PiKVMRaspberry Pi + Linux; open source, also sold as a finished product10.5kThe category benchmark, 1080p60, expensive
Sipeed NanoKVMA small RISC-V Linux box6,621Cheap finished product, with a past security controversy
JetKVMRockchip + Linux finished product5,449The hottest cheap finished product, still climbing 30 in the last ~179 days
JetKVM MiniA finished product on the same ESP32-P4X chip, $33–39Firmware library, 27The most direct rival, and also its "host"
jrowny/p4kvmThe prototype ESP-KVM grew out of161The hardest part was built by this one
sskvm, ESP32-P4-Low-Cost-KVMSimilar projects that appeared between 9 and NovemberEach 5Copied the same thing, nobody noticed

(GitHub, 11-19.)

The IP-KVM category is already crowded, with GL.iNet, Luckfox and Radxa still releasing cheap finished products. But in the "microcontroller, no OS" slot, there was only one prototype as of July, and ESP-KVM now holds it. The two libraries that followed each have 5 stars, which suggests another ESP32-P4 KVM no longer makes sense.

If it were you

C: The playbook is worth copying, but following it directly isn't worth it. The ESP32-P4 KVM slot is already held by someone shipping a version every day or two; latecomers sit at 5 stars each, and the category ceiling is low too: the benchmark PiKVM took seven years to reach 10,000 stars. What's worth learning is how it grew 161 stars out of a prototype with 700 stars, and the move of building open-source firmware for a popular piece of hardware on the same chip.

Who it's for: developers who can write embedded firmware and already have a board with a newly released chip; people willing to put the same care into a website, docs and a release cadence as they would into a product.

Who it's not for: anyone wanting to build yet another ESP32-P4 KVM; anyone who doesn't touch hardware (stars on projects like this mostly come from hardware hobbyists who actually want to build one, an inference); anyone expecting thousands of stars in a couple of weeks (the hardware community is small, and this project took four months and 88 versions to reach 700).

How to do it:

  1. Look for hardware projects whose prototype already works, where the author has said they don't plan to maintain it. Hackaday and CNX feature new chip proof-of-concepts every week. Someone has already done the hardest step; what's missing is making it complete, secure, and flashable. Before taking one over, reach out to the original author, and state clearly in the README's first screen who did what.
  2. Watch for the moment a new chip lands in consumer hardware. When a big company adopts a chip and open-sources its firmware, build third-party firmware for it and go straight to its user forums. Over the next few years, ESP32-P4 and various RISC-V microcontrollers will keep showing up in more finished products.
  3. Build in an ecosystem nobody is looking after. One-KVM shows the Chinese homelab community wants this, while ESP-KVM's docs and community are all in English, and sskvm, the Chinese-language library in the same space, stopped halfway.
  4. Treat the website as a product: browser-based flashing, an online demo, and a page per supported board with a rating (which also captures search traffic).

How to get users: compress the launch into one week. First post a project page you wrote yourself on Hackster or Hackaday.io, pitch Hackaday and CNX, and the next day post on the relevant Reddit community in an "I built…" voice. Make a press page with the numbers, the limitations, and several ready-made blurbs, so writers have less work to do. Don't count on HN: this project's own HN posts all scored 2 points.

When to get in early: the first few months after a new chip comes out. The ESP32-P4 slot was still empty in July, and in September the JetKVM came in with a finished product.

What would signal you read it wrong: ① JetKVM's own Mini firmware gets good enough and the community active enough that ESP-KVM's stars drop back to single digits per day, which would mean "riding a big company" was a one-time boost; ② someone with no media push, relying on a single Reddit post, takes a similar hardware project to several hundred stars, which would mean this launch playbook isn't that critical; ③ you run the same approach on another new chip and it doesn't reach 100 stars within a month, which would mean the heat came from IP-KVM being a topic the homelab crowd already cares about, and a different category won't necessarily work.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
PiKVMOpen source2019pikvm/pikvm 10,478 stars; also sells finished hardwareRaspberry Pi with Linux, 1080p60, the finished product is expensive; ESP-KVM is cheap and has no OS, but manages only about 20–27 fps
Sipeed NanoKVMOpen source2024-076,621 stars; sells finished productsA cheap RISC-V Linux finished product; ESP-KVM is microcontroller firmware that runs on an off-the-shelf dev board
JetKVMOpen source2024-10jetkvm/kvm 5,449 stars, +30 in the last ~179 daysThe hottest cheap finished product (Rockchip + Linux); ESP-KVM is DIY firmware
JetKVM MiniOtherLaunched 2026-09-13, shipping from late OctoberPriced at $33–39; launch post scored 573 on HN, the r/homelab shipping thread got 336 votes; firmware jetkvm/mini has 27 starsA finished product on the same ESP32-P4X chip; ESP-KVM can be flashed onto it as third-party open-source firmware, and the two ride on each other's momentum
TinyPilotOpen source2020-063,491 stars; commercial hardwareRaspberry Pi design, aimed at enterprises, with paid support
One-KVMOpen source2023-112,629 starRust software solution that runs on various small Linux boards, mainly used by the Chinese community
GL.iNet Comet / Luckfox PicoKVM / Radxa LinkrOther2025–2026Not verifiedA cheap, plug-and-play Linux finished KVM; ESP-KVM requires you to buy two boards and assemble them yourself
jrowny/p4kvmOpen source2026-06-22161 starThe prototype ESP-KVM grew out of; its author called it buggy with no security. ESP-KVM added HTTPS, a virtual CD drive, VPN and more on top of it
IPMI/BMC, Intel vProBig-company featuresVery earlyStandard on servers and business machinesRegular desktops, mini PCs and SBCs don't have it; ESP-KVM fills that gap from the outside
Where users come from
  • Verified Hardware media coverage clustered: Hackaday and CNX Software covered it on 2026-07-30, Hackster News on 07-31, followed by the RISC-V International weekly, Circuit Rocks, and 1612.it, then reprints in several languages
  • Verified The author posted on Reddit and niche communities: u/spitsynnet posted in r/esp32 on 08-07, getting 204 votes and 36 comments; posted in the HA community (08-25) and the M5Stack community (09-22); replied in older r/homelab threads recommending it
  • Verified Self-published project pages on Hackster and Hackaday.io: the hackster.io/dexif project page went up on 07-29, a day before the media coverage; the Hackaday.io project page 08-07
  • Verified A press page written for journalists: espkvm.io/press shows 4 randomized wordings for each intro, with quotable numbers, limitations and images, and states that the material can be used without permission
  • Verified: riding the JetKVM Mini (a big-brand finished product on the same chip): 09-13 a JetKVM Mini thread on HN (573 points), whose author replied as a maintainer; an r/homelab post recommended it; 11-04 JetKVM open-sourced the Mini firmware, 6 days later ESP-KVM 0.80 shipped Mini firmware, 0.83 posted to r/jetkvm
  • Inferred The r/homelab "$31 no-solder" post: titled "I built a tiny IP KVM for $31 with an ESP32-P4 — no soldering"; going by the reddit ID it was around 11-16/17, which fits the +62 stars over two days; who posted it and its vote count are unverified
  • Verified The README and website ask for stars: the README says 'The easiest way to help is to star it on GitHub', and the homepage has a Star button
  • Verified HN: 07-31 someone posted the website, 3 points; the author's own 3 posts got 2 points each, and none took off

ESP-KVM (espkvm/espkvm): open-source firmware that turns a few-dollar ESP32-P4 dev board into an IP-KVM

Channel: GitHub | Research date: 2026-11-18/19 | Data card: 695 stars / 52 forks (2026-11-19), +7 in the last 101 days, +7 in the first 16 days

Bottom line

This project comes from a Lithuanian front-end engineer (GitHub account dexif, Evgenij Spitsyn), who took jrowny's IP-KVM prototype on the ESP32-P4 (p4kvm) and turned it into complete, usable firmware. In the four months since, it has shipped 88 releases and gained a full product-style website. Three things made it take off:

  1. Timing: the ESP32-P4 had just come out, and "a KVM with no Linux, just a microcontroller" was doable for the first time;
  2. The author promoted it well: in late July, it hit Hackaday, CNX and Hackster within a week, and his own post in r/esp32 got 204 votes;
  3. Rode JetKVM Mini's coattails: in September JetKVM launched the Mini on the same chip, and the author seized the moment to build "open-source firmware for the JetKVM Mini." Stars sped up in November, mainly from that firmware release, plus an r/homelab "build one for $31" post.

Star count isn't huge (695), and the audience is concentrated among hardware and homelab enthusiasts.

1. What it is

  • One ESP32-P4 dev board, plus a TC358743 HDMI-to-CSI capture board, joined by a ribbon cable, no soldering. Plug it into the target machine's HDMI and USB, and you can see that machine's screen in a browser and emulate its keyboard and mouse. It works even with the BIOS and machines with no OS installed (website espkvm.io).
  • The selling point is "No Linux inside": most rival IP-KVMs are basically a small Linux computer, whereas this is microcontroller firmware of about 1MB. Power loss won't corrupt the filesystem, it boots in about 15 seconds, OTA uses dual partitions with automatic rollback, and there's no shell and no SSH (homepage).
  • Lots of features: H.264/MJPEG hardware encoding; a virtual CD-ROM (SD card, on-chip flash, URL, local files, one-click netboot.xyz); ATX power button; copying text from the BIOS screen (via a glyph table, not OCR); screen-keyword alerts (Telegram/ntfy/webhook); dashcam-style recording; macro scripts; built-in Tailscale and WireGuard; integration with Home Assistant (MQTT) and VNC; plus an MCP server and skills so AI agents can operate machines (the mcp and skills repos under the github.com/espkvm org).
  • Supports 17 different makers' P4 boards, each rated on a 5-point scale; one-click flashing in the browser (WebSerial); a live demo (demo.espkvm.io); and it can even be flashed onto the JetKVM Mini as third-party firmware.
  • Acknowledged weak spot: frame rate of about 20–27fps, well behind the 1080p60 of Linux-based options (website FAQ).

2. Competitors

CompetitorsFormLaunchedScaleHow ESP-KVM differs
PiKVMOpen source + finished hardware (Raspberry Pi)2019pikvm/pikvm 10,478 stars (our GitHub library 11-19)Category benchmark, Linux, 1080p60, finished hardware is pricey (V4 runs several hundred dollars, not verified one by one); ESP-KVM is cheap and has no OS
Sipeed NanoKVMOpen source + finished hardware (RISC-V Linux)2024-076,621 starCheap Linux option with past security controversy; ESP-KVM goes the microcontroller route
JetKVMOpen source + finished hardware2024-10jetkvm/kvm 5,449 stars, +30 in the last ~179 daysThe most popular finished option in the category (Rockchip + Linux); ESP-KVM is DIY firmware
JetKVM MiniFinished hardware; firmware open-sourced in NovemberLaunched 2026-09-13, shipping from late OctoberHN 573 points, r/homelab shipping post 336 votes; jetkvm/mini 27 starsSame ESP32-P4X chip, priced at $33–39 (jetkvm.com). The most direct rival, but ESP-KVM turns it into hardware you can flash yourself
TinyPilotOpen source + commercial hardware (Raspberry Pi)20203,491 starAimed at enterprise users, with paid support
One-KVM(mofeng-git)Open source (Rust)2023-112,629 starSoftware-only option running on various cheap Linux boards, mainly used in Chinese communities
GL.iNet Comet / Luckfox PicoKVM / Radxa LinkrCommercial hardware2025–2026Not verifiedLow-cost finished Linux KVMs, with new models constantly appearing and fierce price competition
jrowny/p4kvmOpen-source PoC2026-06-22161 starThe predecessor of ESP-KVM; the author admits it had many bugs and no security measures, and encouraged others to fork it (CNX)
Motherboards with built-in IPMI/BMC, Intel vPro/AMTBig-company featuresVery early—Found only on servers and commercial machines; ESP-KVM adds this for "machines without a BMC"

Conclusion: the category is crowded (PiKVM, NanoKVM, JetKVM, Comet, PicoKVM, Linkr…), but the "ESP32-P4 microcontroller + no OS" slot had only the p4kvm prototype as of July. JetKVM's entry in September actually validated that path.

3. How the stars came in (timeline)

TimelineEventEvidence
2026-06-22jrowny posted the p4kvm prototype and a YouTube video; 7-03 Hackaday covered it as "This KVM Runs A P4 Instead Of A Pi"hackaday.com/2026/07/03
07-22The espkvm org and repo were createdGitHub API
07-29The author posted a project page on Hackster himself (no-solder tutorial)hackster.io/dexif/...
07-30Hackaday "A Capable KVM Built With The ESP32" and CNX Software covered it the same day; 07-31 Hackster News, the RISC-V International weekly, and Tux Machines reprinted it; 08-01 Italy's 1612.it; 08-02 Circuit Rocks "$45 IP KVM"The website's "In the press" section and the original articles on each site
07-31Someone on HN posted the website (Jimmc414), getting only 3 points, and it didn't take offHN Algolia 49126587
08-07The author u/spitsynnet posted in r/esp32 "I built an open-source IP-KVM out of a cheap ESP32-P4...", getting 204 votes and 36 comments; the Hackaday.io project page went up the same dayThe Brave summary read "Posted by u/spitsynnet - 204 votes and 36 comments"
08-25The author posted in the Home Assistant community (HA auto-discovers it via MQTT)community.home-assistant.io/t/.../1022535
09-13JetKVM Mini launch (same ESP32-P4X chip): 573 points and 235 comments on HN; someone mentioned espkvm in the thread, and the author replied as "Maintainer (espkvm) here"; in the r/homelab launch thread someone recommended github.com/espkvm/espkvm; it was also reshared on XHN 49681152;reddit r/homelab 1weujyv;x.com/markfenner
09-22The author posted in the M5Stack community (Unit PoE-P4 edition)community.m5stack.com/topic/8355
As of 10-09Already 503 stars, meaning over 70% of the stars came from 7–September's launch waveOur github repo_day (deeply source)
10-09 to 11-12Slow, steady growth of 1–6 a day (503→594); 10-20 Tab5 terminal, 10-21 board ratings and other blog posts sent to HN each got 2 pointsGitHub repo; HN Algolia
11-04JetKVM open-source Mini firmware (jetkvm/mini)GitHub
11-10 / 11-12ESP-KVM 0.80 / 0.83 "Custom firmware for the JetKVM Mini is ready", the author posted to r/jetkvm and HNespkvm.io/blog;reddit r/jetkvm 1xukvhx
About 11-16r/homelab "I built a tiny IP KVM for $31 with an ESP32-P4 — no soldering"; the poster said "I recently came across ESPKVM" (going by the reddit ID, around 11-16/17; the original post was blocked by 403, vote count unverified)Jina/Brave search snippets
11-16 → 11-18+62 stars in two days (617→679), then 11-19 added +16, reaching 695Data card daily

Verdict: the first big push came from the author personally working hardware media and communities in one concentrated burst, which got it to about 500 stars; the November surge came from the JetKVM Mini firmware plus an r/homelab post. It never hit trending (the repo was only 120 days old, and trending doesn't favor very new repos), and it never had a real Hacker News moment.

4. Growth tactics broken down

  1. Hardware media in one concentrated week (confirmed). Hackaday and CNX covered it the same day, Hackster, the RISC-V weekly and Circuit Rocks followed, and it was then reposted in French, Greek, Spanish, Russian, Chinese, Japanese, Thai and German (per the official site). The author posted his own Hackster project page (07-29), timed to land one day before the media coverage.
  2. A press page written for journalists (confirmed). espkvm.io/press says "If you are writing about this project, take whatever is useful from this page". It ships 4 randomized versions of each blurb "so that two people writing in the same week do not end up publishing the same sentence", plus ready-to-use numbers, limitations and images. That's a rare, proactive PR approach. The official site lists 17+ independent write-ups, including two Chinese ones (SMZDM and jinbel.cn).
  3. The author posted and replied in communities himself (confirmed). His first r/esp32 post got 204 upvotes; he also posted in the HA community, the M5Stack community and a Facebook ESP group. In an older r/homelab thread, "State of IP KVM solutions 2026", spitsynnet replied "You can check also ESP-KVM". On the HN thread for JetKVM Mini he replied as the maintainer.
  4. Riding a big vendor's product on the same chip (confirmed). After JetKVM Mini launched, ESP-KVM positioned itself as "the same chip, no OS, we did this route first". Once JetKVM open-sourced the Mini firmware, the author shipped a third-party Mini firmware within 6 days (11-04 → 11-10) and pulled existing JetKVM users into r/jetkvm. This is the play of making an open-source replacement firmware for popular hardware.
  5. Treating the website as a product (confirmed). It has an online demo, one-click browser flashing, grades for 17 boards, comparison pages, a "read your board" detection tool, and an engineering blog post for each release (the 0.75 post describes fixing a bug remotely while on holiday in Malta). The author is a frontend engineer by trade (GitHub bio "Frontend developer", @flespi-software), so the 44KB console and the site are high quality.
  6. Directly asking for stars (confirmed). The README says "The easiest way to help is to star it on GitHub - it costs nothing and helps others find the project", and the homepage has a "Star us on GitHub" button.
  7. Riding the AI agent hype (confirmed, effect unknown). It shipped an MCP server, Claude plugin skills and an agent program. A third-party article, "Give Your AI a Spare Keyboard", is also listed in the site's press coverage.
  8. Long-tail traffic from ecosystem integrations: Home Assistant, Tailscale and M5Stack communities all have people sharing it.
  9. No paid promotion or TikTok found, and no X big account pushed it proactively (the x-radar corpus has no hits; it was only sporadically reposted on X).

5. Why users would use it and star it

  • Real pain point: in a homelab, a machine stored in a cabinet that won't boot can't be reached without a BMC, so you have to drag a monitor over. Off-the-shelf IP-KVMs cost tens to hundreds of dollars, and PiKVM was also hit by Raspberry Pi shortages (the author says this in the original Hackster post).
  • Cheap, no soldering, browser flashing, lowering the bar to "buy two boards + click once" (CNX estimates a BoM of about $45, and the r/homelab poster paid $31).
  • "No Linux" is an opinionated pitch: fewer failure points, a smaller attack surface, nothing to maintain. That gets HN and homelab people talking, and JetKVM itself later moved to the same approach on the Mini.
  • Frequent, public updates: of 288 commits, about 286 are the author's own; there are 88 releases, averaging a release every 1–2 days from 9 through November; each one has a blog post, which makes the project feel alive.

6. Differentiation, and whether it's really why it grew

  • Differentiation: the only fully working, feature-complete open-source ESP32-P4 microcontroller IP-KVM firmware, running on 17 off-the-shelf dev boards and the JetKVM Mini. Compared with Linux-based KVMs, it gives up picture quality and gains stability, security, low cost and zero maintenance.
  • That's why it took off, but timing and the author's promotion were also needed. The technology alone wasn't enough: the predecessor p4kvm built the hardest part first and got only 161 stars; the author's own unprompted HN posts also scored only 2 points each. Reaching 695 stars came from three things stacked together: a finished, usable product, dense media and community exposure, and the momentum from JetKVM Mini.

7. Visibility and copycats

  • Visibility: circulating in small circles. Hardware media (Hackaday, CNX, Hackster) and r/esp32 and r/homelab covered it, but it didn't catch fire on HN, never made trending, and no big X account wrote about it. It's pure open-source firmware, so there is no revenue to disclose.
  • Copycats and derivatives: netube99/sskvm (09-10, ESP32-P4 + MS2109 USB capture, Chinese-language, supports agent control, 5 stars), NguyenTri1455/ESP32-P4-Low-Cost-KVM (11-09,5 stars), chnzzh/espcua-driver (11-17, an AI agent CLI/SDK for ESP32-P4 + C790 KVMs), and ClariSortAi/ai-kvm (an AI KVM for the ESP32-S3). The biggest commercial "follower" is actually JetKVM Mini itself: same chip, launched in September.

8. What others can learn

  • When a big vendor ships a product on the same chip, build an open-source replacement firmware for it: go straight into their user community (r/jetkvm), and ride their marketing.
  • The press page: write the blurb in several versions, lay out the numbers and limitations, and cut the cost for journalists to write about it. This infrastructure is what got it a dozen-plus write-ups.
  • Concentrated launch window: a self-posted Hackster project page, media coverage, its own Reddit posts and vertical communities (HA, M5Stack) were all packed into one to two weeks.
  • Treating the website as a product: online demo, browser flashing, hardware grades and comparison pages, which also pick up SEO (one page per board).
  • Publicly crediting whose shoulders it stands on: the README, website and Reddit posts all credit jrowny first, and the original author publicly supported it in r/esp32, which earned strong community goodwill.

9. Still unclear

  • Exact date and upvote count of the r/homelab "$31" post, and whether the poster is the author's alt account (the original post 403 can't be read; the post is written in the third person, "I recently came across").
  • The day-by-day star curve for 7–September can't be obtained: the stargazers endpoint returns 404 or requires authentication, and our data only starts at 10-09. So we can only infer that the launch wave contributed about 500 stars.
  • Actual install base: no download or flash statistics. 52 forks, an external PR (a VNC server written by Jan Heil), someone who printed their own enclosure, and a blog post where the author describes building one after his $800 data-center KVM broke all show people are really building these, but the scale is unknown.
  • Whether the author's very fast update pace comes from heavy use of AI-assisted coding: unverified, only guessed at in HN comments.

Sources

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.