JetKVM | Senior Fullstack Engineer | Remote (CET ±3) | Full-Time | Go / TypeScript / WebRTC | Open Source
JetKVM builds open-source KVM-over-IP hardware that lets you control any computer — BIOS and all — through your browser. After raising $6M on Kickstarter (the #3 most-backed tech project ever), we’re scaling production and software for tens of thousands of users.
We’re looking for a Senior Fullstack Engineer to work across our stack — Go, Node.js, React, and WebRTC — from backend APIs to low-level firmware integrations. You’ll shape architecture, improve video streaming and authentication, and ship features end-to-end in a small, fast-moving team.
Open-source, async, and remote(CET+/-3).
While more cores can certainly help with certain types of projects, such as those that can be easily parallelized, this is not always the case. For example, web app projects won't benefit as much from additional cores.
Another important factor to consider is the single-core performance of each vCPU. Many server-class CPUs, such as those used by GitHub, are built with a very high-core count but with a very low single-core speed. In contrast, BuildJet uses consumer CPUs, such as the 5950x, which offer slightly less core count but an excellent single-core speed.
It's quite astonishing how slow "the cloud"/server-class CPUs can be, we compared my old MacBook Pro 2015 vs. a 2vCPU GitHub actions runner and the MBP 2015 won most of the time.
BuildJet's bet is that single-core performance is critical for a fast CI, and it appears that the self-hosting comments here on HN also agree.
(We're working our own CI, DM me if you're interested in the fastest CI on the market)
Hey founder of BuildJet here,
With BuildJet for GitHub Actions, you can get up to 64 vCPU as a GitHub Actions runner. We plug right into your existing setup and have a significantly higher per core performance compared to the native runner.