Why we broke Fastfony into pieces
From monolith to modular
The monolith that nobody adopted
The first Fastfony was a fully-featured starter-kit — authentication, admin panel, CMS, e-commerce, API, the works. Battle-tested. Production-ready. Too opinionated, too complete. Removing what you didn't need cost more than starting from scratch. Adoption stalled.
The real job to be done
Developers don't want a finished product. They want a fast way to assemble the pieces they need. Authentication, email, billing, admin — each as an independent, focused dependency, glued together by the developer's own code.
The shift
Fastfony is now three things. A collection of MIT-licensed Symfony bundles that do one thing each. A few Composer packs that bundle curated tooling. And a Claude Code skill — the expert who knows how to assemble the pieces into a starter-kit tailored to the developer's request.
What that means for you
If you came for the original monolith: it's still on GitHub, but we no longer recommend it as a starter. If you came looking for a pragmatic way to bootstrap a Symfony app: install the bundles you need, let the skill handle the plumbing.