Show HN: Mastra Factory, the open-source software factory we use to build Mastra
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!
I've seen this pattern happening in other open-source repos. Do you think it's going to be the norm now?
also there are a few folks on our team who we got to know because they showed up in our repo and started contributing, and maybe that sort of serendipity won't happen in the future
I suspect sticking your public repo somewhere other than GitHub and sharing it in more organic programming communities (discord, forums, your hn bio etc) would further reduce the amount of low effort slop you get.