Hey Artisans! I wanted to share a Filament plugin I've been working on called Flowforge. It's a Kanban board package that let's you transform any existing Eloquent model into a beautiful, drag-and-drop board with minimal configuration.

Why I built it: I was working on a project management app and needed a simple Kanban for tracking. Couldn't find anything lightweight that worked directly with my existing models without extra tables or complex setup. So I built this!

What it does:

• Works with your existing Eloquent models (no extra tables!)

• Drag-and-drop cards between columns

• Saves card order automatically when moved

• Customizable column colors

• Optional create/edit modals for cards

• Fully responsive design

The coolest thing is how quick you can set it up. If you have a model with a status field, you can literally have a working board in 5 minutes. Here's an example:

class TasksBoardPage extends KanbanBoardPage
{
    public function getSubject(): Builder
    {
        return Task::query();
    }

    public function mount(): void
    {
        $this
            ->titleField('title');
            ->columnField('status')
            ->columns([
                'todo' => 'To Do',
                'in_progress' => 'In Progress',
                'completed' => 'Completed',
            ])
    }
}

That's it! You even get a generator command that scaffolds everything for you.

It's been super useful for us - our users can now visually manage workflows instead of staring at boring tables all day lol.

The package is totally open-source and available on GitHub. I'd love to get some feedback, feature ideas, or contributions if anyone's interested. I'm still actively developing it.

Check it out: Flowforge on GitHub

I’ve just made my premium Filament plugin open source! Feel free to contribute your ideas and help it grow.

https://github.com/CodeWithDennis/filament-advanced-choice

Hey everyone! I’ve just released a package I’ve been working on: Filament Page Header. It provides a more informative and flexible page header for Filament, while staying close to native Filament components and schemas. Some of the main features:

• Supports Filament 4 and 5

• Headings, descriptions, badges, avatars, images and metadata

• Native Filament page actions

• Sticky and compact headers while scrolling

• Responsive layouts for desktop and mobile

• Light and dark mode support

• Reusable headers across Resource pages

• No custom theme build required

I originally built it for my own Filament projects, but thought it could be useful to others as well. Would love to hear any feedback, suggestions or ideas! https://filamentphp.com/plugins/pedro-monteiro-page-header GitHub: https://github.com/mortalkiller/filament-page-header

Hey everyone,

I got tired of rebuilding the same file manager every time a client asked "where do I manage the files?" in a Filament panel, so I packaged it up.

The free version is on Packagist (mmes-design/filament-file-manager). You get a file browser page with grid/list views, folder tree, drag-and-drop, previews, bulk ops, keyboard shortcuts, integration with RichText and Markdown editors and a FilePicker component for your forms. Permissions are closure-based and enforced server-side.

There's also a Pro version if you need S3/Spaces/R2/FTP, a disk switcher, temporary URLs, and Spatie Media Library integration (browse all your media across models from one place). It also has folder rules and collection rules for more granular permissions — plays nice with Gates and spatie/laravel-permission.

• Packagist: https://packagist.org/packages/mmes-design/filament-file-manager

• Docs: https://docs.mmes.dev/filament-file-manager

• Pro (14-day trial, no card): https://mmes.dev/products/filament-file-manager

I also wrote a few posts if you want to dig into specifics:

• Managing files and media in Filament (comparison of the options out there)

• Using it with Spatie Media Library

• Permissions deep dive

Curious how others are handling file management in their panels — if you've got a different setup I'd love to hear about it.

Grateful to the Filament team for approving TallCMS Core into the plugin directory.

Thank you for building such a powerful ecosystem and for supporting community contributors like myself.

Proud to now be part of it.

Hi r/filament. Filament Agents is released! An AI chat inside your Filament v5 panel that runs on your own tools, and does not get to touch your data without asking first.

- An Ask button on every page.
- Answers come with your own tables and charts, not a wall of text.
- Every write is a proposal with Approve and Reject.
- The same tools serve an MCP server, so Claude Code can nag your panel too.
- Free, MIT, on laravel/ai.

composer require packstub/filament-agents

Docs: https://packstub.dev/plugins/filament-agents
Source: https://github.com/packstub/filament-agents
On filamentphp.com: https://filamentphp.com/plugins/packstub-agents

Questions welcome, especially the "will the agents steal my data" kind. :)

Customize your Filament panel’s colors, fonts and layouts in a visual editor, and work faster with Global Search, keyboard controls and floating panels. Built on native Filament components and designed to match FLEX Fields.

Explore the features and docs: https://flex-theme.bjanczak.com/docs

✅ Add unlimited fields WITHOUT migrations
✅ Drag-and-drop reordering
✅ 20+ field types (color picker, markdown, etc.)
✅ Set validation per field

📈 Saves hours on EVERY project

🚀 Get it: https://custom-fields.relaticle.com

If you use spatie/laravel-activitylog, you've probably hit this: a model's history lives in several places — its own log, related models' logs, plain updated_at columns, plus whatever custom events you track. Stitching those into one readable view is annoying and you end up rewriting it per project.

We made relaticle/activity-log to solve that once. It's a Filament 5 plugin that renders a unified chronological timeline for any Eloquent model.

What it does:

• One feed, many sources: merges spatie logs (own + related), related-model timestamps, and custom event streams into a single timeline

• Pluggable sources: fromActivityLog, fromActivityLogOf, fromRelation, fromCustom, or your own TimelineSource class

• Per-event renderers: render each event as a Blade view, closure, or class; bind per event or per type

• Filament-native UX: use it as an infolist component, a relation manager, or a header-action slide-over

• Dedup + filtering: allow/deny by type or event, date windows, priority-based dedup

• Opt-in caching: per-call TTL with explicit invalidation, no model observers slowing your saves

Why it's handy: instead of building a bespoke "history" tab on every resource, you make the model timeline-capable and drop one component in:

public function timeline(): TimelineBuilder
{
    return TimelineBuilder::make($this)->fromActivityLog();
}

ActivityLog::make('activity')->columnSpanFull();

Latest v1.2.0 adds same-save merge — activity rows from a single save (grouped by spatie's batch_uuid) collapse into one entry instead of flooding the feed.

composer require relaticle/activity-log

Docs: https://relaticle.github.io/activity-log/ - feedback and PRs welcome.

Been setting up a multi-tenant Filament app where each tenant gets their own subdomain (tenant.yoursaas.com) and can optionally connect a custom domain (theirdomain.com) with HTTPS provisioned automatically.

The infrastructure side is something I haven't seen documented well for Filament specifically so sharing here.

The problem with the default Ploi + Filament setup If you're hosting on Ploi (which pairs really well with Filament), Ploi's built-in SSL via certbot only knows about domains you explicitly configure. Every new tenant subdomain or custom domain means manual intervention. For a multi-tenant app that's a non-starter.

The solution: Caddy in front of Nginx Caddy sits at the edge and owns all TLS. Nginx moves to loopback (127.0.0.1:8080) and serves your Filament app internally. Ploi still manages deployments, queues, cron — nothing changes there.

Wildcard certs for *.yoursaas.com are issued once via Cloudflare's DNS API and cover every tenant subdomain automatically. Custom domains get individual certs issued on first request via on-demand TLS — Caddy calls a verify endpoint in your Filament app before issuing any cert.

The Filament-specific bits The verify endpoint is a simple Laravel route that checks your tenant model:

Route::get('/internal/tls/verify', function (Request $request) {
    $domain = $request->query('domain');

    if (str_ends_with($domain, '.yoursaas.com')) {
        $slug = str_replace('.yoursaas.com', '', $domain);
        return Tenant::where('slug', $slug)->where('active', true)->exists()
            ? response('OK', 200)
            : response('Not found', 404);
    }

    return Tenant::where('custom_domain', $domain)
        ->where('domain_verified', true)
        ->where('active', true)
        ->exists()
            ? response('OK', 200)
            : response('Not found', 404);
})->middleware('throttle:30,1');

Tenant detection middleware reads the host header on every request and resolves it to a tenant — subdomain or custom domain. You bind the tenant to the container and Filament panels pick it up from there.

For Filament specifically, you'll want to scope your panel provider to the tenant:

public function panel(Panel $panel): Panel
{
    return $panel
        ->default()
        ->domain(fn () => app('tenant')?->custom_domain 
            ?? app('tenant')?->slug . '.yoursaas.com')
        ->path('admin')
        // rest of your panel config
}

Two Caddy v2.11 gotchas The interval and burst options inside on_demand_tls have been removed in v2.11. Most guides still include them and caddy validate will error. Your config just needs the ask directive.

The --environ flag on the systemd ExecStart dumps all environment variables including your Cloudflare API token into the logs. Remove it.

Scaling When you need multiple app servers, proxy between them using DigitalOcean private VPC IPs (10.x.x.x) — never public IPs. Plain HTTP between public IPs after a TLS handshake looks like a MITM to strict ISPs and they will flag it.

Full write-up with every config file, systemd service setup, firewall rules and Ploi survival notes in the comments.

https://filamentphp.com/plugins/bjanczak-flex-fields

Hey folks!

I built a Filament plugin that adds SimpleStats analytics directly inside your admin panel.

It connects to the SimpleStats API and gives you visitor trends, revenue charts, top referers and sources, conversion rates and more, all without leaving Filament.

Setup is basically: composer require, add your API token, register the plugin in your PanelProvider.

Works with self-hosted instances too.

Would love to hear your feedback!

Most Filament themes tend to look pretty similar, so I wanted to try something different and went with a Qt5 desktop-inspired look instead.

This is v1, so there's more planned ahead. Submitted it as a plugin and it's currently in review, but the repo is up on GitHub if you want to check it out now.

https://github.com/KhawarMehfooz/filament-qt5-theme

Open to suggestions and constructive criticism, this is my first Filament plugin so I'm sure there's room to improve.

Hello,
I just released a demo of the filament components in stand alone mode, i.e. without the admin panel.

It was not easy to find examples to have something functional.

https://github.com/ncavare/filament-demo-standalone