Early Access

Documentation that keeps up

Your product changes every day. Your documentation does not. Vidocu Pulse watches both, works out which articles the change just broke, rewrites them, and recaptures the screenshots and the video from your live product.

Request a demo

Trusted by 20,000+ fast-moving teams

How It Works

Four steps, and you only do the reviewing

Pulse runs the loop that keeping documentation current has always required: notice, rewrite, recapture, publish. You decide what ships.

1
Connect what you already have
A GitHub repository, your live product, your marketing site, and the knowledge base you publish today. All read-only, and you can start with as little as the product itself.
2
Pulse notices what changed
Each scan compares what the product actually does with what your documentation says about it, and returns a list: the articles to write, the ones to update, and the ones nothing supports any more.
3
It writes the update, with evidence
One click turns a finding into a draft that cites the code behind it. Vidocu then signs in to your product, walks the flow the article describes, and captures the screenshots fresh.
4
Your knowledge base stays in sync
Review the draft, then push it to the Vidocu Knowledge Center or to Zendesk, Intercom, Notion, Help Scout, Freshdesk, or GitBook. Article, screenshots, and video move together.

Request a demo

Key Capabilities

What Pulse does between your releases

Pulse is not a writing assistant waiting for a prompt. It is the part of documentation work nobody has time for: checking every article against the product, and doing something about the ones that no longer hold.

It reads the product, not just the docs

Pulse connects to your repository and walks your signed-in app. What the code does is treated as the truth; your marketing copy is only context. That is the difference between finding real gaps and rephrasing what you already published.

It proposes the help center you should have

Instead of one long list of suggestions, Pulse lays out sections and the articles that belong in them, named the way your own navigation names them, and shows you what is missing from that picture.

Drafts grounded in code, not guesses

Every draft cites the files it was written from, at a specific commit. When the evidence is thin, Pulse says so in the draft rather than inventing a button that does not exist.

Screenshots taken from your live product

Pulse opens your app with a saved session, navigates to the screen the article is about, and photographs it. Dynamic pages and screens behind a tab or a dialog included.

Turn a draft into a fresh video

Hand any draft to the AI Recorder and it performs the updated flow and records it. The article, the screenshots, and the walkthrough video all describe the same current version.

Runs on your schedule

Scan daily, weekly, or monthly, at an hour and time zone you choose, so the gap list is waiting for you rather than something you remember to go and look for.

It tells you when it could not do the job

No screenshots because the connected account has no data, a flow it could not reach, a fact it could not verify: each one arrives as a warning on the draft with a link to the fix, never buried in the article.

Nothing publishes without you

Every finding, draft, and screenshot waits for a human. Pulse does the work that made updating docs expensive; the decision to publish stays yours.

See Pulse run on your product

Request a demo

Who is it for

For every team that owns docs nobody has time to maintain

Documentation

Stop auditing the help center by hand

The quarterly read-through that never quite happens becomes a list that arrives on its own, with the drafts already written.

Product

Ship a feature and the docs follow

The release that changed the settings screen also changes the article about it, in the same week rather than the next quarter.

Support

Fewer tickets caused by your own docs

Screenshots that match the current interface remove a whole category of confused ticket before it is filed.

Engineering

Docs that follow the commit, not a reminder

Connect the repository once. Nobody has to remember to file a documentation task alongside the pull request.

What Makes This Different

Don't maintain your help center.
Let it maintain itself.

Documentation does not go stale because people are careless. It goes stale because noticing, rewriting, and re-screenshotting is a week of work nobody has after a release.

The job	With Vidocu Pulse	Keeping docs current by hand
Noticing a change broke an article	Every scan, automatically	Someone has to remember
What the update is based on	Your code and your live app	Whoever wrote the ticket
Writing the revision	Drafted with sources cited	Hours per article
New screenshots	Recaptured from the real screen	Manual, and usually skipped
The walkthrough video	Re-recorded by the AI Recorder	Left stale indefinitely
Where it publishes	Vidocu KB, Zendesk, Intercom, Notion and more	Copy and paste
Coverage gaps you never spotted	Listed as articles to write	Invisible until a ticket arrives
Keeping it running	A schedule you set once	A recurring calendar invite

One change. The article, the screenshots and the video.

4 Sources

Code, app, site and help center

Every scan

Gaps found without being asked

Live screens

Screenshots from your real product

You approve

Nothing publishes on its own

Save hours, reduce repetitive work, create more formats, and localize content for global audiences.

Frequently Asked Questions

What is Vidocu Pulse?

Pulse is a documentation health engine. It connects to your product, your code, and the knowledge base you publish today, then works out which articles no longer match reality. It writes the updates, captures fresh screenshots from your live app, and can re-record the walkthrough video, so your documentation keeps up with the product instead of falling a release behind.

How does Pulse know my documentation is out of date?

It scans up to four sources and compares them: your repository through a read-only GitHub App, your signed-in product walked screen by screen, your marketing site, and your existing help center. Code and the live app are treated as the truth. When the product does something your articles do not describe, or describes something the product no longer does, that becomes a finding.

Does Pulse publish changes without asking me?

No. Pulse produces findings and drafts; a person reviews and publishes them. That is deliberate: the expensive part of keeping documentation current is noticing what changed and rewriting it, not clicking publish.

Do I have to connect my source code?

No. The app adapter walks your signed-in product and needs no repository at all, which is what makes Pulse usable on products whose code we cannot read. Connecting a repository makes the drafts stronger, because the writer can cite the code behind a behaviour rather than infer it from the screen.

Where does the updated content end up?

Vidocu's own Knowledge Center, or your existing help center: Zendesk, Intercom, Notion, Help Scout, Freshdesk, and GitBook are supported destinations. You keep publishing where your readers already are.

How are the screenshots taken?

Pulse signs in to your product with a saved session and navigates to the screen the article describes, including screens that only exist behind a tab, a dialog, or a dynamic URL. It photographs the page once it has actually finished rendering. If the connected account has no data to show, Pulse says so on the draft rather than publishing a picture of an empty list.

Can Pulse update videos too?

Yes. Any draft can be handed to Vidocu's AI Recorder, which performs the updated flow in a real browser and records it. You get a current article, current screenshots, and a current video from the same change.

How do I get Pulse?

Pulse is in early access. It is switched on per workspace by our team rather than bought from the pricing page, so the way in is a demo: we look at your product and your help center together and turn it on for you if it is a fit.

Early access

Your help center, maintained by your product

We will run Pulse against your product and your documentation, and show you the gap list it comes back with.

Request a demo

Turn raw into ready

Your knowledge is valuable. Make it usable.

Upload once. Use everywhere.

Get a demo See it in action

The AI Knowledge Platform. One upload becomes videos, SOPs, guides, articles, and training - in any language.

5.0 on Trustpilot (3 reviews)

AI Recorder

Pulse

AI Subtitles

AI Voiceover

Video Translation

AI Avatars

Knowledge Center

Remix

Studio

Video Editor

Zoom & Pan

Elements & Annotations

Background Music

Presentation Slides

Watermark

Course Builder

Training Center

API

Video to Documentation

Video to SOP

Help Article Generator

AI Knowledge Base Generator

AI Video Documentation

Video to Blog Post

Video Translation

AI Subtitles Generator

Loom to Documentation

Webinar to Knowledge Base

ServiceNow

Salesforce

SAP

Microsoft 365

All platforms

Documentation that keeps up

Four steps, and you only do the reviewing

Connect what you already have

Pulse notices what changed

It writes the update, with evidence

Your knowledge base stays in sync

What Pulse does between your releases

It reads the product, not just the docs

It proposes the help center you should have

Drafts grounded in code, not guesses

Screenshots taken from your live product

Turn a draft into a fresh video

Runs on your schedule

It tells you when it could not do the job

Nothing publishes without you

For every team that owns docs nobody has time to maintain

Stop auditing the help center by hand

Ship a feature and the docs follow

Fewer tickets caused by your own docs

Docs that follow the commit, not a reminder

Don't maintain your help center.Let it maintain itself.

One change. The article, the screenshots and the video.

Frequently Asked Questions

Your help center, maintained by your product

Your knowledge is valuable. Make it usable.

Don't maintain your help center.
Let it maintain itself.