🛠️ All DevTools

[API/SDK] Where developers can execute code quickly and easily Execute code safely with container-native isolation. Execly is a code execution API that runs snippets inside short-lived, language-specific containers.

[Other] Build & test production-safe prompts (GPT, Claude, Gemini) System for building, testing, and improving AI prompts - securely, scientifically, and at scale. Generate requirements, and implement specialized AI suggestions to enhance your prompt. Works with GPT-5, Gemini-2.5-pro, Claude-4.7-sonnet and many others.

[Database] One Engine. Many Database . Real-Time-Replication Helyx is a lightning-fast, cloud-agnostic database replication fabric supporting Oracle, PostgreSQL, MySQL & More. Real-time CDC, zero-downtime schema evolution, CLI simplicity, auto-recovery, and production-grade reliability—replication made effortless

[Other] Touch typing practice specially designed for coders Typir - Master touch typing with progressive alphabet training

[IDE/Editor] Code Python & R anywhere — no installs, no nonsense. bIDE is a free, browser IDE for Python & R that runs entirely in your browser — offline, private, and mobile-friendly. Built by a broke student using AI tools to make coding accessible anywhere.

[Monitoring/Observability] All-in-one uptime and performance monitoring platform PingView helps you monitor websites, APIs, and services with real-time alerts, performance audits, and security scans. Get uptime, SSL, and Lighthouse + Observatory insights

[Monitoring/Observability] Get instant alerts when your URLs or APIs go down. ✅ Monitor websites, APIs, and endpoints easily ⚡ Get instant email or webhook alerts on downtime or changes 📊 Track response times & uptime history 🤖 Self-host or use our cloud version Monitor your websites 24/7 real-time Free plan available.

[Other] Your accessibility copilot. Vertex A11y is a browser extension that scans websites for ADA/WCAG compliance in real time and highlights elements that are not compliant. It scores web pages based on the guidelines and suggests quick fixes.

[Other] Build anything with AI v0 by Vercel is your collaborative AI assistant to design, iterate, and scale full-stack applications for the web.

[Other] Your front-row seat to the world of AI, every day AI-Daily.news delivers sharp, curated AI news and insights every day. Stay ahead with the latest in artificial intelligence, machine learning and emerging tech—distilled for developers, startups and tech fans.

[Other] Show HN: Write Go code in JavaScript files I built a Vite plugin that lets you write Go code directly in .js files using a "use golang" directive. It compiles to WebAssembly automatically.

[Other] Show HN: Helium Browser for Android with extensions support, based on Vanadium Been working on an experimental Chromium-based browser that brings 2 major features to your phone&#x2F;tablet:<p>1. desktop-style extensions: natively install any extensions (like uBO) from the chrome web store, just toggle &quot;desktop site&quot; in the menu first.<p>2. privacy&#x2F;security hardening: applies the full patch sets from Vanadium (with Helium&#x27;s currently wip).<p>Means you get both browsers&#x27; excellent privacy features, like Vanadium&#x27;s webrtc IP policy option that protects your real IP by default, and security improvements such as JIT being disabled by default, all while being a reasonably efficient FOSS app that can be installed on any (modern) android.<p>It&#x27;s still in beta, and as I note in the README, it&#x27;s not a replacement for the full OS-level security model you&#x27;d get from running the GrapheneOS Vanadium combo. However, goal was to combine privacy of Vanadium with the power of desktop extensions and Helium features, and make it accessible to a wider audience. (Passkeys from Bitwarden Mobile should also work straight away once merged in the list of FIDO2 privileged browsers)<p>Build scripts are in the repo if you want to compile it yourself. You can find pre-built releases there too.<p>Would love any feedback&#x2F;support!

[API/SDK] Show HN: Hermes – Self-hosted video downloader I&#x27;ve been playing with my home server again, and I was looking for a video downloader. I found one that looked great, but was no longer functional. So, I vibe-coded my own.<p>Hermes is a REST API and web app built on top of yt-dlp. Why not just use yt-dlp? Additional features, phone support, and automations. Coming soon will be a very basic video editor so you can easily remux and trim your downloaded videos.

[Other] Show HN: MyraOS – My 32-bit operating system in C and ASM (Hack Club project) Hi HN, I’m Dvir, a young developer. Last year, I got rejected after a job interview because I lacked some CPU knowledge. After that, I decided to deepen my understanding in the low level world and learn how things work under the hood. I decided to try and create an OS in C and ASM as a way to broaden my knowledge in this area.<p>This took me on the most interesting ride, where I’ve learned about OS theory and low level programming on a whole new level. I’ve spent hours upon hours, blood and tears, reading different OS theory blogs, learning low level concepts, debugging, testing and working on this project.<p>I started by reading University books and online blogs, while also watching videos. Some sources that helped me out were OSDev Wiki (<a href="https:&#x2F;&#x2F;wiki.osdev.org&#x2F;Expanded_Main_Page" rel="nofollow">https:&#x2F;&#x2F;wiki.osdev.org&#x2F;Expanded_Main_Page</a>), OSTEP (<a href="https:&#x2F;&#x2F;pages.cs.wisc.edu&#x2F;~remzi&#x2F;OSTEP" rel="nofollow">https:&#x2F;&#x2F;pages.cs.wisc.edu&#x2F;~remzi&#x2F;OSTEP</a>), open-source repositories like MellOS and LemonOS (more advanced), DoomGeneric, and some friends that have built an OS before.<p>This part was the longest, but also the easiest. I felt like I understood the theory, but still could not connect it into actual code. Sitting down and starting to code was difficult, but I knew that was the next step I needed to take! I began by working on the bootloader, which is optional since you can use a pre-made one (I switched to GRUB later), but implementing it was mainly for learning purposes and to warm up on ASM. These were my steps after that:<p><pre><code> 1) I started implementing the VGA driver, which gave me the ability to display text. 2) Interrupts - IDT, ISR, IRQ, which signal to the CPU that a certain event occurred and needs handling (such as faults, hardware connected device actions, etc). 3) Keyboard driver, which enables me to display the same text I type on my keyboard. 4) PMM (Physical memory management) 5) Paging and virtual memory management 6) RTC driver - clock addition (which was, in my opinion, optional) 7) PIT driver - Ticks every certain amount of time, and also 8) FS (File System) and physical HDD drivers - for the HDD I chose PATA (HDD communication protocol) for simplicity (SATA is a newer but harder option as well). For the FS I chose EXT2 (The Second Extended FileSystem), which is a foundational linux FS structure introduced in 1993. This FS structure is not the simplest, but is very popular in hobby-OS, it is very supported, easy to set up and upgrade to newer EXT versions, it has a lot of materials online, compared to other options. This was probably the longest and largest feature I had worked on. 9) Syscall support. 10) Libc implementation. 11) Processing and scheduling for multiprocessing. 12) Here I also made a shell to test it all. </code></pre> At this point, I had a working shell, but later decided to go further and add a GUI! I was working on the FS (stage 8), when I heard about Hack Club’s Summer of Making (SoM). This was my first time practicing in HackClub, and I want to express my gratitude and share my enjoyment of participating in it.<p>At first I just wanted to declare the OS as finished after completing the FS, and a bit of other drivers, but because of SoM my perspective was changed completely. Because of the competition, I started to think that I needed to ship a complete OS, with processing, GUI and the bare minimum ability to run Doom. I wanted to show the community in SoM how everything works.<p>Then I worked on it for another 2 months, after finishing the shell, just because of SoM!, totalling my project to almost 7 months of work. At this time I added full GUI support, with dirty rectangles and double buffering, I made a GUI mouse driver, and even made a full Doom port! things I would&#x27;ve never even thought about without participating in SoM.<p>This is my SoM project: <a href="https:&#x2F;&#x2F;summer.hackclub.com&#x2F;projects&#x2F;5191" rel="nofollow">https:&#x2F;&#x2F;summer.hackclub.com&#x2F;projects&#x2F;5191</a>.<p>Every project has challenges, especially in such a low level project. I had to do a lot of debugging while working on this, and it is no easy task. I highly recommend using GDB which helped me debug so many of my problems, especially memory ones.<p>The first major challenge I encountered was during the coding of processes - I realized that a lot of my paging code was completely wrong, poorly tested, and had to be reworked. During this time I was already in the competition and it was difficult keeping up with devlogs and new features while fixing old problems in a code I wrote a few months ago.<p>Some more major problems occurred when trying to run Doom, and unlike the last problem, this was a disaster. I had random PFs and memory problems, one run could work while the next one wouldn’t, and the worst part is that it was only on the Doom, and not on processes I created myself. These issues took a lot of time to figure out. I began to question the Doom code itself, and even thought about giving up on the whole project.<p>After a lot of time spent debugging, I fixed the issues. It was a combination of scheduling issues, Libc issues and the Qemu not having enough (wrongfully assuming 128MB for the whole OS was enough).<p>Finally, I worked throughout all the difficulties, and shipped the project! In the end, the experience working on this project was amazing. I learned a lot, grew and improved as a developer, and I thank SoM for helping to increase my motivation and make the project memorable and unique like I never imagined it would be.<p>The repo is at <a href="https:&#x2F;&#x2F;github.com&#x2F;dvir-biton&#x2F;MyraOS" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;dvir-biton&#x2F;MyraOS</a>. I’d love to discuss any aspect of this with you all in the comments!

[Other] Show HN: I Built DevTools for Blazor (Like React DevTools but for .NET) Hi HN! I&#x27;ve been working on developer tools for Blazor that let you inspect Razor components in the browser, similar to React DevTools or Vue DevTools.<p>The problem: Blazor is Microsoft&#x27;s frontend framework that lets you write web UIs in C#. It&#x27;s growing fast but lacks the debugging tools other frameworks have. When your component tree gets complex, you&#x27;re stuck with Console.WriteLine debugging.<p>What I built: A browser extension + NuGet package that:<p>Shows the Razor component tree in your browser Maps DOM elements back to their source components Highlights components on hover Works with both Blazor Server and WASM<p>How it works: The NuGet package creates shadow copies of your .razor files and injects invisible markers during compilation. These markers survive the Razor→HTML pipeline. The browser extension reads these markers to reconstruct the component tree.<p>Current status: Beta - it works but has rough edges. Found some bugs when testing on larger production apps that I&#x27;m working through. All documented on GitHub.<p>Technical challenges solved:<p>Getting markers through the Razor compiler without breaking anything Working around CSS isolation that strips unknown attributes Making it work with both hosting models<p>It&#x27;s completely open source:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;joe-gregory&#x2F;blazor-devtools" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;joe-gregory&#x2F;blazor-devtools</a><p>Demo site where you can try it:<p><a href="https:&#x2F;&#x2F;blazordevelopertools.com" rel="nofollow">https:&#x2F;&#x2F;blazordevelopertools.com</a><p>Would love feedback, especially from anyone building production Blazor apps. What debugging pain points do you have that developer tools could solve?

[DevOps] Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD

[Other] A GUI client for Windows, Linux and macOS, support Xray and sing-box and others

[Other] Clojure Land – Discover open-source Clojure libraries and frameworks

[Other] Developer tools Explore our comprehensive collection of developer tools including JSON formatters, text processors, validators, and utilities. All tools are free to use and work directly in your browser.

[API/SDK] MCP server for GraphQL/OpenAPI docs: local files/remote URLs MCP server that provides tools for interacting with API documentation. Supports both GraphQL and OpenAPI specifications, fetching schema definitions from various sources (local files or remote URLs), caching them, and exposing them through a set of tools.