Gemini Executive Synthesis
Druids, an open-source library for structuring and running multi-agent coding workflows.
Technical Positioning
Making 'software factory' infrastructure, specifically multi-agent coordination, more accessible by abstracting VM infrastructure, agent provisioning, and communication.
SaaS Insight & Market Implications
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.
Proprietary Technical Taxonomy
Raw Developer Origin & Technical Request
Hacker News
Apr 10, 2026
Show HN: Druids – Build your own software factory
Hi HN!Druids (github.com/fulcrumresearch/d... 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 (
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.Developer Debate & Comments
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?
Frequently Asked Questions
Market intelligence mapped to Druids, an open-source library for structuring and running multi-agent coding workflows..
What is the technical positioning of Druids, an open-source library for structuring and running multi-agent coding workflows.?
Based on our AI analysis of the original developer request, its primary technical positioning is: Making 'software factory' infrastructure, specifically multi-agent coordination, more accessible by abstracting VM infrastructure, agent provisioning, and communication.
Are engineers actively discussing Druids, an open-source library for structuring and running multi-agent coding workflows.?
Yes, we have tracked 5 direct responses and active debates regarding this specific topic originating from Hacker News.
What are the foundational technologies related to Druids, an open-source library for structuring and running multi-agent coding workflows.?
Our proprietary extraction maps Druids, an open-source library for structuring and running multi-agent coding workflows. to adjacent architectural concepts including open-source library, multi-agent coding workflows, VM infrastructure, agent provisioning.
Are there startups building around Druids, an open-source library for structuring and running multi-agent coding workflows.?
Yes, market intelligence reveals commercial overlap. A product named 'Mngr' focuses directly on this: Run 100s of Claude agents in parallel
Engagement Signals
Cross-Market Term Frequency
Quantifies the cross-market adoption of foundational terms like communication and code review by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.
SaaS Metrics