π οΈ All DevTools
Showing 1–20 of 3276 tools
Last Updated
February 07, 2026 at 08:00 PM
Developer Docs Audit
Product Hunt[Other] Increase LLM visibility, signups and activated users Get actionable insights to increase LLM visibility, free signups and activated users through your developer documentation. Based on 120+ top devtool docs.
PocketCmds
Product Hunt[Other] The cheat sheet every developer bookmarks on day one Stop Googling the same commands over and over. PocketCmds is a free, instant command reference for 83+ developer tools β from Git and Docker to Kubernetes, AWS, Terraform, and beyond. Every command is organized by stack, grouped into subcategories, and ready to copy with one click.
Introducing the Developer Knowledge API and MCP Server
Hacker News (score: 18)[Other] Introducing the Developer Knowledge API and MCP Server
Show HN: I spent 4 years building a UI design tool with only the features I use
Hacker News (score: 40)[IDE/Editor] Show HN: I spent 4 years building a UI design tool with only the features I use Hello everyone!<p>I'm a solo developer who's been doing UI/UX work since 2007. Over the years, I watched design tools evolve from lightweight products into bloated feature-heavy platforms. I kept finding myself using a small amount of the features while the rest just mostly got in the way.<p>So a few years ago I set out to build a design tool just like I wanted. So I built Vecti with what I actually need: pixel-perfect grid snapping, a performant canvas renderer, shared asset libraries, and export/presentation features. No collaborative whiteboarding. No plugin ecosystem. No enterprise features. Just the design loop.<p>Four years later, I can proudly show it off. Built and hosted in the EU with European privacy regulations. Free tier available (no credit card, one editor forever).<p>On privacy: I use some basic analytics (page views, referrers) but zero tracking inside the app itself. No session recordings, no behavior analytics, no third-party scripts beyond the essentials.<p>If you're a solo designer or small team who wants a tool that stays out of your way, I'd genuinely appreciate your feedback: <a href="https://vecti.com" rel="nofollow">https://vecti.com</a><p>Happy to answer questions about the tech stack, architecture decisions, why certain features didn't make the cut, or what's next.
I spent 5 years in DevOps β Solutions engineering gave me what I was missing
Hacker News (score: 74)[Other] I spent 5 years in DevOps β Solutions engineering gave me what I was missing
Show HN: Daily-updated database of malicious browser extensions
Hacker News (score: 10)[Other] Show HN: Daily-updated database of malicious browser extensions Hey HN, I built an automated system that tracks malicious Chrome/Edge extensions daily.<p>The database updates automatically by monitoring chrome-stats for removed extensions and scanning security blogs. Currently tracking 1000+ known malicious extensions with extension IDs, names, and dates.<p>I'm working on detection tools (GUI + CLI) to scan locally installed extensions against this database, but wanted to share the raw data first since maintained threat intelligence lists like this are hard to find.<p>The automation runs 24/7 and pushes updates to GitHub. Free to use for research, integration into security tools, or whatever you need.<p>Happy to answer questions about the scraping approach or data collection methods.
likec4/likec4
GitHub Trending[Other] Visualize, collaborate, and evolve the software architecture with always actual and live diagrams from your code
Show HN: GitClaw β An AI assistant that runs in GitHub Actions
Show HN (score: 5)[Other] Show HN: GitClaw β An AI assistant that runs in GitHub Actions
CyphrKey
Product Hunt[Other] WisprFlow for vibe coders w/ voice shortcuts Voice-to-code prompt engineering for developers. Talk naturally, ship production-ready code. CyphrKey transforms casual speech into optimized prompts for your AI coding tools. Three modes: Echo (clean transcription), Cyphr (debugging prompts), and Composer (production-ready instructions with error handling, types, and accessibility). It knows your codebase, references your actual files, and works with Claude Code, Cursor, and any AI tool. Free 5-day trial.
Forge CLI
Product Hunt[CLI Tool] Ship faster from your terminal β with any LLM you choose AI coding tools hallucinate. Forge doesn't. It fetches real docs for any library you're using. It sees your actual type errors via LSP. It understands your codebase semantically. β Works with any LLM (OpenAI, Claude, Gemini, Ollama) β Runs entirely in your terminal β Your code stays local One command: npm install -g codeforge-cli Then just type: forge No IDE. No subscription. Just code.
NGXSMK DatePicker
Product Hunt[Other] Signal-driven datepicker for modern Angular apps A high-performance, enterprise-ready datepicker built from the ground up with Angular Signals. Features native dark mode, mobile-first UX, 8-language i18n, zoneless support, and zero dependencies. Perfect for Angular 17+ applications.
Show HN: Artifact Keeper β Open-Source Artifactory/Nexus Alternative in Rust
Hacker News (score: 29)[Other] Show HN: Artifact Keeper β Open-Source Artifactory/Nexus Alternative in Rust I'm a software engineer who keeps getting pulled into DevOps no matter how hard I try to escape it. I recently moved into a Lead DevOps Engineer role writing tooling to automate a lot of the pain away. On my own time outside of work, I built Artifact Keeper β a self-hosted artifact registry that supports 45+ package formats. Security scanning, SSO, replication, WASM plugins β it's all in the MIT-licensed release. No enterprise tier. No feature gates. No surprise invoices.<p>Your package managers β pip, npm, docker, cargo, helm, go, all of them β talk directly to it using their native protocols. Security scanning with Trivy, Grype, and OpenSCAP is built in, with a policy engine that can quarantine bad artifacts before they hit your builds. And if you need a format it doesn't support yet, there's a WASM plugin system so you can add your own without forking the backend.<p>Why I built it:<p>Part of what pulled me into computers in the first place was open source. I grew up poor in New Orleans, and the only hardware I had access to in the early 2000s were some Compaq Pentium IIs my dad brought home after his work was tossing them out. I put Linux on them, and it ran circles around Windows 2000 and Millennium on that low-end hardware. That experience taught me that the best software is software that's open for everyone to see, use, and that actually runs well on whatever you've got.<p>Fast forward to today, and I see the same pattern everywhere: GitLab, JFrog, Harbor, and others ship a limited "community" edition and then hide the features teams actually need behind some paywall. I get it β paychecks have to come from somewhere. But I wanted to prove that a fully-featured artifact registry could exist as genuinely open-source software. Every feature. No exceptions.<p>The specific features came from real pain points. Artifactory's search is painfully slow β that's why I integrated Meilisearch. Security scanning that doesn't require a separate enterprise license was another big one. And I wanted replication that didn't need a central coordinator β so I built a peer mesh where any node can replicate to any other node. I haven't deployed this at work yet β right now I'm running it at home for my personal projects β but I'd love to see it tested at scale, and that's a big part of why I'm sharing it here.<p>The AI story (I'm going to be honest about this):<p>I built this in about three weeks using Claude Code. I know a lot of you will say this is probably vibe coding garbage β but if that's the case, it's an impressive pile of vibe coding garbage. Go look at the codebase. The backend is ~80% Rust with 429 unit tests, 33 PostgreSQL migrations, a layered architecture, and a full CI/CD pipeline with E2E tests, stress testing, and failure injection.<p>AI didn't make the design decisions for me. I still had to design the WASM plugin system, figure out how the scanning engines complement each other, and architect the mesh replication. Years of domain knowledge drove the design β AI just let me build it way faster. I'm floored at what these tools make possible for a tinkerer and security nerd like me.<p>Tech stack: Rust on Axum, PostgreSQL 16, Meilisearch, Trivy + Grype + OpenSCAP, Wasmtime WASM plugins (hot-reloadable), mesh replication with chunked transfers. Frontend is Next.js 15 plus native Swift (iOS/macOS) and Kotlin (Android) apps. OpenAPI 3.1 spec with auto-generated TypeScript and Rust SDKs.<p>Try it:<p><pre><code> git clone https://github.com/artifact-keeper/artifact-keeper.git cd artifact-keeper docker compose up -d </code></pre> Then visit http://localhost:30080<p>Live demo: <a href="https://demo.artifactkeeper.com" rel="nofollow">https://demo.artifactkeeper.com</a> Docs: <a href="https://artifactkeeper.com/docs/" rel="nofollow">https://artifactkeeper.com/docs/</a><p>I'd love any feedback β what you think of the approach, what you'd want to see, what you hate about Artifactory or Nexus that you wish someone would just fix. It doesn't have to be a PR. Open an issue, start a discussion, or just tell me here.<p><a href="https://github.com/artifact-keeper" rel="nofollow">https://github.com/artifact-keeper</a>
GitHub Actions is slowly killing engineering teams
Hacker News (score: 326)[Other] GitHub Actions is slowly killing engineering teams
Show HN: Horizons β OSS agent execution engine
Hacker News (score: 13)[DevOps] Show HN: Horizons β OSS agent execution engine I'm Josh, founder of Synth. We've been working on coding agent optimization with method like GEPA and MIPRO (the latter of which, I helped to originally develop), agent evaluation via methods like RLMs, and large scale deployment for training and inference. We've also worked on patterns for memory, processing live context, and managing agent actions, combining it all in a single stack called Horizons. With the release of OpenAI's Frontier and the consumer excitement around OpenClaw, we think the timing is right to release a v0.<p>It integrates with our sdk for evaluation and optimization but also comes batteries-included with self-hosted implementations. We think Horizons will make building agent-based products a lot easier and help builders focus on their proprietary data, context, and algorithms<p>Some notes:<p>- you can configure claude code, codex, opencode to run in the engine. on-demand or on a cron<p>- we're striving to make it simple to integrate with existing backends via a 2-way event driven interface, but I'm 99.9% sure it'll change as there are a ton of unknown unknowns<p>- support for mcp, and we are building with authentication (rbac) in mind, although it's a long-journey<p>- all self-host able via docker<p>A very simplistic way to think about it - an OSS take on Frontier, or maybe OpenClaw for prod
Show HN: Calfkit β an SDK to build distributed, event-driven AI agents on Kafka
Show HN (score: 6)[API/SDK] Show HN: Calfkit β an SDK to build distributed, event-driven AI agents on Kafka I think agents should work like real teams, with independent, distinct roles, async communication, and the ability to onboard new teammates or tools without restructuring the whole org. I built backend systems at Yahoo and TikTok so event-driven agents felt obvious. But no agent SDKs were using this pattern, so I made Calfkit.<p>Calfkit breaks down agents into independent services (LLM inference, tools, and routing) that communicate asynchronously through Kafka. Agents, tool services, and downstream consumers can be deployed, added-to, removed, and scaled independently.<p>Check it out if this interests you! Iβm curious to see what yβall think.
[Other] Show HN: Accept-md β One command to make Next.js sites LLM-scraping friendly I recently saw a post from the Vercel CEO pointing out that LLMs understand websites much better when they can request:<p>`Accept: text/markdown`<p>Most websites today are built for humans. When AI agents try to consume them, they get complex HTML instead of clean, structured content.<p>So I built *accept-md* β a simple open-source package for Next.js that helps solve this.<p>Getting started is intentionally minimal:<p>``` npx accept-md init ```<p>After that, your existing Next.js routes can automatically respond with Markdown whenever an AI agent (or any client) requests it. No redesigns, no CMS changes, and no duplicate pages to maintain.<p>Right now the project is:<p>* Focused only on Next.js * Middleware-based and lightweight * Designed to work with existing apps * A small step toward more AI-friendly websites<p>This is an early experiment, but I think the idea itself matters as AI agents become first-class consumers of the web.<p>Iβve open-sourced it and would love help with:<p>* Better markdown extraction * Edge cases across Next.js setups * Performance and caching * Tests and examples * Documentation * Eventually adapters for other frameworks<p>Would love feedback from the HN community on the approach β and whether `Accept: text/markdown` feels like a pattern worth standardizing for the AI-native web.
We tasked Opus 4.6 using agent teams to build a C Compiler
Hacker News (score: 88)[Other] We tasked Opus 4.6 using agent teams to build a C Compiler
A small, shared skill library by builders, for builders. (human and agent)
Hacker News (score: 15)[Other] A small, shared skill library by builders, for builders. (human and agent)
ZeroTworu/anet
GitHub Trending[Other] Simple Rust VPN Client / Server
OpenVideo
Product Hunt[Other] Open-source video editing & rendering SDK for the web High-performance browser-based video rendering engine powered by WebCodecs and PixiJS. Build professional video editors with ease.