letmesplain
proving-ground

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 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 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 deliberately hard test bed: a live staffing platform with real workflows, real privacy stakes, and real users. That environment set the bar for everything on this site:

A Splain walkthrough playing inside a real Filament admin panel: the page is dimmed, a table of widgets is spotlit, and a popover titled 'Your widget list' explains it.
The real thing: a guide spotlighting a table inside a genuine Filament panel — this screenshot comes from the package's own test workbench, which CI drives end-to-end on every push.

The recursion

Splain's own Studio ships with a Splain tour of itself. The docs on this site tour themselves. The dot in the corner of this page is the real playback engine, running the shipped free-tier bundle. 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

The software never claims more than it does. In the product, in the docs, and on this site: limits are stated out loud, unproven things are labeled planned, and "it works" always means "there is a test that proves it."

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.

Back to the tour Read the manual