**For customer education and training** # Every release ships with its training already updated. For SaaS vendors that train thousands of customer users: courses built from walkthroughs that are re-recorded and checked on every release, certificates that lapse when the product changes, and packages for your LMS. ## Courses as code A course puts walkthroughs in teaching order, in one file per course: sections, learning paths per role, knowledge checks, completion rules and certificates. Lessons play the latest approved recording, so a course never shows last quarter's UI. - Knowledge checks are drafted from the walkthrough and hidden from learners until a person approves them. - Learners sign in from your app with a short-lived signed token, or by invite. \[Illustration\] A course file for Acme CRM basics: visibility for learners, completion at 90% watched with checks required, a certificate valid 365 days that lapses on change, an admins learning path, and lessons with a knowledge check. ## When the product changes, the training says so When an approved UI change to a lesson publishes, that course's certificates need a refresh and learners see a short "What changed" view of just the changed lessons. Release training drafts "What changed in this release" from the UI changes approved between two versions, each clipped to the changed steps. - SCORM 1.2, SCORM 2004 (4th edition) and cmi5 packages per course. They stream the current recording, so the package in your LMS doesn't go stale. - Each language recorded from the product running in that language, checked on the PR, with untranslated strings and cut-off labels noted. A person approves each locale's translation before it publishes. \[Illustration\] The public player for “Invite a teammate” (Acme CRM): the recorded video with chapters and captions, and the stamp “Recorded from build a1b2c3d · verified 3h ago”. ## Fits an enterprise release process Checks run in GitHub, GitLab (including self-managed), Azure DevOps (Services and Server) and Bitbucket Cloud. For staging that only your network reaches, run Stagewright's recorder container inside it: it opens no ports and only calls out over HTTPS. Videos can be public, private or password-protected, and served from your own domain. \[Illustration\] How a pull request is judged: Unchanged passes. UI changed or new waits for approval. A failure that repeats where the PR touched the walkthrough's anchors asks for the walkthrough to be updated; one that repeats where it didn't is a regression, filed as an issue. A failure that doesn't repeat is flaky and never blocks. Walkthroughs the change can't affect are skipped. ## Not there yet We'd rather you hear it here than in a security review. - SCIM provisioning. SAML single sign-on and audit-log export are on the Scale plan. - SOC 2. We're keeping practices audit-ready and will start the process when a customer needs it. - Data residency choice. The database is in the US today; a runner you host keeps the browser on your network, but recordings are uploaded to Stagewright. - Jira Data Center and Bitbucket Data Center. Jira Cloud and Bitbucket Cloud are supported. - Help-center articles per locale. Translated videos and articles are served from the player; help-center publishing is in the source language. - Recording by clicking through the app, and desktop or mobile apps. ## Try it on your own product Record a first walkthrough on your machine with no account. PR checks, approvals and publishing are in private beta: join the waitlist and we'll set you up by hand. npx stagewright init [Join the waitlist](https://app.stagewright.ai/?waitlist)[Developer docs](https://stagewright.ai/developers)