01The problem it solves
WordPress handles content and standard ecommerce. When the core is a business rule —states, validation, per-record permissions—, modelling it with posts, fields and plugins leaves the logic scattered and hard to test.
That scattering is not obvious at first. It shows when a rule changes: you have to find which plugin, which field and which template hold the exception, then check that nothing else breaks.
Laravel does not remove that complexity: it gathers it in one place where it can be read, tested and migrated. The trade-off is that it requires maintaining an application, a server and a team that can operate it.
If nobody can explain today what states a record has, who approves them and what happens when something fails, moving to Laravel only shifts the confusion elsewhere. The model is clarified before any code is written.
02When it adds value and when it doesn't
Can add value
- The project needs different permissions per record or per role, beyond what native WordPress roles resolve without add-ons.
- Business rules involve states, validation and transactions that posts and custom fields model poorly.
- Several consumers —website, app, public API or integrations— need the same data contract instead of a copy each.
- Background work needs queues, retries and scheduled tasks that run without a page visit.
- The team works in PHP and can maintain an application over time.
- The application is expected to live for years and its domain justifies custom code, tests and controlled migrations.
Doesn't add value
- It is a content or corporate website that WordPress already handles with editing by non-technical people.
- It is a standard store covered by WooCommerce and mature plugins, with no custom rules forcing them.
- The client needs full autonomy to edit and change things without depending on development.
- The team has no PHP and does not want to operate an application and its server.
- The problem is performance or security on a WordPress site: that is fixed with an audit, caching and hardening, not a rewrite.
- WordPress covers the case without forcing it; adding Laravel would duplicate deployment and maintenance with no clear advantage.
The four decisions
-
01
Stay on WordPress
If the problem is covered by content, standard ecommerce or role permissions and the team edits without development, WordPress remains simpler and needs less operation. Forcing Laravel here adds deployment and maintenance with no advantage to offset them.
-
02
A full Laravel application
When the centre is an application with its own rules, a panel and background work, Laravel covers the backend, administration and scheduled tasks in one place. It is the option with the most initial work and also the one that leaves the domain in readable, testable code.
-
03
Laravel as an API and WordPress for content
If the public site is still content-first but some logic does not fit in it, WordPress can stay for content with Laravel behind it as an API. It makes sense when there are several consumers; with only one, it duplicates systems and you have to run both.
-
04
Not going ahead with Laravel
If there is no PHP team, no appetite for running a server and queues, or the problem was performance and is fixed with an audit and caching, it is not considered. It is also ruled out when WordPress covers the case without forcing it: a new stack does not fix a decision that was never made.
03What we do
Laravel isn't the service: the service is what gets built with it. These are the usual pieces, each one with its scope and its cost.
-
01
Data model with entities, states, permissions and transactions.
Go to Custom applications -
02
API with a stable contract for the consumers that need it.
Go to Custom applications -
03
Admin panel adapted to the people who will use it.
Go to Custom applications -
04
Queues and scheduled tasks for work that must not depend on a request.
Go to Custom applications -
05
Integrations with the systems already in place.
Go to Custom applications -
06
Reversible migrations and version control for the schema.
Go to Custom applications -
07
Tests for the critical flows before deployment.
Go to Custom applications -
08
Deployment, documentation and handover with the agreed repository and access.
Go to Custom applications
04Performance and maintenance
Can be measured
- Queries per request and slow queries, before and after each change.
- Queue depth and time, including retries.
- Index usage and execution plans for the heaviest queries.
- Response times for endpoints and panel screens.
Can't be promised
- That Laravel scales without limit: the ceiling depends on the database, the infrastructure and the code, and it is measured under real load.
- That it is always faster than WordPress: it depends on the case and on what each one does.
- A number of concurrent users without having tested the system under equivalent load.
Maintenance
Update the framework and dependencies, review security, apply reversible migrations and keep backups of database and code. PHP, the database, the queues and the scheduler also have to be operated. It costs more than maintaining a content site and is agreed separately.
Price and timeline
Quoted after diagnosis. It depends on the scope of the domain, the roles, the integrations, the data migration and the planned maintenance. There is no fixed price before the case is reviewed.
See the speed and WPO service05Proof: stated capability
Declared capability. There are no publishable cases or verified metrics with Laravel on this project, and evidence per technology is still pending.
What I can show is the reasoning: what gets modelled, what gets tested and what gets handed over. If you need specific references, ask for them before hiring, and I will state plainly what exists and what does not.
This page explains when Laravel fits and when it does not. It is not a claim of proven experience or a promise of results.
See the projects06Frequently asked questions
Does Laravel replace WordPress?
Not by default. WordPress remains the core for content websites, standard WooCommerce, rescue and performance. Laravel is considered when business rules, per-record permissions, several data consumers or background work would only be covered in WordPress by forcing posts, fields and plugins.
What maintenance does a Laravel application need?
Framework and dependency updates, security review, backups and tests before each deployment. PHP, the database, queues and scheduled tasks also have to be operated. It costs more than maintaining a content website and is agreed separately.
Can it integrate with an existing WordPress site?
Yes, as a separate application or API that exchanges data with WordPress when the case justifies it. Laravel is not a plugin and is not installed inside the theme. The integration is tested in a separate environment with defined permissions.
Where is it hosted?
On a server or container with PHP, a database and the services the application uses, such as queues. The environment is defined with the project; no specific hosting is recommended without knowing load, data and operation.
How much does it cost?
Quoted after diagnosis. It depends on users, rules, integrations, permissions and planned maintenance. There is no hourly rate or fixed package for applications while the scope is not written down.
Who owns the code?
Laravel is distributed under the MIT licence. The application code belongs to the client if the contract says so, and is delivered with a repository and documentation. Third-party dependencies keep their own licence.