Guidance is easy to demo.
It's hard to keep true.
Every team knows the ritual: someone new starts, and someone experienced walks them through it — again. The tools that promise to fix this mostly bolt a tour on from outside: a browser extension, a third-party script, a recorded overlay that breaks the first time the interface changes and nobody notices for months.
Splain adds in-app, code-anchored walkthroughs to Laravel (the PHP web framework) and its Filament admin panels (the admin-panel framework for Laravel) — guidance that can't silently go out of date.
Splain was built on a different bet: guidance belongs inside the app, anchored to the code, and the build should fail when the two drift apart. A guide's steps name real elements with exact selectors. A checker replays every guide against every page before anything ships. If a refactor deletes an anchor a guide depends on, your CI (the automated checks that run before you merge code) goes red — the walkthrough can't silently rot into a lie.
The proving ground
Splain has been a standalone package from day one — and it grew up against a live staffing platform we build and run ourselves, with real workflows, real privacy stakes, and real users. That environment set the bar for everything on this site:
- Walkthroughs had to survive modals, confirmation dialogs, dropdown menus, failed validations, and multi-page journeys — because the real workflows used all of them.
- Privacy Mode masks real records on screen while you record a tutorial — honestly scoped as a presentation aid, not a security guarantee, because calling it more would be a lie.
- Before a guide can be published, Splain requires a named person to sign off that it reflects how the work is really done. Staff aren't added by clicking "New" — they arrive through hiring; a guide that says otherwise is worse than no guide. The interface allowing an action is not the same as that being the workflow.
The recursion
The dot in the corner of this page is the real playback engine — the actual Splain player that ships in the product, not a mockup. Click it. The docs on this site tour themselves, too. We couldn't help it, and it keeps us honest: if the product can't explain itself, why would you trust it to explain yours?
The rule that governs everything
That's also why this site is short on adjectives and long on receipts. Splain isn't revolutionary — in-app guidance is a proven category. It's a different set of trade-offs: self-hosted instead of SaaS, code-anchored instead of fragile, built-in instead of bolted on, honest instead of shiny.