Twelve posts into this series, the question I actually get in replies isn’t “is this good.” It’s “do I need the Pro tier, or am I fine with just the free part.” That’s a fair question to ask a person selling something, and it deserves a straight answer instead of a sales one.
Stay on the free core if you’re a solo developer or a small team shipping one product, and you’ve already got a review process disciplined enough to catch a controller that drifts from convention before it merges. The architecture — the response envelope, the exception hierarchy, safe concurrency, tenant-scoped caching, Octane discipline — is yours forever, MIT licensed, with no functional gap between what you get for free and what a paying customer gets on the correctness side. I mean that literally: nothing in the free tier is deliberately hobbled to push you toward paying. It’s a complete, production-grade foundation on its own.
Reach for the Pro tier when the cost stops being “is the architecture correct” and starts being “how much of my week goes to enforcing and repeating it.” That’s a different problem, and it shows up in specific, recognizable ways: your team is building more than one or two modules a sprint, and hand-assembling the same eleven-file skeleton correctly, every time, is eating hours you’d rather spend on the feature itself. Or “why is this endpoint slow” has come up more than once this month, and the honest answer is you don’t actually know, you’re guessing, and a proper APM tool feels like overkill for the size of the question. Or you’re already leaning on an AI assistant for a meaningful share of your code, and you’ve noticed it keeps writing the pattern Laravel defaults to instead of the one your team actually uses.
None of these are correctness problems. They’re velocity problems, and velocity problems are exactly what a paid tool should solve — that’s the same reason your team already pays for a CI pipeline, an APM tool, or a paid IDE plugin, without treating any of those as controversial. The free architecture answers “is this right.” The Pro tier answers “how fast can we keep doing it right, at the pace the business actually needs.”
If you’re unsure which side of that line you’re on, there’s a fast test: look at the last sprint. If nobody on the team spent time re-explaining a convention, rebuilding a module skeleton by hand, or guessing at a performance problem instead of measuring it, you’re fine where you are. If any of those happened more than once, that’s not a hypothetical cost — that’s this month’s evidence.
Either way, start with the free core. composer require rupeshstha/core-foundation. If it earns your trust the way it’s meant to, https://packagist.org/packages/rupeshstha/core-foundation is where the rest of it lives.
Full docs index: Welcome to Core Foundation · Installation. Pro tier, in detail: Scaffolding · Server Timing · Agentic Skills