Hi HN, we're Shane, Sam, and Abhi.
Almost two years ago, we shared Mastra, our open-source TypeScript agent framework, on Show HN: https://news.ycombinator.com/item?id=43103073. It got a few hundred upvotes; a couple of weeks later our downloads had doubled, and we were off to the races.
Today we're sharing Mastra Factory, the open-source software factory we built to help maintain Mastra itself.
At Mastra, we now average nearly 4M downloads per week, and with Factory our team now merges hundreds of PRs a week across the mastra-ai GitHub org. Last week, Factory opened and merged 238 PRs, alongside 630 merged PRs from humans.
There's a lot of debate about what a software factory is. For us Factory is a configurable agentic kanban board that's @-taggable in Slack.
Under the hood, it uses Mastra’s durable agents for long-running sessions, our conversational memory system, a markdown based wiki with source citations to incorporate company knowledge, signals that subscribe to PR comments wired up into sessions, and a customizable cloud sandbox with our coding harness (working on supporting Claude Code, Codex etc).
When we started out, we modeled Factory around our existing workflow-oriented process (triage, plan, build, review, shipped). Three months later, we find ourselves mostly driving it through Slack vs a web UI.
We’ve seen more senior engineers kick off sessions in parallel (“triage the 20 oldest issues and let’s evaluate…”). We’re using bug and vuln scanners now, and we’ve closed our repo to outside contributors, asking folks to write detailed issue repros instead.
You can get started with `npm create factory`.
It’s fully open-source, so you can run it entirely on your infra (we also offer a hosted version). Comment here, we would love to know what you think!
What have you learned from people who use Mastra today versus what you/they were doing in the beginning?
> closed our repo to outside contributors
I've seen this pattern happening in other open-source repos. Do you think it's going to be the norm now?
Just to clarify, as I couldn’t confirm this from the docs. Do agents run with their own identity or is it assuming engineer github identity?
This needs more visuals - the kinds of people using this may not be software developers, and it seems just like a command line too at first glance unless you watch the video.
Excited to try. Do you have a video demoing how you use it (or just best practices for getting up and running well on my team)?
i'm always curious how the workflow with these factories work. like are you basically just giving it tickets and letting the ai use it's "judgement" on how to implement them? do you essentially say something like "we need X" and the agents do the rest? or is it somehow more interactive? and what about verification, particularly on the UX side of the end result?
but you are going to disappear soon swallowed buy some guyz working for a guy called CLAUDE
[flagged]
I build something similar, based on similar ideas: https://factory.redbeardlab.com
There is a [language](https://redbeardlab.github.io/dotFactory/) that let express complex workflows.
The workflow can be pretty much anything, eg:
1. Clone repo A and B + Start OpenCode + Feed a prompt into it
2. Pick up the commit generated by opencode for both repo, and run CI
Another workflow I created is: every day at 3AM, check that the documentation of the website is up to date, if yes exit, if not update the documentation. Pass the updated documentation to an adversarial LLM and if it pass, merge it - otherwise loop with the feedback from the adversarial one.
You have a concept of trigger, which can be either a webhook, or a github PR or a github issue, or just a cron expression. Or just someone manually clicking.
There is a concept of secrets and config, so the user can create their own secrets to start codex-cloud, or opencode, or making custom API call.
There is also the concept of manual gate, so you can wait for an human to actually click a button.
Finally, it supports running containers. Useful if you want to call an obscure API from your workflow, you don't have to wait for the platform owner to create a step for your API, but you can just run a container into it.