Show HN: Druids – Build your own software factory
Making 'software factory' infrastructure, specifically multi-agent coordination, more accessible by abstracting VM infrastructure, agent provisioning, and communication.
View Origin LinkProduct Positioning & Context
AI Executive Synthesis
Making 'software factory' infrastructure, specifically multi-agent coordination, more accessible by abstracting VM infrastructure, agent provisioning, and communication.
Druids addresses the complexity of orchestrating multi-agent coding workflows, a critical bottleneck for organizations adopting agent-based development. By abstracting VM infrastructure, provisioning, and communication, it democratizes access to 'software factory' capabilities previously limited to 'frontier labs.' The event-driven architecture and isolated sandbox runtimes are key to scaling concurrent agents reliably. This product directly targets developer pain points associated with wiring and managing complex agent interactions. Its utility for performance optimization, code review, pentesting, and migrations positions it as a foundational tool for automating advanced software development tasks. Druids capitalizes on the growing trend of agentic systems, offering a framework to build sophisticated, automated software pipelines.
Hi HN!Druids (https://github.com/fulcrumresearch/druids) is an open-source library for structuring and running multi-agent coding workflows. Druids makes it easy to do this by abstracting away all the VM infrastructure, agent provisioning, and communication. You can watch our demo video here (https://www.youtube.com/watch?v=EVJqW-tvSy4) to see what it looks like.At a high level:- Users can write Python programs that define what roles the agents take on and how they interact with each other.- A program is made of events - clear state transitions that the agents or clients can call to modify state. Each event gets exposed as an agent tool.- Druids provisions full VMs so that the agents can run continuously and communicate effectively.We made Druids because we were making lots of internal coding tools using agents and found it annoying to have to rearrange the wiring every time.As we were building Druids, we realized a lot of our internal tools were easier to express as an event-driven architecture – separating deterministic control flow from agent behavior – and this design also made it possible to have many agents work reliably.We had issues with scaling the number of concurrent agents within a run, so we decided to have each program run in an isolated sandbox program runtime, kind of the same way you run a Modal function. Each agent then calls the runtime with an agent token, which checks who can talk to who or send files across VMs, and then applies the tool call.Our early users have found the library useful for:- running many agents to do performance optimization- building custom automated software pipelines for eg code review, pentesting, large-scale migrations, etc...We've heard that the frontier labs have the infrastructure to quickly spin up 100 agents and have them coordinate with each other smoothly in various ways. We're hoping that Druids can be a starting point to make that infrastructure more accessible.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is Druids – Build your own software factory?
Druids – Build your own software factory is analyzed by our AI as: Making 'software factory' infrastructure, specifically multi-agent coordination, more accessible by abstracting VM infrastructure, agent provisioning, and communication.. It focuses on Druids addresses the complexity of orchestrating multi-agent coding workflows, a critical bottleneck for organizations adopting agent-based develop...
Where did Druids – Build your own software factory originate?
Data for Druids – Build your own software factory was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was Druids – Build your own software factory publicly launched?
The initial public indexing or launch date for Druids – Build your own software factory within our tracked developer communities was recorded on April 10, 2026.
How popular is Druids – Build your own software factory?
Druids – Build your own software factory has achieved measurable traction, logging over 32 traction score and facilitating 5 recorded discussions or engagements.
Which technical categories define Druids – Build your own software factory?
Based on metadata extraction, Druids – Build your own software factory is categorized under topics such as: open-source library, multi-agent coding workflows, VM infrastructure, agent provisioning.
What are some commercial alternatives to Druids – Build your own software factory?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Monkey Morse, which offers overlapping value propositions.
How does the creator describe Druids – Build your own software factory?
The original author or development team describes the product as follows: "Hi HN!Druids (https://github.com/fulcrumresearch/druids) is an open-source library for structuring and running multi-agent coding workflows. Druids makes it easy to do this by abstracting away all ..."
Community Voice & Feedback
I love the idea of using a shared event log for coordination. Smart!I have a Symphony-style[1] factory, which keeps all the context in a single session, but I want to start splitting into stations with separate sessions, and I hadn’t worked out how to do communication between sessions.[1] https://github.com/openai/symphony
Interesting. I like it. Now let's say I currently use the OS process as my primitive for agents, just spawning `claude "foo bar baz"`, and orchestrating this way, using perhaps Unix style of files for intermediate data and piping for transformations. What would you are some good use cases of Druid for someone like me?
When you have 5 workers + a judge all running in isolated VMs, what is a workflow for tracing a failure? Can I replay the event log locally, or inspect what each agent tried? And also, can agents share intermediate logs, results without going through the event system?
I'm going to check this out. I’ve been working on my end-to-end development method and these types of holistic pipelines I think are the future. (or the present!)I've decided to start with concept capture, which then builds out strategy docs, which feed into specs, etc ... might be time for me to share, but I'm in the process of battle testing myself!Looking at your post again, I guess I could script a concepting agent to help hone the idea?
Discovery Source
Hacker News Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.
SaaS Metrics