Background
Laravel is my production framework of choice at KnausDev and has been for over eight years. My architectural patterns have evolved over that time, and I’ve settled firmly on a Domain-Driven Design approach — it scales with the codebase and keeps complexity manageable on the kind of long-lived applications I deliver for clients like Exlink and Dadooo.ai.
Open-source contributions
One thing I missed after committing to DDD was the plugin-style modularity I’d grown used to in WinterCMS, so I built and open-sourced package-generator to fill that gap in my own workflow. I’m also an active maintainer of laravel-openrouter, a community package that’s become genuinely useful since the AI boom.
How I Use It
I use Laravel daily at KnausDev for production-grade SaaS applications, REST APIs, and multi-tenant systems. Beyond greenfield work, a substantial part of my experience is in heavy refactors — taking large-scale legacy Laravel codebases and modernizing them into maintainable architectures.
What I build with Laravel
- B2E platforms: large-scale business-to-employee applications with strong data segmentation and fully white-labeled deployments
- SaaS platforms: multi-tenant systems with isolated data, billing, and role-based access backed by PostgreSQL
- REST APIs: versioned, documented endpoints consumed by Vue 3 and mobile clients, following API design best practices
- White-label systems: fully brandable applications where every tenant gets their own identity, theming, and domain
- Legacy modernization: restructuring codebases that have outgrown their original design into DDD architecture as part of system migration projects
- Zero-downtime migrations: executing large-scale data migrations on live production systems
- Third-party integrations: payment providers, CRMs, and external services
Laravel paired with PHP is where the bulk of my platform engineering and product development work lives. It’s the default for every backend I build.
Status
Active: primary backend framework, expert level.