# Stagewright > Product walkthroughs, checked in every pull request. Stagewright records guides, videos and help articles from your running product, re-runs them on every PR, and asks you to approve what changed or files what broke. Before merge, not after the release. Stagewright is in private beta. The CLI is on npm (`npx stagewright init`, then `npx stagewright record`; no account needed). Every page below is Markdown; add `.md` to any page's address. ## Start here - [Stagewright: product walkthroughs, checked in every pull request](https://stagewright.ai/index.md): Stagewright records guides, videos and help articles from your running product, re-runs them on every pull request, and asks you to approve what changed or files what broke. Before merge, not after the release. - [Developers](https://stagewright.ai/developers.md): Walkthroughs as YAML in your repo, recorded with the CLI against localhost, checked in any CI, written by your coding agent through MCP and the Stagewright plugin. - [The method](https://stagewright.ai/method.md): The ideas Stagewright is built on: real over generated, walkthroughs as tests, approve or file, and honest numbers. - [Pricing](https://stagewright.ai/pricing.md): Stagewright is free to map and free to run in your own CI: runs on your machines and CI are unlimited on every plan. Paid plans are in private beta. Viewing is never metered. ## Guides - [Docs as code, for product walkthroughs](https://stagewright.ai/docs-as-code.md): Docs as code applied to product walkthroughs: walkthroughs as files in the repo, reviewed in pull requests, run in CI against the product, and published when a person approves the change. - [Record product walkthrough videos from your Playwright tests](https://stagewright.ai/guides/playwright-walkthrough-videos.md): How to record narrated product walkthrough videos from existing Playwright tests: Playwright's own video recording, the Stagewright fixture and reporter, importing a spec as a walkthrough, and running it in CI with a PR check. ## Problems - [Your help center is behind your last release](https://stagewright.ai/problems/help-center-behind-last-release.md): Why help-center screenshots, videos and articles fall behind the product after every release, what teams do about it today, and what it takes to catch it on the pull request instead. - [Stale articles are why your AI support agent answers wrong](https://stagewright.ai/problems/stale-articles-ai-support.md): Why AI support agents like Intercom Fin give wrong answers after a release, in support teams' own words, and how to keep the articles they answer from current with the product. ## Roles - [For engineering](https://stagewright.ai/for/engineering.md): For engineers: walkthroughs in YAML next to the code, a Walkthroughs check on every PR, regressions filed with video, fixes proven on the fix PR. - [For product teams](https://stagewright.ai/for/product.md): For heads of product and founders: every feature's walkthroughs, articles and support load in one place, checked on every pull request. - [For support and success](https://stagewright.ai/for/support.md): For support and success leads: help-center articles checked against the product, updated as drafts when the UI changes, and support load per feature. - [For customer education](https://stagewright.ai/for/training.md): For customer education teams: courses from checked walkthroughs, lapsing certificates, release training, SCORM and cmi5, per-locale recording, private hosting and enterprise CI. ## Comparisons - [Compare](https://stagewright.ai/compare.md): Honest, dated comparisons of Stagewright with Clueso, Guidde, Scribe, ScreenCI, Videate, Vidocu Pulse, LaunchBrightly and visual regression testing, and how it works with Promptless, Mintlify and Intercom Fin. Sourced from their own public pages. - [Stagewright vs Clueso](https://stagewright.ai/compare/clueso.md): Clueso re-records product videos after a pull request merges. Stagewright checks walkthroughs on the pull request before merge and files what broke. A dated, sourced comparison. - [Stagewright vs Guidde](https://stagewright.ai/compare/guidde.md): Guidde captures workflows into video documentation from a browser extension. Stagewright records walkthroughs from your running product and checks them on every pull request. A dated, sourced comparison. - [Stagewright with Intercom Fin](https://stagewright.ai/compare/intercom-fin.md): Fin Operator updates help-center text from a brief you give it. Stagewright checks the flows those articles describe on every pull request, supplies verified screenshots and video, and says which flows changed. How they fit together. - [Stagewright vs LaunchBrightly](https://stagewright.ai/compare/launchbrightly.md): LaunchBrightly keeps help-center screenshots current from outside your product, with visual audits and approvals. Stagewright records whole flows from your repo on every pull request. A dated, sourced comparison. - [Stagewright with Promptless or Mintlify](https://stagewright.ai/compare/promptless-mintlify.md): Promptless and Mintlify keep text docs current from your code changes. Stagewright runs the flows customers are taught, records them as video, and gives each pull request a verdict. How to use them together. - [Stagewright vs ScreenCI](https://stagewright.ai/compare/screenci.md): Both turn Playwright-style scripts into narrated product videos and run them in CI. The difference is what happens around the recording. A dated, sourced comparison. - [A Scribe alternative for customer-facing guides that stay current](https://stagewright.ai/compare/scribe-alternative.md): Scribe documents how your team works. If you publish step-by-step guides for your own product's customers, Stagewright re-records them from the product on every pull request. A dated, sourced comparison. - [Stagewright vs Videate](https://stagewright.ai/compare/videate.md): Videate re-renders product videos when someone hits refresh or a scheduled batch runs. Stagewright checks walkthroughs on every pull request, before merge. A dated, sourced comparison. - [Stagewright vs Vidocu Pulse](https://stagewright.ai/compare/vidocu-pulse.md): Vidocu Pulse scans your help center against your code and live app on a schedule and drafts fixes. Stagewright checks walkthroughs on every pull request. A dated, sourced comparison, including where Vidocu's own pages disagree. - [Stagewright and visual regression testing (Chromatic, Percy)](https://stagewright.ai/compare/visual-regression-testing.md): Isn't this just Chromatic? Visual testing checks your UI for QA. Stagewright checks the walkthroughs customers watch and read, and publishes them. How they differ and how they fit together. ## Everything else - [Changelog](https://stagewright.ai/changelog.md): What's new in Stagewright: shipped work, newest first. - [Integrations](https://stagewright.ai/integrations.md): GitHub, GitLab, Azure DevOps, Bitbucket, Linear, Jira, Intercom, Zendesk, Productlane, PostHog and Segment: what Stagewright reads from each and what it writes back. - [When Stagewright isn't the right tool](https://stagewright.ai/not-for.md): What Stagewright doesn't do: AI avatars, HTML-clone interactive demos, editing uploaded video, click-to-capture browser extensions, native mobile apps, or products with no environment a browser can drive. - [Privacy](https://stagewright.ai/privacy.md): How Stagewright handles data: events describe features, not people. No keystrokes, no form values, no session replay. - [Security and data](https://stagewright.ai/security.md): Stagewright security and data handling: Cloudflare Workers, Neon Postgres with row-level security, R2 and Clerk; recordings on your machine, in your CI or on a runner inside your network; encrypted secrets; no SOC 2 yet. - [Couldn't we just build this with Claude?](https://stagewright.ai/why-stagewright.md): Any team with a coding agent can script Playwright, ffmpeg and a voice API in an afternoon. What that doesn't produce: history, joined data per feature, maintained integrations, checks people trust, and hosting with proof.