This article is not a technical comparison (let's be clear from the outset that Laravel and Symfony are both excellent) but an analysis of governance and sustainability.
Each technology stack has various attributes:
- A governance model
- A sustainability hypothesis
- An operating philosophy
These aspects, which are often overlooked, are an integral part of the decision-making process we follow when we periodically review our technological choices for future projects.
As we have extensive experience in the world of PHP, which has been evolving at breakneck speed in recent years, we consider Symfony and Laravel, the two major benchmarks in the PHP-based world.
Foundation vs Company: who decides the future?
Symfony is governed by SensioLabs, but through open governance with a distributed core team.
Laravel is essentially Taylor Otwell (and Accel, which has invested £57 million in it and will probably expect a return on its investment).
When you choose a framework, you are also choosing: if the direction changes tomorrow, who decides? The community? Or a single individual? A company?
While Taylor pursues his personal vision for Laravel, Symfony takes a pluralistic and meritocratic approach, where the helm is in the hands of a distributed core team, architectural decisions are made through public discussions, and there is a formal process for RFCs and breaking changes.
Symfony has several advantages: it has institutional resilience (it does not depend blindly on its founder Fabien), large companies (Spotify, Blablacar, etc.) are represented in the core team, and finally, there is a separation of interests (SensioLabs sells Symfony consulting services, but does not have proprietary SaaS that creates conflicts of interest in the design of the framework, as is the case with Larave
Sustainability model
Laravel is basically supported by selling services (Laravel Forge, Laravel Vapor, Laravel Nova, Laravel Cloud, etc.). The mechanism is therefore simple: the free framework attracts developers, who use Laravel in production, buy Forge/Vapor/etc., and the revenue finances the framework.
It works, but it has consequences. First and foremost, architectural ones: Laravel's development direction can follow business logic, generally aligning with what sells well, not just technical best practices.
Symfony, on the other hand, supports itself differently: SensioLabs sells consulting services, but the framework is in no way optimised to sell support.
Symfony's components are so well-made that they are used by Drupal, Magento, Joomla, and Laravel itself. These projects in turn co-finance through contributions, bug fixes, and feature development.
Symfony's sustainability is strong thanks to the distribution not only of the framework, but also of its components.
Symfony has several advantages: it has institutional resilience (it does not depend blindly on its founder Fabien), large companies (Spotify, Blablacar, etc.) are represented in the core team, and finally, there is a separation of interests (SensioLabs sells Symfony consulting services,
Always think about the future
The sustainability of for-profit projects depends on their ability not only to attract developers, but also to generate revenue (especially in the face of substantial investments).
The sustainability of projects led by distributed communities, on the other hand, has historically proven to be more stable and reliable.
There is also a learning aspect: with Laravel, you learn a framework, while with Symfony, you learn universal design patterns. The difference? When Laravel becomes obsolete (like all frameworks), Symfony skills will remain valid.
Of course, there are many other factors that come into play when selecting a framework; Laravel is notoriously much easier to learn, and Symfony is notoriously difficult to understand for those unfamiliar with it.
As an agency, our job is not (only) to build quickly, but to build well. And “well” also means: on foundations that do not depend on the commercial success of a single player, that do not create proprietary lock-in, that respect the principles of open source and distributed governance. This is our techno-political credo, and it is reflected in every technological choice we make.
