I’ve been working on MCF for quite a while, mainly because I wanted a better way to structure larger Laravel applications. Laravel already gives us most of the tools we need, but when an application grows, I found myself repeatedly making the same architectural decisions: how to organize features, where workflows should live, how to handle access control, storage, auditing, and other common parts of the application. So I started building MCF on top of Laravel to provide a consistent structure for these things without trying to replace Laravel itself. MCF is built around modules and workflows, with additional components for things like access control, authentication, storage, auditing, notifications, and code generation. It’s still something I’m actively improving, and I’m sharing it because I’d genuinely like to hear how other Laravel developers approach this problem. If you work on larger Laravel applications, I’d be interested to know how you structure them and what you think could be improved in MCF.

MCF Laravel

A modular application architecture for Laravel

A modular application architecture for Laravel