Laravel

Filament: an admin panel for Laravel applications

The admin panel is the part of a system your customers never see and your own people spend eight hours a day in. Filament shortens the road to building one - provided you know what it does not do.

6 min read

Any application that does more than display content eventually needs a second face: a place where staff review orders, correct data, approve requests and work out why something went wrong. That part costs a surprising amount, because it consists of dozens of dull screens, each of which has to be designed, labelled and secured.

Filament is a tool for building exactly those panels in Laravel. It is not a ready-made system you install and use — it is a set of building blocks a developer assembles into a panel that fits one particular process. That distinction drives everything below.

How this differs from WordPress

WordPress arrives finished: you log in and get a panel somebody designed for you. The upside is that it works on day one. The downside is that your processes have to bend to someone else's assumptions, or be propped up with plugins.

Filament is the opposite: nothing is ready except the mechanisms. The screens are described by a developer, in code, against your data model. So the panel looks like your work rather than like the template author's idea of it — but somebody has to write it.

A simple test. If you need a site with content, a blog and a contact form, Filament is beside the point. If your people spend every day entering data into a system with rules specific to your industry, it starts to make sense.

What actually saves time

Describing a single resource — an order, say — immediately gives you a list with search, filters and sorting, a create and edit form with validation, a single-record view, bulk actions and export. Those are the dozens of dull screens nobody has to write from scratch.

On top of that come things usually bolted on later and on a tight budget: notifications, dashboard widgets with key numbers, support for several panels inside one application (one for staff, one for customers) and separation of data between customers in a multi-tenant setup.

The practical effect is that the conversation with your team moves from "how do we build a filtered table" to "what are the rules for approving an order". The second one is what you are really paying for.

What Filament does not handle — where the costliest mistakes live

The documentation says it outright: Filament provides no guarantees about the security of your application. That is not a disclaimer for form's sake, it is a warning about one specific misunderstanding.

The most common one concerns separating data between organisations. The multi-tenancy mechanism narrows what a user sees within the selected organisation — but it is not a per-record authorization system. The query that builds a list does not pass every row through an access policy. If someone on the team concludes that because data is split between tenants the permissions are "done", you end up with a panel where an employee sees records of their own company that they have no business reading.

Two related traps are worth knowing, because they look harmless:

  • Removing global scopes also removes tenant isolation. One line added while building a report can show every customer's data at once.
  • Uniqueness validation does not see global scopes. A check for "does this number already exist" searches the whole table by default, other tenants included — so it either reveals that their records exist or blocks a number that is free for you. There are separate scoped variants of that validation and they have to be used deliberately.

The takeaway for whoever commissions the system: "does the panel have permissions" is too vague a question. Ask who can see an individual record, who can change it, and where that is written down. The answer "Filament handles that" is wrong.

Versions, and the part nobody enjoys planning

Filament ships new major versions regularly, and support for old ones ends on a published schedule. As this is written, version five is current, version four still receives bug fixes, and version three gets security fixes only — it stopped receiving new features back in 2024.

That has two consequences. First, upgrading the panel is not an optional whim but ordinary maintenance, much like upgrading Laravel itself. Second, Filament brings requirements with it: the current release needs at least PHP 8.2 and a reasonably recent Laravel. A panel on an old server will not be upgraded until the environment is.

The good news: the maintainers ship a tool that walks through the code and performs the mechanical part of moving to a new version. The bad news: community plugins do not always keep pace, so before upgrading you have to check that every plugin the project uses is ready.

Ask for the version in the quote. "We will build the panel in Filament" and "we will build the panel in Filament 5" are two different offers. A panel delivered on a version that will be down to security fixes within a year starts ageing before you accept it.

Licence and cost

Filament itself is open source and free. The vast majority of plugins are too, though some are paid. The cost of a system built on Filament is therefore not a licence but developer time — which is exactly why the scope, not the tool, is what to ask about.

How it works technically

Filament runs on the server: the interface is described in PHP and the browser receives ready-made fragments of the page. For a team that knows Laravel this is an advantage, because little has to be written in JavaScript. The price is that some interactions require a round trip to the server, and unusual interface behaviour still ends in custom browser-side code.

For the record, starting a panel in an existing application is three commands in practice: install the package, run php artisan filament:install --panels and create the first user. That can be misleading — the panel is standing within minutes, but it is standing empty. The real work begins when the resources and the rules are described.

When we advise against it

When the application has two or three admin screens and no sign of more: the learning and maintenance overhead will not pay off at that size. When the team knows neither Laravel nor Livewire, because extending the panel beyond the standard blocks needs both. And when the panel is meant to be a product sold to end customers as their interface — Filament is a tool for internal work, not for building a polished consumer application.

What to check on delivery

Three things whose absence only shows up months later: written access rules for individual records, together with tests that verify them; a named Filament version and a plan for upgrading it; and a list of plugins used, stating which are paid and who maintains them.

An admin panel outlives the website in front of it. It is worth knowing from day one who sees what inside it.

Not working out?

If the problem stays, or you would rather not experiment on a live site, write to us and we will look at it. The diagnosis costs nothing.

Web applications

Other guides

Drupal 10 reaches end of life

Drupal 10 stops receiving security fixes on 9 December 2026. If your site runs on it, you have weeks left to decide - and the cost depends mostly on which version you are starting from.

Getting started with AI in your company

Most failed AI projects do not fall over on the technology, but on the choice of process. So we start with what is countable and repetitive, not with what looks most impressive.

A slow website

A slow site is never one fault, it is the sum of several. We start by measuring, because without that optimisation is guesswork - and usually speeds up what was already fast.

An expired SSL certificate

Instead of your site, visitors get a red warning and have to click through "proceed anyway". Most of these cases are an expired certificate or a renewal that never finished.

Moving a website to new hosting

A migration goes well or badly depending on the order of the steps. The most expensive mistake is switching DNS before checking that the site works on the new server at all.

WordPress redirecting to spam sites

Visitors land on somebody else's site, and Google shows spam where your offer used to be. That is a break-in, not a fault - and cleaning the files alone will not hold.

The WordPress 500 error

HTTP 500 is the server saying something interrupted the code. On its own it tells you nothing - the whole job is getting to the log.

The WordPress white screen

Instead of your site you get blank white. It is one of the most common symptoms, and in most cases it can be defused in a quarter of an hour.