There isn't one — and that's the point.
Free Builder ships a fixed scope on purpose: 12 systems, one scaffold (Mongo, Express, React, Node, plus Next.js for the marketing site), and a 206-page kit that covers build, marketing, and customer service. Every "can you add X" instinct gets redirected to a simpler question: does this belong in your product, or in the framework?
The framework stays lean so the AI builds inside coherent boundaries instead of turning into a pile of one-off prompts. Feature requests for the kit itself mostly get declined, not because they're bad ideas, but because bloating the scaffold defeats the reason it works: a 3-week evenings-and-weekends build, not an open-ended backlog.
What you build in your own SaaS is a different call, and it's yours to make. That's the operator's job:
- Bring the domain expertise — the knowledge is what makes your product yours.
- Decide what's worth money to your customers, not what's technically interesting.
- Direct your AI workers to build only that.
- Let the scaffold's boundaries keep the build coherent as you add features.
- Ship, sell, and let real customer demand — not a wish list — decide what comes next.
The discipline of not building every request is a feature of the system, not a gap in it.