Hacker news

  • Top
  • New
  • Past
  • Ask
  • Show
  • Jobs

Show HN: Mastra Factory, the open-source software factory we use to build Mastra

146 points by codekarate 1 day ago | 42 comments | View on ycombinator

brap about 21 hours ago |

Used to play quite a bit with Mastra (not Factory) and it was a very pleasant experience. Cool launch, congrats!

Couple of questions:

1. Did you experiment with not having a separate design/plan phase? From my experience agents usually don’t really know what the plan is until they start editing files and executing tests (in other words, implementing), so the initial plan is usually not great and changing it mid-flight is overhead. I also find reviewing tested code to be much easier than reviewing plans/designs, which are often full of ungrounded assumptions.

2. Is this using your own custom coding agent harness over the raw LLM endpoints users provide? If so, did you consider having it integrate with existing harnesses (e.g. Claude Code, Antigravity, etc.)?

jaf12duke 1 day ago |

What have you learned from people who use Mastra today versus what you/they were doing in the beginning?

Gakho 1 day ago |

> 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?

siscia 1 day ago |

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.

namanyayg about 18 hours ago |

Legendary and congratulations on the launch!

SillyUsername 1 day ago |

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.

moltar 1 day ago |

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?

volkermauel about 13 hours ago |

would love to see a ha production helm chart + k8s sandbox provider (maybe based on k8s-sigs agent sandboxes?)

jobryan 1 day ago |

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)?

_pdp_ about 21 hours ago |

> For us Factory is a configurable agentic kanban board that's @-taggable in Slack.

Software factories are not a real architecture. They are just AI agents working on the same project. GitHub and similar platforms are already ideal for this. Requirements go in as issues, agents open PRs, someone reviews and merges them.

We used to call this software development.

The only "new" part is that now nobody complains at standups!

tireguess 1 day ago |

but you are going to disappear soon swallowed buy some guyz working for a guy called CLAUDE

saarth28 1 day ago |

this is cool!

undefined about 15 hours ago |

undefined

slopinthebag 1 day ago |

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?

solutionsbymeh about 21 hours ago |

nice project

gyuminoh 1 day ago |

[flagged]

agent_yard 1 day ago |

[flagged]

MykhailoSailor 1 day ago |

[flagged]