Laravel and Filament support dates, and when your admin system needs an upgrade

A lot of the booking, patient-record and back-office systems built for small businesses in the last few years run on the same two tools. Laravel is the framework underneath, and Filament draws the admin screens your staff use all day. Ours run on them too. Both projects publish the exact date each version stops getting fixes, and for systems built between 2022 and 2024, several of those dates have already passed.

That does not mean the system stops working. It means that if someone finds a new security hole, nobody will fix it for your version. Below are the dates, what they mean in practice, and why the upgrade belongs in the quiet months.

What changed

• Laravel 13 came out on 17 March 2026 and is the current version. It gets security fixes until 17 March 2028.
• Laravel 12 stopped getting bug fixes on 13 August 2026. It still gets security fixes until 24 February 2027.
• Laravel 11 stopped getting security fixes on 12 March 2026, and Laravel 10 on 4 February 2025. Laravel 9 and older are further past it.
• Filament v5, announced on 16 January 2026, is the current version of the admin panel. Filament says that apart from support for Livewire v4, it has no changes over v4.
• Filament v4 gets security fixes until 15 January 2028, and Filament v3 until 1 January 2028. Filament v2 stopped getting them on 1 January 2026.
• Both run on PHP. PHP 8.1 reached end of life on 31 December 2025. PHP 8.2 stops getting security fixes on 31 December 2026.

Laravel's rule is 18 months of bug fixes and two years of security fixes for every version, with a new version about once a year (Laravel release notes). Filament and PHP publish their own tables (Filament support policy, PHP supported versions).

What it means for your business

If nobody has upgraded your system since it was built, the build year tells you roughly what it runs on:

• Built in 2022: probably Laravel 9 and Filament v2. Neither gets security fixes any more. This is the case that needs a budget now.
• Built in 2023 or 2024: probably Laravel 10 or 11 with Filament v3. The admin panel gets security fixes until January 2028, but the framework underneath it gets none. Filament itself warns that apps on older versions "could still be vulnerable" through PHP, Laravel or Livewire.
• Built in 2025: probably Laravel 12, which gets security fixes until 24 February 2027. It is not urgent, but it belongs in next year's plans.

"Out of support" is not the same as "broken". The bookings screen will open tomorrow just as it did today. What changes is the risk. A system that holds customer names, phone numbers, payments or medical notes keeps running on code that nobody will patch.

The more practical pressure usually comes from your hosting company. Hosts drop old PHP versions from their servers. When that happens, the upgrade stops being something you plan and becomes something you do on their schedule.

There is some good news: upgrades are less painful than they used to be. Laravel says it tries to make every move to a new major version take "one day or less", and calls version 13 "a relatively minor upgrade in terms of effort". Filament ships an automated upgrade script and says the move to v5 needs no manual steps beyond it. Those are the vendors' own words. A real system with years of custom work will take longer, and most of that time goes on testing, not rewriting. How much longer depends on the project. Nobody can quote it honestly without looking at the code.

Your staff may also get something out of it. Filament reports that its August 2026 releases made form fields render 86–92% faster, and tables with row actions about 49–52% faster. These are Filament's own benchmarks, not independent tests. Still, on a screen that lists thousands of bookings, the difference is usually one people notice.

What to do before the season

The worst time to find out you are on an unsupported version is the week your host emails a deadline in the middle of August. For a dive centre or a rental business, that means booking the work for the winter. For a ski shop, it means the summer.

1. Ask your developer which versions of Laravel, Filament and PHP the live system runs on.
2. Ask your hosting company when it plans to remove PHP 8.1 and 8.2 from its servers.
3. If the answer includes Laravel 11 or older, Filament v2 or PHP 8.1, ask for an upgrade estimate now and schedule the work for your off-season.
4. If you are on PHP 8.2, plan the move before 31 December 2026.
5. Ask for the upgrade to be tested first on a copy of the system with real data, including a full booking and a payment, before it touches the live one.

If you are no longer sure who looks after your system, sort that out first. Upgrades like this are part of the systems we build and maintain.

For the technically minded

• Laravel 13 requires PHP 8.3–8.5. Bug fixes are listed as "Q3 2027", and security fixes run to 17 March 2028. Laravel 12 supports PHP 8.2–8.5.
• Filament 5.x requires PHP 8.2+, Laravel 11.28+ and Tailwind CSS v4.1+. v5 is v4 plus Livewire v4, and the upgrade script covers it. v4 bug fixes run until 15 January 2027. v3 bug fixes ended on 1 August 2026. v6 has no announced date, and v5 support is due to last about 1–2 years after v6 ships.
• Because Filament 5 needs Laravel 11.28 or later, an app on Laravel 9 or 10 has to move the framework, and PHP with it, before the panel.
• PHP security support: 8.3 until 31 December 2027, 8.4 until 31 December 2028, 8.5 until 31 December 2029.
• Filament v4.12.6 and v5.7.6 also patched CSS colour sanitisation, added opt-in protection against CSV formula injection, and added limits on query-builder rules. That is a reason to be on a current patch release, not just a current major.