We put a lot of work into abstracting BPF into a JavaScript framework to give builders, human or agentic, the ability to use complex kernel primitives with a familiar programming model to build production grade, scalable infrastructure tools.
Our hope is that everyone here will soon be able to build their own tools on-demand, versus buying them.
We separate a lot of the data layer code from the presentation-level code, to make them re-usable and keep the test surface on the actual data's accuracy manageable across all the random edge cases that arise across CPU architectures, kernel versions, and environments like AWS ECS network namespace voo-doo.
yeet | Chicago, IL / Remote | Full-Time
Building a dynamic runtime on top of the Linux BPF sub-system. Looking for extremely talented / passionate Rust developers / Backend Engineers with a deep interest in Linux internals, Distributed Systems, Dev Tools, Great Developer Experiences and Systems programming.
Experience working with distributed systems AND / OR writing highly-concurrent, performant multi-threaded Rust is a must.
Feel free to tell us all about your favorite GNU core utilities / Linux system calls / kernel sub-systems at: work [at] yeet.cx
after going through the docs this looks quite useful, but I'd prefer if the AI features were optional.
assuming it's your project here is some unsolicited feedback:
(1) imprint missing, no idea where the company is operating based on name or tld, cannot rule out it is in adversary country
(2) not a fan of curl | sh, looks way more professional if some prebuilt packages for common distros are also offered. maybe remove the yellow box and add some distro logos "available on your favorite distro"
(3) On landing page I think the last section with the cost comparison should actually be at the very top. No sysadmin wants to have AI chat on their machines. The cost comparison chart shows well-known tools that every sysadmin knows (splunk etc), and directly relates yeet to it - this is very good.
(4) the main landing page hero text is not really explanatory - linux ops is a big term, and there was not a lot of info I got out of it. Further down there is "yeet gives you kernel level visibility with featherweight overhead. Nothing gets dropped.", which I'd personally prefer. Maybe instead of "yeet is a JavaScript runtime for Linux Ops." use something like "yeet is a Javascript runtime for your linux kernel".
Generally the sysadmins I know are not looking for AI chats or agent toolkits, and right now these are "features" that might make people close the tab. But sysadmins want to easily get custom analytics and reduce SaaS costs, these features are looked for.
Maybe it makes sense to more clearly split up the "specialized Javascript for linux Kernel" thing from the AI features. No manager bats an eye if I install a new Javascript runtime that allows better LOCAL-FIRST (!) linux kernel analytics, but a lot of explanation needs to be done if there are "agents" or "AI chats" which can potentially exfiltrate data.
Building a dynamic runtime on top of the Linux BPF sub-system. Looking for extremely talented / passionate Rust developers / Backend Engineers with a deep interest in Linux internals, Distributed Systems, Dev Tools, Great Developer Experiences and Systems programming.
Experience working with distributed systems AND / OR writing highly-concurrent, performant multi-threaded Rust is a must.
Feel free to tell us all about your favorite GNU core utilities / Linux system calls / kernel sub-systems at: work [at] yeet.cx
Building a dynamic runtime on top of the Linux BPF sub-system. Looking for extremely talented / passionate Rust developers / Backend Engineers with a deep interest in Linux internals, Distributed Systems, Dev Tools, Great Developer Experiences and Systems programming.
Experience working with distributed systems AND / OR writing highly-concurrent, performant multi-threaded Rust is a must.
Feel free to tell us all about your favorite GNU core utilities / Linux system calls / kernel sub-systems at: work [at] yeet.cx
Building a dynamic runtime on top of the Linux BPF sub-system. Looking for extremely talented / passionate Rust developers / Backend Engineers with a deep interest in Linux internals, Distributed Systems, Dev Tools, Great Developer Experiences and Systems programming.
Experience working with distributed systems AND / OR writing highly-concurrent, performant multi-threaded Rust is a must.
Feel free to tell us all about your favorite GNU core utilities / Linux system calls / kernel sub-systems at: work [at] yeet.cx
Building a dynamic runtime on top of the Linux BPF sub-system. Looking for extremely talented / passionate Rust developers / Backend Engineers with a deep interest in Linux internals, Distributed Systems, Dev Tools, Great Developer Experiences and Systems programming.
Experience working with distributed systems AND / OR writing highly-concurrent, performant multi-threaded Rust is a must.
Feel free to tell us all about your favorite GNU core utilities / Linux system calls / kernel sub-systems at: work [at] yeet.cx
This tool was built on top of our engine: yeetd.
We put a lot of work into abstracting BPF into a JavaScript framework to give builders, human or agentic, the ability to use complex kernel primitives with a familiar programming model to build production grade, scalable infrastructure tools.
Our hope is that everyone here will soon be able to build their own tools on-demand, versus buying them.
We separate a lot of the data layer code from the presentation-level code, to make them re-usable and keep the test surface on the actual data's accuracy manageable across all the random edge cases that arise across CPU architectures, kernel versions, and environments like AWS ECS network namespace voo-doo.