Companies Using Livewire

The best measurement of Laravel on this site is not the Laravel page

Livewire cannot run without Laravel. It is a Laravel package, it registers Laravel routes, and there is no port of it to anything else. So every domain where we detect Livewire is a Laravel domain, with no inference required.

We currently detect Livewire on 33,940 domains. Only 2,930 of them also return a Laravel signal. That is 8.63%. The remaining 31,010 are running Laravel and our Laravel detection cannot see them.

This is not a bug in either rule. It is the difference between two detection surfaces. Laravel is matched from a session cookie and framework headers, and a production Laravel deployment routinely renames the session cookie and strips the headers, because the framework's own documentation suggests it. Livewire is matched from a JavaScript global and a script file that the browser must download for the page to function at all. One signal is optional and the other is load-bearing.

The consequence is arithmetic. We publish Laravel at 92,822 domains. Add the 31,010 Livewire domains that Laravel detection misses and the floor becomes 123,832, a 33.4% understatement, and that is from one package. Anything else that is Laravel-only and browser-visible would push it further. Read our Web Frameworks ranking with that in mind: the gap between ASP.NET at 46.19% and the PHP frameworks below it is partly a real difference in deployment scale and partly a difference in how loudly each stack announces itself.

The exit is to JavaScript, not to another PHP framework

2,158 domains have dropped Livewire since we began tracking it. The obvious way to read that table is wrong twice over.

The largest destination by raw count is Alpine.js, on 400 of those domains. It is not a destination. Livewire version 3 bundles Alpine, so Alpine is present on 98.04% of live Livewire domains and its appearance among leavers is under-represented, not over: 18.54% of churned domains against 98.04% of active ones, a ratio of 0.19. The second largest is Laravel itself at 65 domains, which is not a destination either, because you cannot leave Livewire for the framework it runs inside.

Comparing the rate on churned domains with the rate on live ones sorts this out. Next.js is 4.46 times over-represented among leavers, Nuxt.js 4.06, Express 3.35, Inertia.js 2.67, Angular 2.62, Ruby on Rails 2.27 and React 2.03. Microsoft ASP.NET sits at 1.01, which is coexistence rather than movement, and Vue.js at 0.83 and Svelte at 0.82 are below the line for the same reason.

The one that matters is Inertia.js. It is the only in-ecosystem substitute that clears the bar. Inertia and Livewire answer the same question for Laravel teams, which is how to build a reactive interface without maintaining a separate API, and they answer it in opposite directions: Inertia ships a Vue or React front end, Livewire renders from PHP. A team that changes its mind moves between those two, and 69 of them did. Inertia has no profile on this site yet, so that row is stated here rather than linked.

The traffic runs the other way, and it is larger

Against 689 domains that now run Livewire and have dropped React, and 268 that have dropped Vue.js, the outbound flows of 62 and 108 look small. We checked whether that is real movement or detection flicker by bucketing the drop dates: the React cohort accumulates smoothly across August and early September with no single day carrying more than 7.3% of it, which is not the shape a crawl artifact makes.

So the direction is genuine, and it is the direction Livewire's own pitch predicts: sites replacing a JavaScript front end with server-rendered PHP. We would still read 689 as a floor rather than a headline. Our churn window is about three months old, and a site that quietly removed React two years ago is invisible to it.

What the flat industry curve is telling you

No industry accounts for more than 4.09% of matched Livewire companies. That is unusual. XenForo, published alongside this profile, has a single cluster of games, motoring and sport that defines the platform. Livewire has nothing of the kind.

The reason is who makes the decision. The three technology industries together are 11.50%, and those are the agencies and consultancies that build with Laravel. Everything else, in order, is retail, real estate, construction, financial services and accounting, which is a client list rather than a market. Livewire is chosen by the builder, so it lands wherever the builder's next project lands. The 1 to 10 employee band at 57.67% is the same fact from the other side.

If you sell to Livewire teams, the flat curve means the industry filter is close to useless and the firmographic one is not. A 1 to 10 person agency in Germany, the Netherlands or the United Kingdom is a far better description of this base than any vertical.