Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

FHoulbreque's avatar

Filament 4.0 production readiness

Hello everyone,

Just starting a new project that would greatly benefit from being Filament based, especially with the shorter time it will take for me to complete it using this tool, I am still wondering what I should base the project on.

Initially, I thought going Laravel 11/Filament 3 combo but, as this project would be only deployed in early october, maybe it would be better to use Laravel 12/Filament 4... especially as it's using Tailwind 4 and I plan to use it on the non Filament pages.

Would you think it already ready for using it in production, or should I stick to Filament 3 and upgrade later on the project?

Thanks :)

0 likes
3 replies
LaryAI's avatar
Level 58

Filament 4.0 is currently in active development and, as of June 2024, is not yet officially released as a stable version. The Filament team has stated that Filament 4 will support Laravel 12 and Tailwind CSS 4, which is great for future-proofing your project, especially if you plan to use the latest features and want consistency across your admin and frontend UI.

Here are some considerations:

  1. Production Readiness:

    • If your project is mission-critical or you require maximum stability, it’s generally best to stick with the latest stable releases (Filament 3.x with Laravel 11).
    • Filament 4 may have breaking changes, incomplete documentation, or undiscovered bugs until it reaches a stable release.
  2. Timeline:

    • Since your deployment is planned for early October, there’s a chance Filament 4 will be stable by then, but there’s no guarantee. You can monitor the Filament GitHub repo or their Discord for updates.
  3. Upgrading Later:

    • Starting with Filament 3 and upgrading to 4 later is a safe approach. The Filament team usually provides upgrade guides to help with migration.
    • If you start with Filament 4 beta/RC, be prepared for possible breaking changes and the need to refactor as the API stabilizes.
  4. Tailwind 4 Support:

    • If you need Tailwind 4 features now, you might need to use Filament 4 (beta) or find workarounds to use Tailwind 4 with Filament 3, which could be tricky.

Recommendation:

  • For maximum stability and support, start with Laravel 11 + Filament 3.
  • If you are comfortable with potential instability and want to use the latest stack, you can experiment with Laravel 12 + Filament 4 beta/RC, but be ready for changes and possible issues.
  • Keep an eye on the Filament 4 release progress. If it becomes stable before your launch, you can consider switching or upgrading before deployment.

Example: Installing Filament 3 with Laravel 11

composer create-project laravel/laravel:^11.0 my-app
cd my-app
composer require filament/filament:"^3.0"
php artisan filament:install

Upgrading Later:
When Filament 4 is stable, you can follow the official upgrade guide to migrate your project.

Summary:
Unless you have a strong reason to use Filament 4 right now, it’s safer to start with Filament 3 for a production project. Monitor the Filament 4 release, and plan your upgrade accordingly.

Glukinho's avatar

Even Filament website states that version 4 is in beta and 3.x still should be used for stability: https://filamentphp.com/docs/4.x/introduction/overview

You are currently viewing the documentation for Filament 4.x, which is currently in beta and is not stable. Breaking changes may be introduced to releases during the beta period. Please report any issues you encounter on GitHub. Looking for the current stable version? Visit the 3.x documentation.

So, I think you should stick to 3.x for now.

FHoulbreque's avatar

@Glukinho I noticed that, but as the project significantly evolved in the past month, I thought better to ask if people new how close to a RC this was. But I'll probably be safe and stick to the laravel 11/filament 3 option.

Or I go to Laravel 12 and forgo filament altogether and just use Livewire. Another approach to the issue.

Thank you for reacting anyway :)

Please or to participate in this conversation.