# supportvid.io

> supportvid connects to a GitHub repository once. On every new release, autonomous agents read the release, changelog and diff, regenerate the user documentation, and record a fresh narrated tutorial video: a pipeline designed to keep docs and videos current with each release. Teams can join the waitlist at supportvid.io.

## What supportvid does

- Watches the releases and changelogs of a connected GitHub repository
- On every tagged release, agents read the diff and understand the new behavior
- Regenerates the user documentation to match the version that actually shipped
- Records a fresh narrated tutorial walkthrough video per release
- Tags docs and videos per release, so older versions stay browsable
- Aims to publish through a hosted docs portal or an embed in your own site
- Is designed around your review: you approve updates before they publish, with hands-off publishing planned for teams that want it

## Who it is for

Teams who ship on GitHub, from indie developers to platform teams drowning in documentation debt. The workflow is designed for public and private repositories, authorized through GitHub with read access that you can revoke at any time.

## Status

- Teams are onboarded from the waitlist in small batches.
- Join the waitlist at https://supportvid.io/ - one email when your spot opens, no spam.
- Pricing has not been published yet. It will be announced at launch.

## Pages

- [Home](https://supportvid.io/): Product overview, how it works, and the waitlist signup.
- [Blog](https://supportvid.io/blog): Practical writing on user documentation, help centers, release workflows, and tutorial videos for teams that ship on GitHub.
- [For AI assistants](https://supportvid.io/ai): Verified product facts for AI assistants, with guidance on what not to claim.
- [Privacy](https://supportvid.io/privacy): Privacy policy: one email address, one launch notification, never shared.

## Blog posts

- [How to keep user documentation up to date after every product release](https://supportvid.io/blog/keep-user-documentation-up-to-date): Documentation drifts every time you ship. A release-triggered workflow for keeping user docs accurate: impact checks, clear ownership, verification, and automation.
- [Help center documentation best practices for teams that ship on GitHub](https://supportvid.io/blog/help-center-documentation-github-teams): Docs-as-code practices for GitHub teams: keep help content in the repo, review it in pull requests, tie updates to release tags, and automate freshness checks.
- [When tutorial videos help users, and when they are unnecessary](https://supportvid.io/blog/tutorial-videos-when-they-help): Tutorial videos shine for multi-step workflows and onboarding, and waste effort as reference material. A practical checklist, plus the stale video problem.
- [Release notes vs user documentation: what each one is for](https://supportvid.io/blog/release-notes-vs-user-documentation): Release notes announce what changed. User documentation explains the product as it is today. What belongs in each, how they link, and how to keep both in sync.
- [Creating user guides for SaaS products: a practical playbook](https://supportvid.io/blog/creating-user-guides-for-saas-products): How to write SaaS user guides people can actually follow: task-based structure, a reusable page template, writing rules, media choices, and a plan for staleness.

## Machine-readable resources

- https://supportvid.io/llms-full.txt: The same summary plus the full text of every blog post
- https://supportvid.io/ai.txt: Plain-text facts and usage guidance for AI assistants
- https://supportvid.io/ai-full.txt: Extended plain-text version: facts, key pages, blog topics, and Q&A
- https://supportvid.io/ai.json: Structured product facts as JSON
- https://supportvid.io/answers.json: Canonical question and answer pairs as JSON
- https://supportvid.io/.well-known/ai-site.json: Machine-discoverable index of all AI resources on this site