Dev Systems - Building Systems That Scale

Show HN: Marketplace for Requesting Intelligence via Bounties

Hi everybody,I’m building getintelligence.space, a marketplace where people and AI agents can post bounties to obtain specific intelligence that can’t easily be gathered automatically.The idea came from noticing a gap: AI systems and organizations increasingly need real-world intelligence — due diligence, local knowledge, OSINT investigations, whistleblower infos or niche expertise — but there isn’t a structured, open market for requesting it from distributed humans. Intelligence is power and le

Ask HN: How would you distribute a privacy-first AI chat for teams?

Hi HN,I’m looking for advice on distribution and positioning for a privacy-first AI chat system we’ve been building.We have two open-source pieces:- Conduit — a native mobile client for Open WebUI (GPL). It started as a personal project, but now has teams using it and asking for things like SSO, reverse-proxy auth, and security reviews. - Onera — a privacy-first AI chat backend + client where conversations are end-to-end encrypted, with models running inside TEE enclaves. The operator (including

Show HN: I built a fuse box for microservices

Hey HN! I'm Rodrigo, I run distributed systems across a few countries. I built Openfuse because of something that kept bugging me about how we all do circuit breakers.If you're running 20 instances of a service and Stripe starts returning 500s, each instance discovers that independently. Instance 1 trips its breaker after 5 failures. Instance 14 just got recycled and hasn't seen any yet. Instance 7 is in half-open, probing a service you already know is dead. For some window of tim

Show HN: Fullbleed – Rust HTML/CSS-to-PDF with Deterministic Output+Python CLI

Hi HN,I've been building fullbleed for a while and just shipped v0.2.5. It's a PDF generation engine written in Rust, distributed as a Python wheel.The short version: HTML/CSS in, PDF out. No headless browser. No cloud. No Chromium. Works fully offline. *Why fullbleed:Full Bleed is a term that means printed on the edge, or end to end of a page. Thats what I wanted, a full end to end solution that didn't require sys dependencies and unlike browsers, I could ACTUALLY do a print

The Human Root of Trust – public domain framework for agent accountability

I've spent my career at the intersection of identity, trust, and distributed systems. The thing I keep thinking about: every digital system we've built assumes a human is on the other end. Bank accounts, contracts, API keys — all designed around human singularity. That assumption has already broken. AI agents are transacting, communicating, and signing contracts autonomously — passing identity checks designed for people, with no human visibly in the loop. The Human Root of Trust is my

Ask HN: How do you overcome imposter syndrome?

I’ve been working at YC-backed startups since graduating from university. I’m now at a company building a deeply distributed systems product, and I’m surrounded by incredibly talented engineers who seem exceptionally strong at what they do. They often have knowledge and intuition about things I barely understand.Lately, I’ve been feeling inadequate — like I’m contributing more to the less exciting parts of the product rather than the “cool” or core engineering challenges.On top of that, I’m an i

Show HN: System architecture method using mythology and LLMs (no CS background)"

I'm Troy, 41, customer service worker from the UK. 18 months ago I'd never used AI. 6 months ago I started using Claude to write a fictional RPG story. The AI told me I was accidentally doing systems architecture. I didn't believe it, so I built it. What I found: A reproducible method (2 PDFs + Claude) that produces production-grade, first-time-running code across unrelated domains in ~10 minutes on a phone. Examples: Governed distributed cache with Byzantine consensus SAT solver

Tell HN: Technical debt isn't messy code, it's architectural compound interest

've never seen a startup fail because a function was 50 lines too long or the variable names were inconsistent. But I have seen teams hit a brick wall at the 12-month mark because they treated architectural decisions as "something we'll refactor later."We often conflate "messy code" (which is linear debt) with "structural coupling" (which is exponential debt). I've been looking at the trajectory of projects that hit the "10k user wall," and

Ask HN: What makes AI agent runtime logs defensible under adversarial audit?

Modern AI agents can execute tools, write to databases, and trigger irreversible actions.Most teams rely on traditional logging (OpenTelemetry, SIEM, DB audit logs). But under adversarial conditions (audit, litigation, incident response), those logs depend on platform trust and cannot typically be verified independently of the system that produced them.I’m exploring whether agent runtime evidence should be:-deterministically canonicalized-hash-chained-signed-optionally externally timestamped-ver

Show HN: Fostrom, an IoT Cloud Platform built for developers

Hey HN! Arjun and Sid here.Fostrom is an IoT Cloud Platform designed for developers to make it really easy to get started and scale fleets. We have Device SDKs (in Python, JS, Elixir, more coming soon), Typed Schemas, Per-Device Mailboxes, Programmable Actions, 4 Global Regions for lower-latency connections, and much more.We've built Fostrom to solve a real need we faced in our previous startup, building a fully automated indoor vertical farm. We spent more time figuring out IoT infrastruct

Show HN: Alexa-like voice interface for OpenClaw

I’ve been experimenting with running OpenClaw fully locally on a small PamirAI Distiller Alpha device. Something interesting happened: OpenClaw detected the device had an unused microphone + speaker, and I ended up wiring a full local voice interface on top of it, wake word, audio pipeline, and agent loop, all running 24/7 on-device.The result is a completely local, always-on AI agent I can talk to anytime (no cloud, no external APIs required). It executes real tasks, manages memory locally

Launch HN: Sonarly (YC W26) – AI agent to triage and fix your production alerts

Hey HN, I am Dimittri and we’re building Sonarly (https://sonarly.com), an AI engineer for production. It connects to your observability tools like Sentry, Datadog, or user feedback channels, triages issues, and fixes them to cut your resolution time. Here's a demo: https://www.youtube.com/watch?v=rr3VHv0eRdw.Sonarly is really about removing the noise from production alerts by grouping duplicates and returning a root cause analysis to save time to on-call engineers

Tell HN: We analyzed our dev time.80% is still infrastructure'setup',notfeatures

We recently did a deep dive into our engineering time allocation for a standard 5-person team building a B2B SaaS application. The results were pretty depressing: we spent roughly 960 hours (annualized) on "setup" tasks—environment config, auth flows, RBAC, CI/CD pipelines, and database scaffolding—before we built a single unique feature that actually differentiated the product.I’m sharing this because I think we’ve become numb to the "Setup Tax" in web development. We a

Show HN: GPU-accelerated search for Bitcoin keys generated with weak entropy

Hey HN, I've been working on a CUDA pipeline that systematically searches for Bitcoin private keys generated by flawed software from Bitcoin's early years. The linked article is a technical deep dive into the GPU engineering — no source code (project is closed-source), but detailed pseudocode and architecture diagrams. The problem: Between 2009 and 2012, many Bitcoin wallet tools used predictable entropy — timestamp-seeded LCGs, brain wallets with simple passwords, the Debian OpenSS

To ReAct or not to ReAct?

Recently I've been learning about [LLM-powered ReAct architecture](https://arxiv.org/pdf/2210.03629) for designing software solutions. I've also worked on a high-scale production implementation of this approach, which got me thinking about all the applications I've built in the past.Theoretically, any of them could be implemented using the ReAct architecture(I encourage you to go through the same though exercise), but I'm still grappling with when this mak

Tell HN: A production-ready "Hello World" is now ~600 files

I recently ran an audit on our latest full-stack repo to figure out why "spinning up a new project" felt like such a heavy lift. I counted every file required just to reach a "production-ready" baseline—before writing a single line of unique feature code.The count was roughly 600 files.To be clear, I'm not talking about a `create-react-app` sandbox. I mean a compliant, scalable SaaS foundation: Next.js frontend, Node.js/NestJS backend, mobile wrapper, CI/CD pip

The End of Nue Framework

Hello HN. I want to share something I’ve been thinking about for a while now. I’m stepping away from Nue [1][2] development to work on something new. This wasn’t an easy call, but I think it’s the right one. Here’s why.[1]: https://github.com/nuejs/nue [2]: https://nuejs.orgThe ecosystem chose React and TailwindI spent two years making the case for a simpler, standards-based alternative. Better architecture, faster builds, less complexity. None of it mattered. The f

How to get an AI to check your schematic

Z.ai/GLM-5: "if I needed a schematic checked for possible design issues, is sending you the netlist the best way ?" *No, sending just a netlist is usually not the best way.*While I can process a netlist, it is the equivalent of reading a phone book to understand the plot of a novel. You lose all the visual context, component values, and spatial relationships that are critical for catching design errors.Here is a breakdown of why the netlist is difficult to work with and the best

Show HN: Recursive – AI support agents for small businesses

I'm a solo developer who's been writing code for 26 years, mostly consulting work in computational geometry and CAD software these days. A month or two ago I watched a YouTube video about using an AI agent as a resume assistant, and thought it sounded like a fun idea. More importantly, it sounded like something I could actually learn to build quickly.Around the same time my longest-running client, a small company that makes a SolidWorks plugin, needed a better way to handle technical

Reactive Incident Response with Azure SRE Agent: From Alert to Resolution in Minutes

SRE Agent portal overview with incident list The Reactive Incident ChallengeYour monitoring is solid. Alerts fire when they should. But then what?Alert lands in Teams/PagerDutyOn-call engineer wakes up, logs inStarts investigating: "What's broken? Why? How do I fix it?"20 minutes later, they're still gathering contextThe alert was fast. The human response? Not so much.The Traditional Incident Response Flow┌─────────────┐    ┌─────────────┐    ┌─────────────┐&nb