🛠️ All DevTools

[Other] A Safer Container Ecosystem with Docker: Free Docker Hardened Images

[Other] A terminal emulator that runs in your terminal. Powered by Turbo Vision

[Other] Log level 'error' should mean that something needs to be fixed

[Other] Backup automation for self-hosters. Built on top of restic

[API/SDK] Web3 wallet tools NexaPay provides client-side Web3 wallet tools. Generate and manage wallets locally with 100% non-custodial control.

[Testing] Open source testing and reporting platform QA Studio: Open-source test management platform with automated test reporting, test case management, and Playwright integration. Zero code changes - automatically discovers your tests. Built by QA engineers for modern CI/CD pipelines.

[Other] The open-source, local-first alternative to Kombai. OpenKombai is a free, open‑source, privacy‑first “design to code” tool that converts UI screenshots and designs into production‑ready React + Tailwind CSS using local LLMs via Ollama. It runs fully on your machine (no API keys, cloud, or token costs), ships with a drag‑and‑drop Studio UI, and is built with a FastAPI backend plus a modern React/Vite/Shadcn frontend for easy hacking, extension, and self‑hosting.

[Other] FastAPI Endpoints: Efortless routing, simplified fastapi-endpoints is a lightweight and simple file-based router for FastAPI framework. The key features are: - Simple: Organize and define routes directly through a clear and simple file structure. - Auto Discovery: Automatically detects and registers all defined routers. - Effortless Integration: Seamlessly integrates with existing FastAPI projects. - Selective Routing: Include or exclude specific routers by specifying Python modules.

[Other] Monitor and manage Github Copilot usage With one simple view, you can see requests, costs, model breakdowns and usage trends over time – so you can decide if Copilot is paying off. I built this after asking myself “Am I actually using GitHub Copilot enough to justify the cost?” The existing GitHub dashboards weren’t enough, so I created Copilot Tracker to give a clear, focused view on usage and value. Check out the landing page to try a quick dashboard interactive demo

[Other] Shared and synchronized AI memory + reasoning across teams Most AI coding tools are single-player. Your AI forgets everything when the session ends, forcing every dev to waste time on redundant exploration. Grov turns your AI coding agent into a collective team brain. It captures the reasoning behind every solution and syncs it to your entire team. If one dev’s AI figures out your auth system, everyone’s AI knows it instantly. Currently works with claude code, expansion: codex, gemini Later: cursor

[Other] Crypto, AI Tools, Web3, Trading, Smart Contracts ChainGPT AI Hub is a crypto-native AI workspace built for traders, researchers, and builders who need clarity in fast-moving markets. It combines crypto alerts, market analysis, smart contract tools, legal intelligence, and AI-powered trading for Web3 workflows. AI Hub V2 boosts performance and accuracy, enabling faster market tracking, on-chain insight, and risk assessment. Purpose-built for crypto. No generic AI. Just tools that understand the market.

[CLI Tool] Show HN: Skouriasmeno Papaki – S3 transfer tool, up to 12x faster than AWS-CLI

[Other] I ported JustHTML from Python to JavaScript with Codex CLI and GPT-5.2 in hours

[Other] Show HN: A community-curated list of BYOC (Bring Your Own Cloud) vendors Hi HN,<p>I’m from the team at Nuon. While building in the Bring Your Own Cloud (BYOC) space, we realized there wasn&#x27;t a centralized, community-driven resource like awesome-selfhosted.net for managed software that lives in the customer&#x27;s VPC.<p>We hope software vendors will open a PR and add their BYOC offerings.

[Other] Chat-tails: Throwback terminal chat, built on Tailscale

[Other] Show HN: Deterministic PCIe Diagnostics for GPUs on Linux I built a small Linux tool to deterministically verify GPU PCIe link health and bandwidth.<p>It reports: - Negotiated PCIe generation and width - Peak Host→Device and Device→Host memcpy bandwidth - Sustained PCIe TX&#x2F;RX utilization via NVML - A rule-based verdict derived from observable hardware data only<p>This exists because PCIe issues (Gen downgrades, reduced lane width, risers, bifurcation) are often invisible at the application layer and can’t be fixed by kernel tuning or async overlap.<p>Linux-only: it relies on sysfs and PCIe AER exposure that Windows does not provide.

[Other] Show HN: I built the fastest RSS reader in Zig Well, I certainly tried. I had to, because it has a certain quirk inspired by &quot;digital minimalism.&quot;<p>The quirk is that it only allows you to fetch new articles once per day (or X days).<p>Why? Let me explain...<p>I want my internet content to be like a boring newspaper. You get it in the morning, and you read the whole thing while sipping your morning coffee, and then you&#x27;re done! No more new information for today. No pings, no alerts, peace, quiet, zen, etc.<p>But with that, I needed it to be able to fetch all articles from my hundreds of feeds in one sitting. This is where Zig and curl optimisations come in. I tried to do all the tricks in the book. If I missed something, let me know!<p>First off, I&#x27;m using curl multi for the network layer. The cool thing is it automatically does HTTP&#x2F;2 multiplexing, which means if your feeds are hosted on the same CDN it reuses the same connection. I&#x27;ve got it configured to handle 50 connections total with up to 6 per host, which seems to be the sweet spot before servers start getting suspicious. Also, conditional GETs. If a feed hasn&#x27;t changed since last time, the server just says &quot;Not Modified&quot; and we bail immediately.<p>While curl is downloading feeds, I wouldn&#x27;t want CPU just being idle so the moment curl finishes downloading a single feed, it fires a callback that immediately throws the XML into a worker thread pool for parsing. The main thread keeps managing all the network stuff while worker threads are chewing through XML in parallel. Zig&#x27;s memory model is perfect for this. Each feed gets its own ArenaAllocator, which is basically a playground where you can allocate strings during parsing, then when we&#x27;re done, we just nuke the entire arena in one go.<p>For parsing itself, I&#x27;m using libexpat because it doesn&#x27;t load the entire XML into memory like a DOM parser would. This matters because some podcast feeds especially are like 10MB+ of XML. So with smart truncation we download the first few X mb&#x27;s (configurable), scan backwards to find the last complete item tag, cut it there, and parse just that. Keeps memory usage sane even when feed sizes get massive.<p>And for the UI I just pipe everything to the system&#x27;s &quot;less&quot; command. You get vim navigation, searching, and paging for free. Plus I&#x27;m using OSC 8 hyperlinks, so you can actually click links to open them on your browser. Zero TUI framework needed. I&#x27;ve also included OPML import&#x2F;export and feed groups as additional features.<p>The result: content from hundreds of RSS feeds retrieved in matter of seconds, and peace of mind for the rest of the day.<p>The code is open source and MIT licensed. If you have ideas on how to make it even faster or better, comment below. Feature requests and other suggestions are also welcome, here or GitHub.

[Other] No Graphics API

[Other] The GitHub Actions control plane is no longer free

[Other] GitHub will begin charging for self-hosted action runners on March 2026