Stagewright vs Vidocu Pulse

What Vidocu Pulse is, in its own words

Vidocu’s launch post, dated September 18, 2026: “Today we are opening early access to Vidocu Pulse: a documentation health engine that watches your product and your code, works out which help articles a change just broke, rewrites them, and recaptures the screenshots and the video from your live app. You review what it found and decide what publishes. Nothing goes live on its own.” Pulse reads up to four sources, all read-only: code through a GitHub App, the live product “walked screen by screen with a saved login session,” the marketing site, and the existing help center. “There is no autopilot mode that pushes to your live help center unattended, and we are not planning one.”

Vidocu is candid about the trade-offs. In its own roundup of self-updating documentation tools: “Scans run on a schedule, not on every merged pull request, so Ferndesk, Mintlify and Promptless react faster to a single PR. Video takes a click rather than happening automatically. It is for web products only, and it needs an account with real data to walk.”

How they differ

When. Pulse finds drift after it reaches the product, at the next scheduled scan. Stagewright runs the affected walkthroughs on the pull request, so the person who changed the flow sees the change in their review, with frames, before it merges.

What gets checked. Pulse reads your whole help center and compares it with your code and live app, including articles that no recording covers. Stagewright checks flows by running them: an article is only checked if a walkthrough covers its feature, and the rest are marked not checked.

What a broken flow becomes. Pulse reports a flow it couldn’t reach as a warning on the draft. Stagewright records the failure a second time, and if it repeats, files it in your issue tracker with the clip, assigned to the PR’s author, and replays the fix PR to prove it.

Side by side

Finding what's out of date

Finding what's out of date: Stagewright and Vidocu Pulse
Capability	Stagewright	Vidocu Pulse	Source
When it checks	Every pull request the change can affect, before merge	"Scan daily, weekly, or monthly, at an hour and time zone you choose", or on demand	source
What it compares	A recording of each walkthrough against its approved baseline; articles mapped to the walkthrough's feature	Code, the live app, the marketing site and the help center; "Code and the live app are treated as the truth"	source
Articles nothing records	Partial. Marked ○ not checked until a walkthrough covers the feature	Yes. Each scan compares the whole help center with the product	source
Works without a repository	No	Yes. "This source needs no repository at all"	source
Check on the PR with before and after frames	Yes	No. "Scans run on a schedule, not on every merged pull request" (Vidocu’s own words)	source
When it can't check something	The run fails at the step, with the frame; a failure that repeats is a regression, one that doesn't is flaky	Warnings on the draft ("a flow it could not reach, a label it could not verify") with a link to the fix	source
Broken flows filed to an issue tracker with video	Linear, Jira Cloud, GitHub Issues	No. Not documented, per their public docs as of October 2026	source

Last verified 2026-10-11 against Vidocu Pulse's public pages, linked in each row.

Updating and publishing

Updating and publishing: Stagewright and Vidocu Pulse
Capability	Stagewright	Vidocu Pulse	Source
A person decides what publishes	Approval in the PR or in Stagewright; articles go back as drafts by default	"Every finding, every draft, and every screenshot waits for a person"	source
Drafts say what they were written from	Yes. "written from src/invites/** and 9 tickets"	Yes. "The draft cites the files it was written from, at a specific commit"	source
Video after a change	Re-recorded on the PR; publishes when approved	One click hands a draft to the AI Recorder (Beta). "Video takes a click rather than happening automatically" (Vidocu’s own words)	source
Help-center destinations	Productlane, Intercom, Zendesk	Vidocu Knowledge Center, Zendesk, Intercom, Notion, Help Scout, Freshdesk, GitBook	source
Output formats	MP4, GIF, step screenshots, PDF guide, Markdown article, quick clips	"8 distinct formats from single source", including SOPs, help articles and quizzes	source
Languages	Each locale recorded and checked on the PR	70+	source
Platforms	Web apps, in Chromium	"It works on web products."	source
SSO, SOC 2	No. Not yet	"SOC 2® examined"; SSO on Enterprise	source
Price of Pulse	Not priced yet (private beta)	Three different answers on Vidocu's own pages (below)	source

Last verified 2026-10-11 against Vidocu Pulse's public pages, linked in each row.

Pulse’s price and availability: Vidocu’s pages disagree

We found three statements on vidocu.ai, checked on 2026-10-11:

The launch post: “Pulse is in early access. It is switched on per workspace by our team rather than bought from the pricing page…”
The roundup post: “Early access. Pulse is an add-on for paid Vidocu plans and is set up with you on a demo; no public price yet.”
The Pulse feature page: “Sign up and open Pulse from the sidebar. It is available on every plan, including the free one, and it runs on your workspace credits…”

The feature page reads like the newest of the three, but we can’t tell. Vidocu’s base plans, per its llms.txt, are Free, Pro at $39 a month, Business at $149 a month and Enterprise. Ask Vidocu before you rely on any of them.

Where Vidocu Pulse is better

Coverage of the whole help center. It audits every article, not just the ones a walkthrough covers.
No repository needed. Pulse can walk the live app with a saved login. Stagewright starts from your repo.
Breadth. Eight output formats, 70+ languages, seven publishing destinations, and SOC 2.
Self-serve plans with published prices.

Choose Vidocu Pulse if

Your help center is large and mostly not covered by any recording, and a daily or weekly audit is soon enough.
The people who own the docs don’t work in the repository.

Choose Stagewright if

You want drift caught on the pull request, before merge, by the engineer who caused it.
A flow that broke should be filed as a regression with video, not left as a warning on a draft.
You want walkthroughs as files in the repo, recorded on a laptop or in any CI.

Using both

They can work side by side: Pulse’s scheduled audit across the whole help center, and Stagewright’s PR check for the handful of flows customers are taught most.

FAQ

Does Pulse run on pull requests? No, per Vidocu’s own roundup: “Scans run on a schedule, not on every merged pull request.”

Does Pulse re-record video automatically? Per Vidocu, “Video takes a click rather than happening automatically”: a draft is handed to the AI Recorder, which is in beta.