Laravel Filament plugins for a full website: what to install

Filament gives you an excellent admin panel, but a public website needs more than a panel: pages, menus, SEO, redirects, forms, a media library, roles and backups. Filament's plugin directory lists more than 1,200 plugins, so most of these jobs have an answer. The harder questions are which plugins to pick and what is still left for you to build.

Here is a short list for each job, then what plugins leave open, and when a CMS is the better choice.

The plugins, job by job

All of these list Filament 5 support on their directory pages as of October 2026. Check each package's composer.json before you rely on it, as version lists can lag behind the code.

Job	Plugin	What it does
A CMS in one package	TallCMS Core (tallcms/cms)	Pages and posts, menus, a media library, SEO tools and a block editor. MIT
Pages with SEO and redirects	Flexible Content Block Pages (statikbe/laravel-filament-flexible-content-block-pages)	Block-based pages, a menu builder, SEO fields, redirects, a sitemap and multilingual URLs. MIT
Menus	Menu Builder (datlechin/filament-menu-builder)	Nested menus that you render anywhere in the application. MIT
Media	Curator (awcodes/filament-curator)	A media picker and manager with image transformations. MIT
Forms	Bolt (Lara Zeus)	A form builder for your users, with a separate paid Pro edition
Roles and permissions	Shield (bezhansalleh/filament-shield)	Policies and permissions for your panels. MIT
Activity log	Activity Log (rmsramos/activitylog)	Screens over Spatie's laravel-activitylog. MIT
Backups	Spatie Laravel Backup (shuvroroy/filament-spatie-laravel-backup)	Create, monitor, download and delete backups. MIT

For a small site, one of the first two rows and a backup plugin may be all you need. Look at them first, because each plugin you add later is one more thing to keep up to date.

What to check before you stack them

Each plugin can be good on its own. These questions are about what happens when you combine several:

• The next Filament upgrade. Your panel can only move to a new major version once every plugin you depend on has moved too.
• Security. The directory itself warns that, apart from official plugins, "the security of all others is not reviewed or vetted". Read the code of what you install on a public site.
• Who draws the public pages. An admin plugin gives you a screen and a table. Check what it gives the front end: routes, templates, canonical URLs, search, a page cache. Whatever it leaves out is your code to write and maintain.
• Roles across plugins. Check that every plugin's screens respect the roles you set up, and that an editor can't reach settings meant for an administrator.
• Who does the daily work. Plugins give a person a screen. If an AI agent is going to run the site, it needs tools for each of those jobs, with limits on what it may do.

When plugins are the right choice

Stay with plugins when:

• The site is a small part of a larger application. Your Laravel app has a Filament panel and needs a few pages and a menu. A CMS would be far more than you need.
• You need it free. Everything in the table has a free edition. kitloom does not.
• You want your own data model. Plugins let you shape your tables. kitloom's content is stored in the WordPress data model.

When the site is the product: kitloom

kitloom is a Laravel CMS with Filament or Nova as its admin, and an AI agent can run the site under your control. It isn't a plugin you add to an existing panel. Its modules need kitloom's core and data model, and it is sold whole: $149 for one site or $299 for every site you build.

In exchange, these jobs come as modules of one product, released and tested together: SEO, Redirections, Forms, Backup, Activity Log, the shop, bookings and more. There are also themes in Blade, Vue or React for the public pages.

A module's screens are ordinary Filament resources and pages. Installing the package is enough, because its service provider adds the plugin to the panel, and a config switch turns it off:

Panel::configureUsing(function (Panel $panel): void {
    if (! config('kitloom-redirects.filament.register', true)) {
        return;
    }

    $panel->plugin(RedirectsPlugin::make());
});

No WordPress is installed and none of its code runs. kitloom only takes the shape of its data, so a WordPress site can also move in with its content, URLs and users.

An AI agent runs the site, under your control

Each kitloom module brings tools for agents as well as screens for people. Claude, Cursor or your own agent connects to /mcp, calls describe_site, and works through the same code as the admin: create_content, upload_media, menu_save, seo_update, form_create, redirect_from_404.

You can ask it to "draft three posts from these notes and put them in the Guides category", or "which addresses gave 404 this week? Redirect the ones that have a new page".

It acts as the user whose key it holds, so an author's key writes drafts and a read-only key only reads. The settings that decide who gets in or what code runs on every page are locked. Nothing is deleted for good, every change is in the activity log, and revoking the key stops it at once. See Run your site from Claude or Cursor.

Try it

Open a Filament sandbox in one click, with no sign-up, and every module and theme is there. Look through the screens, then connect an agent from the dashboard and give it something to do. There is no free edition, but you get a 14-day refund: see Pricing.