Packstub
Free & open source Public beta packstub/filament-session-replay

Filament Session Replay

Session replay inside your Filament panel. Register the plugin and the panel's pages are recorded; every recording lands in a filterable Sessions resource and plays in the panel with errors, failed Livewire requests and web vitals on the timeline — next to the person, the workspace and the panel's own permissions, on your own disk and database.

Install for free Read the docs Free MIT license
Filament Session Replay screenshot
Fig. 01 — Filament Session Replay

Features

What’s included

  • The panel recorded without a directive, with the panel's own guard, the current workspace, the panel id and the impersonator signed into each recording
  • A Sessions resource with filters for errors, slow pages and rage clicks, and a watch page with the player, a marker list that seeks on click, Pin, Export and Delete
  • A Session replays tab and a "Watch last session" action for your users, a maskInReplay() macro on fields, columns and entries, and one viewSessionReplay gate that Filament Shield can take over

Install

One command, from Packagist

No accounts, no tokens. This package is free and open source — it installs straight from Packagist like any other Composer package. It’s in public beta until 1.0, so the command asks Composer for the latest beta.

install — bash
$ composer require "packstub/filament-session-replay:^1.0@beta" "packstub/session-replay:^1.0@beta"

What you get

Free, and maintained like everything else we ship.

Is it really free? +

Yes — MIT licensed, free forever, for any kind of project. We build our own plugins with it, and sharing it makes the whole ecosystem better.

How do I install it? +

Run the Composer command above. It installs from Packagist like any other package — no Packstub account needed.

Can I use it in commercial projects? +

Absolutely. The MIT license covers personal, client, and commercial use without restrictions.

Where do I report bugs or request features? +

On the GitHub repository — issues and pull requests are both very welcome.

How does this relate to your paid plugins? +

Same team, same standards. Free tools like this one are part of how we build our commercial plugins, so they get maintained with the same care.