Why Laravel? That is not the topic here.
This article assumes you already decided to build with Laravel, and instead focuses on a more practical question:
What does the Laravel ecosystem actually look like in 2026, and what should you choose today?
The original draft was based on material gathered through ChatGPT Deep Research, then heavily revised with additional analysis and commentary from actual ecosystem observation. The goal is not neutrality for its own sake, but a realistic reading of where Laravel is heading.
The State of Laravel in April 2026
Executive Summary
As of April 2026, the situation around Laravel starter kits has become fairly clear:
Breeze and Jetstream are not “dead,” but they are no longer the strategic center of the ecosystem.
Laravel officially shifted its public onboarding flow toward the new Starter Kits in 2025. Breeze and Jetstream still receive maintenance updates even in 2026, but their READMEs explicitly position them as belonging to the Laravel 11 era and earlier.
The practical conclusion is:
- Breeze should no longer be considered the default choice for new production systems
- Jetstream remains acceptable for existing systems, but is difficult to justify for new adoption
- The modern default is now Starter Kit + Inertia, especially React
- Livewire is still highly relevant and should not be dismissed as “legacy inertia”
That last point matters more than many people realize.
A surprisingly large portion of the discourse around Laravel UI strategy focuses only on GitHub stars of the public starter repositories. That produces a misleading picture.
Yes, React Starter Kit currently has stronger momentum as the public-facing “entry point.” But the broader Laravel UI ecosystem still shows enormous Livewire adoption.
The ecosystem split is becoming increasingly visible:
- React + Inertia dominates external AI-oriented products and modern SaaS UX
- Vue remains a pragmatic choice for teams with existing Vue investment
- Livewire continues to excel in internal systems, admin panels, and PHP-centric organizations
- Svelte is promising, but still lacks ecosystem gravity for default adoption
The larger story, however, is not merely frontend selection.
The real shift is that Laravel’s AI SDK is beginning to change Laravel’s architectural assumptions themselves.
This is not just “another package.”
Laravel is increasingly treating AI capabilities as part of the framework’s default application model:
- AI SDK
- MCP integration
- Boost
- Cloud APIs
- Agent Skills
- Maestro-managed starter kits
These are not isolated experiments anymore.
They are converging into a coherent platform direction.
Research Assumptions
This analysis prioritizes primary sources:
- Laravel 13 release notes
- Official AI SDK documentation
- Starter Kit documentation
- Laravel blog posts
- Public statements by Taylor Otwell
- Official GitHub repositories, issues, and pull requests
Community discussions in both English and Japanese were used mainly to identify practical pain points rather than as authoritative sources.
One important complication is that the new Starter Kits are distributed as cloneable repositories rather than Packagist packages.
That means install counts cannot be measured in the same way as Breeze or Jetstream.
As a result, public GitHub signals such as:
- stars
- forks
- issue activity
- ecosystem discussion volume
must be treated as imperfect adoption proxies.
This is actually a structural weakness of repository-template distribution models in general.
Comparing the Starter Kit Options
Let’s state the conclusion first.
Breeze is no longer the default recommendation for new production applications.
Jetstream is difficult to justify outside existing systems.
The primary battlefield is now Starter Kit + Inertia or Starter Kit + Livewire.
The strongest default choice today is React + Inertia.
However, dismissing Livewire as merely “legacy momentum” is a serious misunderstanding.
Breeze
Breeze still has real advantages:
- minimal structure
- easy-to-read authentication flow
- relatively small codebase
- useful for backend/API-oriented systems
- easier onboarding for traditional Laravel developers
There is also a practical reality many people understate:
A large number of teams still adopt Breeze successfully even in Laravel 12 and 13.
Why?
Because the modern Starter Kits are heavy.
Not only technically heavy, but operationally heavy:
- rapidly changing upstream conventions
- evolving frontend architecture
- weak documentation stability
- limited Japanese-language ecosystem support
- frontend discipline requirements many Laravel teams historically never needed
In practice, many teams still choose Breeze simply because they can fully understand it.
That matters.
Still, from Laravel’s strategic direction, Breeze is no longer where the framework’s future investment is concentrated.
Laravel increasingly treats the application starting point not as:
“authentication scaffolding”
but rather as:
“AI-ready frontend + auth + DX platform foundation”
That is a major philosophical shift.
Breeze still has value.
But increasingly, that value resembles:
- learning material
- minimal proof-of-concept foundation
- compatibility layer
- reference implementation
rather than “the modern standard.”
Jetstream
Jetstream faces a harder problem.
Historically, Jetstream differentiated itself through:
- teams support
- 2FA
- session management
- more feature-complete authentication workflows
But much of that territory is now being absorbed by the Starter Kit ecosystem itself.
Laravel’s newer Starter Kits increasingly support:
- built-in authentication
- WorkOS integration
- passkeys
- social login
- magic authentication
- SSO flows
- team variants
Meanwhile, Maestro now manages large variant matrices internally across:
- Fortify
- WorkOS
- Teams
- framework variants
As a result, Jetstream’s unique positioning has weakened significantly.
Existing Jetstream systems are still perfectly reasonable to maintain.
But for greenfield applications, the argument for starting with Jetstream has become increasingly thin.
React Starter Kit + Inertia
This is currently the strongest default recommendation for new external-facing Laravel applications.
The reasons are straightforward:
- React ecosystem dominance
- strong AI UI ecosystem compatibility
- shadcn/ui momentum
- Radix primitives
- React 19 ecosystem maturity
- TypeScript-first workflows
- modern component architecture
More importantly, AI-oriented UX increasingly favors rich client-side interaction models.
That naturally aligns with React.
Laravel appears fully aware of this.
The modern Starter Kits are clearly optimized around:
- TypeScript
- component-driven UI
- modern frontend tooling
- AI-ready interaction patterns
rather than traditional server-rendered MVC assumptions.
The downside is equally obvious:
This stack requires real frontend engineering discipline.
Teams accustomed to purely backend-centric Laravel workflows often underestimate:
- frontend state complexity
- TypeScript maintenance
- component architecture overhead
- npm ecosystem churn
- modern frontend build tooling expectations
Still, for customer-facing AI-heavy products, React + Inertia is currently the strongest default choice.
Vue Starter Kit + Inertia
Vue remains the pragmatic choice for organizations already invested in Vue.
The migration cost is lower.
The mental model is stable.
The Composition API ecosystem is mature.
However, React currently has stronger gravity in:
- AI-oriented UI libraries
- external ecosystem examples
- modern component ecosystems
- bleeding-edge frontend tooling momentum
Vue is therefore less “future dominant,” but still highly viable.
For many teams, stability may matter more than ecosystem fashion.
Svelte Starter Kit + Inertia
Svelte is interesting.
The developer experience is genuinely attractive.
Svelte 5 is modern and elegant.
Inertia integration is surprisingly clean.
But ecosystem gravity still matters.
Right now:
- ecosystem scale remains limited
- learning resources are thinner
- Laravel-specific operational knowledge is scarce
- hiring pools are smaller
- official investment signals are weaker
Svelte is viable for teams already committed to it.
But it is still difficult to recommend as the default Laravel frontend strategy.
Livewire Is Not Dead
This point deserves emphasis.
Many discussions incorrectly frame Livewire as a fading legacy option.
The numbers simply do not support that narrative.
Livewire still maintains enormous ecosystem presence:
- tens of millions of installs
- massive production footprint
- strong GitHub activity
- official Laravel investment
- Flux UI integration
- Livewire 4 ecosystem momentum
The important distinction is this:
Public starter kit repository popularity does not equal total ecosystem dominance.
Livewire continues to perform extremely well for:
- internal business systems
- admin dashboards
- operational tooling
- PHP-centric organizations
- teams minimizing frontend specialization
Where Livewire becomes less comfortable is extremely interaction-heavy AI UX with complex client-side state.
There, React usually provides more architectural flexibility.
But for large classes of real-world business applications, Livewire remains extremely competitive.
Calling it “only inertia” misunderstands the actual Laravel user base.
Laravel’s AI Direction
The most important shift in Laravel right now is not frontend technology.
It is the framework’s AI-native direction.
Laravel increasingly behaves as though AI is not an extension layer, but part of the framework’s core application model.
This matters because many frameworks currently integrate AI as:
- external orchestration
- generic SDK wrappers
- thin API abstractions
Laravel is instead attempting to integrate AI directly into:
- queues
- events
- auth
- filesystem
- application lifecycle
- structured workflows
- operational tooling
In other words:
Laravel is trying to remain Laravel while becoming AI-native.
That is strategically important.
And honestly, fairly ambitious.
1-Year Outlook
Over the next year, Laravel’s AI direction will likely continue aggressively.
The signals are already obvious:
- AI SDK
- MCP support
- Boost
- Cloud APIs
- Agent Skills
- Maestro
- Starter Kit consolidation
The likely short-term evolution areas are:
- conversation state stabilization
- tool-loop orchestration
- structured output improvements
- vector-store integrations
- multi-tenant AI architecture support
- operational maturity around AI workflows
This is not based on secret roadmap knowledge.
It is simply the logical reading of where official framework investment is concentrated.
3-Year Outlook
Within roughly three years, Laravel’s UI strategy will probably polarize even further.
The ecosystem split may become:
React + Inertia
- external-facing products
- AI-first experiences
- rich interactive UX
- modern SaaS platforms
Livewire
- internal systems
- management interfaces
- operational tooling
- PHP-centric organizations
- productivity-oriented systems
Vue likely survives as the “stable pragmatic middle.”
Svelte may remain niche unless official investment accelerates significantly.
Meanwhile, Breeze and Jetstream increasingly transition into compatibility assets rather than ecosystem centers.
5-Year Outlook
Five years is long enough that predictions become dangerous.
Still, some directional probabilities are visible.
The Laravel components most likely to remain strategically central are:
- Eloquent
- Queue
- Events
- Auth
- Broadcasting
- Filesystem
- AI-integrated application primitives
- Maestro-managed starter ecosystems
The components most likely to lose strategic importance are:
- legacy authentication starter packages
- older frontend assumptions
- Blade-first public application architecture
This last point deserves nuance.
Blade itself is not dying.
Blade remains deeply embedded inside Laravel:
- mail rendering
- internal templating
- Inertia foundations
- server-side workflows
- operational tooling
But Blade is increasingly no longer the assumed default public UI architecture.
That distinction matters.
Final Thoughts
Laravel in 2026 feels fundamentally different from Laravel in the Breeze era.
The framework is no longer optimizing primarily for:
- simple MVC onboarding
- lightweight auth scaffolding
- traditional PHP-only workflows
Instead, Laravel is increasingly positioning itself as:
- an AI-native application platform
- with integrated operational tooling
- modern frontend expectations
- strong developer experience
- full-stack orchestration assumptions
That creates both strengths and risks.
The strength is coherence.
Laravel increasingly feels like a unified application platform rather than a disconnected package collection.
The risk is that complexity rises.
The modern Laravel ecosystem now expects:
- frontend literacy
- TypeScript familiarity
- operational maturity
- AI workflow understanding
- ecosystem adaptation speed
For some teams, that is exciting.
For others, it is exhausting.
But regardless of preference, the direction itself is becoming difficult to ignore.
And if you are building new Laravel applications in 2026, pretending the ecosystem has not changed is probably the real mistake.
Top comments (0)