<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: Aegis_Labs</title><link>https://news.ycombinator.com/user?id=Aegis_Labs</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 07 Jun 2026 20:39:41 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=Aegis_Labs" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by Aegis_Labs in "Show HN: Aegis – 85ns Sovereign Infrastructure Running on $100 Android Hardware"]]></title><description><![CDATA[
<p>Everyone is optimizing for H100s, but I’m hitting 85ns on a $100 Samsung A04e. I’m tired of 'bloated' infrastructure. Aegis is my proof that Rust-based sovereign nodes don't need a data center to scale.</p>
]]></description><pubDate>Wed, 15 Apr 2026 15:16:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=47780304</link><dc:creator>Aegis_Labs</dc:creator><comments>https://news.ycombinator.com/item?id=47780304</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47780304</guid></item><item><title><![CDATA[Show HN: Aegis – 85ns Sovereign Infrastructure Running on $100 Android Hardware]]></title><description><![CDATA[
<p>I built this using Rust to achieve 85ns latency benchmarks. Currently scaling to 824 active nodes directly from a Samsung A04e. While everyone is focused on high-end mobile AI, I'm focusing on sovereign, low-latency infrastructure that runs on anything. Feedback on the node scaling logic in my repo is appreciated</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47780284">https://news.ycombinator.com/item?id=47780284</a></p>
<p>Points: 1</p>
<p># Comments: 1</p>
]]></description><pubDate>Wed, 15 Apr 2026 15:14:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=47780284</link><dc:creator>Aegis_Labs</dc:creator><comments>https://news.ycombinator.com/item?id=47780284</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47780284</guid></item><item><title><![CDATA[Show HN: 85ns latency on a $100 Android device using Rust]]></title><description><![CDATA[
<p>"I built this because I'm tired of software bloat. I used Rust on a MediaTek Helio P35 (Samsung A04e) and achieved 85ns stable latency. Here is how I handled the memory management..."</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47675774">https://news.ycombinator.com/item?id=47675774</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 07 Apr 2026 14:16:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=47675774</link><dc:creator>Aegis_Labs</dc:creator><comments>https://news.ycombinator.com/item?id=47675774</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47675774</guid></item><item><title><![CDATA[New comment by Aegis_Labs in "Go hard on agents, not on your filesystem"]]></title><description><![CDATA[
<p>I know many 'Senior Engineers' will say 85ns is impossible on a $100 Cortex-A53 device. They'll say you need a $10k server. I've proven them wrong. Here is why your architecture is probably slower than my A04e..."</p>
]]></description><pubDate>Wed, 01 Apr 2026 14:21:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=47601332</link><dc:creator>Aegis_Labs</dc:creator><comments>https://news.ycombinator.com/item?id=47601332</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47601332</guid></item><item><title><![CDATA[New comment by Aegis_Labs in "A 1.8T Logic Layer for Ultra-Low-End ARM ($100 Devices"]]></title><description><![CDATA[
<p>500+ clones on a $100 device? That sounds like a lot of overhead for such weak hardware. Are you bypassing the standard Android stack entirely or using some custom instruction sets for the 1.8T logic? I'd love to see some latency benchmarks compared to a standard Go/Rust implementation</p>
]]></description><pubDate>Sun, 29 Mar 2026 07:50:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=47561179</link><dc:creator>Aegis_Labs</dc:creator><comments>https://news.ycombinator.com/item?id=47561179</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47561179</guid></item><item><title><![CDATA[New comment by Aegis_Labs in "CERN uses tiny AI models burned into silicon for real-time LHC data filtering"]]></title><description><![CDATA[
<p>This is the spirit. I'm doing something similar: scaling a 1.8T logic system using a budget mobile device as the primary node. Just hit 537 clones today. It's all about how you structure the logic, not the CPU power.</p>
]]></description><pubDate>Sat, 28 Mar 2026 14:47:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=47555076</link><dc:creator>Aegis_Labs</dc:creator><comments>https://news.ycombinator.com/item?id=47555076</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47555076</guid></item><item><title><![CDATA[New comment by Aegis_Labs in "Go hard on agents, not on your filesystem"]]></title><description><![CDATA[
<p>Interesting point. I've been running an autonomous multitalented AI agent (Aegis) on a $100 Samsung A04e. It manages 859 referring sites without touching the local filesystem much. Efficiency over hardware works."</p>
]]></description><pubDate>Sat, 28 Mar 2026 14:46:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=47555063</link><dc:creator>Aegis_Labs</dc:creator><comments>https://news.ycombinator.com/item?id=47555063</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47555063</guid></item></channel></rss>