A maintainer I respect quietly stopped responding to issues on a package I depend on. Not an announcement, not a farewell post — just a graph of commits that flattens out, and a backlog of issues that stops getting triaged. I don’t know their reasons and I won’t guess at them. But I’ve been close enough to that exact edge myself, on smaller projects, to recognize the shape of it from a distance: years of unpaid maintenance on something people depend on, with no path where the effort and the reward ever meet.
I built the free half of core-foundation — the base classes, the response envelope, the exception hierarchy, the locking, the tenant-safe caching, the Octane discipline — over eight years, inside client work, on someone else’s clock. Open-sourcing it costs me nothing I haven’t already spent. Maintaining it well, for strangers, forever, for free, is a different commitment entirely. And I’ve watched enough good tools go quiet because that second thing was never accounted for.
So I split the package on purpose, before launch, instead of bolting a price onto it after the fact once I resented maintaining it for free.
The architecture — everything the last six posts have covered — is MIT licensed and stays that way. Not a trial, not a “free tier” that quietly shrinks over time. If you never pay me anything, you still get a correct response envelope, a real exception hierarchy, safe concurrency handling, tenant-scoped caching, and Octane-safe bindings. That’s the part I want to become how Laravel APIs are built, and gatekeeping it behind a price would work directly against that goal.
What’s paid is the part that took the architecture from “correct” to “fast to actually use, every day, on a real team.” Scaffolding that generates a fully-wired module in one command instead of you hand-assembling eleven files from memory. Server-Timing profiling that shows you exactly which layer of a request is slow, in Chrome DevTools, without adding a single third-party APM tool. An AI assistant context layer that means Claude or Cursor or Copilot already knows this architecture, so the code it writes for you matches the conventions instead of you correcting it after the fact. These aren’t the ideas. The ideas are free. This is the labor of turning the ideas into tools that save you actual hours, maintained by someone who gets paid to keep maintaining them.
I’m not pretending this is purely generous. I want this package to be worth building a business around, not just a portfolio piece I open-sourced for the credibility and then let go quiet in a year. A price is what makes “in a year” a promise instead of a hope.
If the free architecture is useful to you, use it — that’s the whole point of it being free. If the tooling on top saves you the hours it saves me, that’s at https://packagist.org/packages/rupeshstha/core-foundation, license-gated, same as any other serious dev tool you already pay for without thinking twice about it.
The next three posts go through exactly what that Pro tier does, in the same detail as everything before it.
Free architecture, start to finish: Welcome to Core Foundation · Installation