Skip to content
Vidabug
Sign inStart a project
Two services · one private cloud machine

Your software, explained on video. Its bugs, fixed with proof.

Vidabug does two things for software teams. It films narrated explainer videos of your software, one short video per task, with captions, transcripts and step guides. And from your source code, it finds the bugs a new user meets, repairs and tests them, and commits each fix to a separate branch in your own repository, with before and after proof. You decide whether to merge.

Start a project See the packages

Choose a package now, or connect your software first and get a package recommended once it has been analysed.

01 Videos

Narrated explainer videos of your software

One short video per task, in your brand, with captions, a transcript and a step guide.

  • MP4, up to 4K
  • Captions & transcript
  • PDF & Word guides
  • Your logo & colours
02 Bug fixes

The bugs a new user meets, fixed with proof

Met as a new user meets it, then repaired, retested and committed to a branch you own.

  • Screenshot & steps
  • Root cause & repair
  • Tests that prove it
  • Pull request & report

Illustrations of the two services, not customer recordings.

Bring any project

Live website, GitHub, any Git host or a ZIP. Vidabug starts from what you have.

What each one lets Vidabug do
01 · Service one · Videos

Narrated videos of your software. One for every task.

An onboarding library for your customers and your staff: short narrated explainers of your own software, with captions, transcripts and step guides, in your brand, and re-filmed as your software changes.

What you give

Two ways in
No code accessFrom your live app and its manual
  • The address of your running, hosted software
  • A test login for a test account
  • Your user manual, as PDF, Word or Markdown
OrFrom your source code
  • A repository on GitHub, GitLab, Azure DevOps, Bitbucket or any Git host
  • Or a ZIP of the source

Plus your logo, colours, intro and outro text, and the chapters, shape, length and narrator voice you want.

What you get

  • A library of short explainers, one per task, in the order a new user meets them
  • Natural narrator voices, camera work, zoom and annotations
  • Burned-in subtitles, a captions file and an interactive transcript
  • Step-by-step guides as PDF and Word, for people who prefer reading
  • Your brand: logo, colours, intro and outro on every video
  • Any shape: 16:9, 9:16, 1:1 or 4:5, up to 4K
  • Re-filmed on a schedule as your software changes
Onboarding library6 explainers · captions · guides
  1. Sign in for the first time0:42 · CC · Guide
  2. Create a purchase order0:51 · CC · Guide
  3. Approve an order0:47 · CC · Guide
  4. Send it to the supplier0:38 · CC · Guide
  5. Run the monthly report0:55 · CC · Guide
  6. Invite your team0:33 · CC · Guide
Illustration of a library. Each explainer comes with its transcript, captions file and step guide.
Start a video project See the packagesChoose a package, or connect your software first and get a package recommended once it has been analysed.
02 · Service two · Bug fixes

The bugs your users meet. Repaired, and proven.

From your source code, Vidabug installs your app in a private cloud machine and uses it like a new user. Each defect it meets in the flows you choose is documented and traced to its root cause; the ones within scope are repaired, retested and filmed again, then committed to a separate repair branch in your repository with before and after proof. Your original branch stays unchanged; you decide whether to merge.

What it covers, and what it does not. Vidabug tests the features and journeys in your plan, the way a user meets them, and fixes what it can prove and retest. It can miss defects, it does not certify an app as bug-free, and it is not a penetration test or a load test. Problems outside your code (hosting, third-party services, data) are reported, not changed. Every repair is a proposal: run your own tests on the branch before you merge.

  1. Found
  2. Documented
  3. Root cause
  4. Repaired
  5. Tested
  6. Filmed again
  7. Pull request
HIGHD-01 · CHECKOUT · EXAMPLEThe order total ignored the discount code✓ Repair verified
Total120.00SAVE10 accepted
Total108.00SAVE10 applied: 10% off
BEFOREAFTER 
src/cart.js@@ -10,6 +10,7 @@ export function total(cart, code) {-  return applyDiscount(sum, code) && sum;+  const discounted = applyDiscount(sum, code);+  return Math.round(discounted * 100) / 100;
Root cause
The total was computed before the discount was applied.
How it was proven
The new test fails without the fix and passes with it; the final take shows 108.00.

What you give

  • A repository on GitHub, GitLab, Azure DevOps, Bitbucket or any Git host
  • Or a ZIP of the source: it is scanned for malware before anything opens it
  • The areas to explore, as chapters you choose
  • Access you can revoke at any moment

What you get

  • Every defect documented, with a screenshot and the steps to reproduce it
  • The root cause, found in the code, in plain words
  • The repair, with a test that fails without it and passes with it
  • Before and after proof: the repaired screen, filmed again
  • A pull request on its own branch, with every fix listed for you to review
  • The report, as PDF and Word, with the cost of every verified repair
Start a bug-fix project See the packagesChoose a package, or connect your software first and get a package recommended once it has been analysed. Your main branch is never touched; failed attempts are counted honestly, and anything that could not be verified is reported as such.

Stacks Vidabug runs and tests. Source code in these languages and frameworks, or any web app already running: Vidabug installs it, films it and repairs what it can prove. An unusual setup is checked when your project is analysed, before you pay.

  • Python
  • JavaScript
  • TypeScript
  • Java
  • Kotlin
  • C#
  • Go
  • Rust
  • PHP
  • Ruby
  • Dart
  • React
  • Next.js
  • Vue
  • Nuxt
  • Angular
  • Svelte
  • Flutter web
  • Django
  • Flask
  • FastAPI
  • Express
  • NestJS
  • Spring Boot
  • ASP.NET Core
  • Laravel
  • Ruby on Rails
  • PostgreSQL
  • MySQL
  • SQLite
  • MongoDB
  • Redis
  • Playwright
  • Cypress
  • Pytest
  • Any hosted web app: SaaS, CRM, ERP, portals, admin tools

Logos are trademarks of their owners, shown to indicate compatibility; no endorsement is implied.

03 · Why the demand is exploding

Software got powerful. Learning it got harder.

Three forces are turning onboarding from a nice-to-have into a budget line that customer success, support, operations and L&D now own.

Industry estimate

14 days

Complex B2B software is everywhere

Custom CRMs, ERPs, telematics dashboards and logistics systems are dense with features. Industry estimates put the window in which a new customer is won or lost at the first 14 days, their time to value. Documentation is too dense to read in that window. Video gets users activated.

Customer success · Product
Industry estimate

$15–30 a ticket

The shadow cost of support

Industry estimates put a tier-1 ticket at roughly $15–$30 for an enterprise to resolve by hand. Most of them are the same few questions, asked again every month, by a new set of users.

Support · Customer success
Where the hours go

100s of hours

Internal operational enablement

Rolling out proprietary workflows for warehouse management, field operations or auditing can consume hundreds of senior management hours training new staff. Short video modules standardise that training at once.

Operations · L&D
04 · The shadow cost

The same 200 questions. Every month.

$36,000–$72,000a year, spent answering 200 recurring tier-1 questions a month by hand, at industry estimates of $15–$30 a ticket.

Answer them once, on video, and the maths turns around. If a library of 10 micro-explainers resolves 200 recurring questions a month, it pays for itself in less than a quarter, and keeps paying every month after.

Run your own numbers
200 tier-1 tickets this monthOne square is one ticket
120 answered by a short video80 still need a personIllustration at a 60% share. Your share goes in the calculator.
05 · The reframe

Not video tutorials. An onboarding library.

We don’t make video tutorials. We cut churn and tier-1 support tickets by building interactive onboarding libraries for B2B platforms, and we fix the bugs we meet on the way.

Call it “video tutorials” and it competes with freelancers at $50 a video. Build it as a library and it is measured against your ticket queue, your activation rate and your training calendar.

A one-off freelance tutorial compared with a Vidabug onboarding library
What is comparedA one-off freelance tutorial typicallyA Vidabug onboarding library every engagement
What you getOne videoA library of short explainers, one per task, with the report and step guides
When the software changesOut of date at the next releaseRe-filmed on a schedule, or when the repository changes, so it stays current
Captions and transcriptExtra, if at allBurned-in subtitles, a captions file and an interactive transcript
For people who prefer readingNot includedStep-by-step guides as PDF and Word
Your brandDepends on the briefYour logo, colours, intro and outro on every explainer
A defect on screenFilmed around, or re-recorded by handFrom source code: found, fixed and proven, with tests and a pull request
While it is madeWait for the fileA live view of every production, stage by stage
The commercial modelPriced per video, onceA monthly or annual package that keeps the library current
06 · Where it fits

Built for software that is hard to learn.

Wherever a screen has to be explained more than once, a library explains it for good.

B2B SaaS customer onboarding

Get every new account to its first result inside the first 14 days, without booking a call. One short explainer per task, in the order a new customer meets them.

Aimed at activation and churn

ERP and CRM roll-outs

Every module and every role, explained on the configuration your people actually use.

Aimed at adoption

Telematics and logistics dashboards

Dense screens of maps, alerts and reports, broken into one-question answers.

Aimed at ticket deflection

Warehouse and field operations

The same training for every shift and site, in 9:16 for the phone in their pocket.

Aimed at training time

Audit and compliance software

The exact steps, with a transcript and a step guide you can keep as a training record.

Aimed at audit readiness

Internal tools and change management

When a process changes, the explainer is re-filmed with it, so nobody learns the old way.

Aimed at change adoption

Release notes as video

Every release gets a short narrated explainer of what is new, filmed on the release itself.

Aimed at feature adoption
07 · How it works

From your software to a living library, by itself.

Five stages. You set them up once and watch every one of them in your studio.

8%Preparing
    08 · Live, while it happens

    Watch your library come together.

    A cloud machine is started for your production alone. Your studio shows every stage as it happens: signing in or installing, exploring each chapter, every defect the moment it is found and the moment it is fixed, the quality checks the video has to pass, and the delivery. No status meetings, no waiting for a file.

    Open your studio →
    09 · Your video, your format

    Any shape. Any quality. A natural voice.

    Choose before the production starts, including the target duration; the video is recorded in exactly that format, so text stays sharp at every size.

    Video type
    Shape
    Quality
    Narrator

    Open the cart. Your items and the total are side by side.

    1920 × 1080screens, websites and presentationstour pace

    • Zoom & pan
    • Circles
    • Arrows
    • Lines
    • Underlines
    • Numbered callouts
    • Spotlight
    • Blur for personal data
    • Cursor & clicks
    • Burned-in subtitles
    • Captions file
    • Your logo and colours
    10 · What you receive

    Everything a library needs, in one package.

    Watch it in your studio with chapter markers, read along in the transcript, or download it all as one ZIP.

    PDFThe report, as PDF and Word

    A structured report that shows how every figure was measured, with a report assistant that explains it in plain language.

    1. Summary and key figures
    2. How it was measured
    3. The process, step by step
    4. Defect records
    5. Regression testing
    6. Video production
    MP4Narrated video

    Voice, subtitles, camera work and annotations, in your format and your brand.

    VTTCaptions

    Subtitles with real timings, for players and accessibility.

    TXTInteractive transcript

    Search it, select a line to jump there, download it as text.

    STEPSStep-by-step guide

    Every step with its screenshot and words, as PDF and Word.

    ASKReport assistant

    Plain-language summaries and answers about the report.

    PNGScreenshots

    Every step of the video, and every defect before and after.

    DIFFThe fixes

    From source code: every repair as one patch file.

    PRA pull request

    On its own branch, with every fix listed. You review and merge.

    ZIPThe whole package

    Everything above in one download, ready to archive or share.

    11 · Why the words matter

    The video gets watched. The transcript gets everywhere.

    Every explainer comes with its exact words, timed to the picture. That text does six more jobs for you.

    Interactive transcriptExample · Chapter 3 · Approve a purchase order
    1. Open Purchasing, then Orders awaiting approval.
    2. Select the order. Its lines and the budget are side by side.
    3. Check the cost centre. It must match the requester’s team.
    4. Press Approve. The order moves to Ready to send.
    5. The supplier receives a copy, with your reference.
    Transcript (.txt)Captions (.vtt)Step guide (PDF, Word)

    A searchable help centre

    Publish the words beside the video, and your help centre is searchable by people and by search engines alike (SEO).

    Accessibility

    Burned-in subtitles and a captions file with real timings, for every viewer and every player.

    Translation and localisation

    Plain, timed text is where translation starts, for captions, guides and help articles.

    Knowledge bases and chat assistants

    Feed your support knowledge base and chat assistant the exact steps, in the order the software needs them.

    Training records for audits

    A written record of what staff were shown, step by step, for audits and compliance.

    Skimmable step guides

    For people who prefer reading: every step with its screenshot, as PDF and Word.

    12 · The return

    Your numbers, not ours.

    Enter your own ticket volume and costs. The calculation runs here, in your browser: nothing is sent and nothing is stored.

    Your support desk

    The same questions your team answers again every month.
    Industry estimates put a tier-1 ticket at $15–$30. Use your own figure if you have one.
    How-to questions are the ones a video answers best.
    Used for the hours given back. It is the same saving, counted in time.
    An illustrative figure for the calculation, not a quote: use your package price, or the figure in your quote.

    What the library gives back

    Payback on each month of the library

    2.5 weeks

    Paid back within the month

    Monthly support savings
    $2,640
    Annual support savings
    $31,680
    Hours given back, a month
    20 h
    240 h a year
    Net, after the investment
    $13,680
    a year
    Answering 120 of your 200 monthly tier-1 tickets with short videos saves about $2,640 a month ($31,680 a year) and gives your team back 20 hours a month. Each month of the library is paid back in 2.5 weeks.

    The formula, in the open

    Support savings only. Faster activation, lower churn and shorter staff training are real gains too, and none of them is counted here.

    1. Answered by videotickets × share200 × 60% = 120 a month
    2. Monthly savingsanswered × cost per ticket120 × $22 = $2,640
    3. Annual savingsmonthly savings × 12$2,640 × 12 = $31,680
    4. Payback, in weeksinvestment ÷ (monthly savings × 12 ÷ 52)$1,500 ÷ $609 a week = 2.5 weeks
    5. Hours given backanswered × minutes ÷ 60120 × 10 ÷ 60 = 20 h a month
    13 · Pricing

    Fund your account. Pay for what each video uses.

    These retainers are proposals for discussion during our private pilot. Every engagement is a custom quote: this is not a live public price list or checkout offer.

    1Fund your accountonce, or with a monthly plan
    2Describe the videothe estimate updates line by line as you type
    3Start itthe estimate is held, not spent
    4Pay what it usedthe rest comes straight back
    START HERE

    Launch library

    Your first library: the questions your team answers most.

    By quotation
    • A first set of micro-explainers for your top recurring questions
    • From your live app and manual, or your source code
    • Captions, transcripts and step guides
    • Your logo, colours, intro and outro
    Get started
    MONTHLY RETAINER

    Growth retainer

    For product teams that ship every month.

    Custom scope
    • Everything in the Launch library
    • Re-filmed on a schedule as your software changes
    • Bug fixes with proof, from your source code
    • Repository sync, with what changed since the last video
    • Up to 4K, in every shape
    Get started
    ENTERPRISE · TALK TO US

    Enterprise enablement

    For organisations with many products, teams and roll-outs.

    Talk to us
    • Libraries across your products and internal tools
    • Customer, staff and partner onboarding
    • Security and data processing review
    • Custom budget caps
    • Organisation-level reporting
    Talk to us
    1. 1 Choose how to fund
    2. 2 Create your workspace
    3. 3 Pay
    4. 4 Connect your software
    5. 5 Describe your first video

    Not sure how much to add? Connect your software first: once it has been analysed, Vidabug shows what your first video will cost before you pay anything.

    Every video includes the live view, the report assistant, natural narrator voices, burned-in subtitles, the captions file and the interactive transcript. A production that does not deliver costs nothing.

    14 · Trust is the foundation

    Your software is too important for black-box promises.

    The policies are public, and independent verification is never claimed when it has not happened.

    An isolated machine

    Every production runs in a private cloud machine made for it alone. From source code, your app runs there with synthetic data only.

    A test login, kept out of reach

    For your live app, use a test account. The login secret never enters the cloud machine: it is substituted only on the way to your own site, and never appears in the video or the report.

    Scoped access

    Repository credentials are scoped to the host and repository you chose, never enter the machine, and can be revoked at once.

    Personal data blurred

    Personal and secret values on screen are blurred before they are recorded.

    Your main branch, untouched

    Every fix goes to its own branch and comes back as a pull request or a patch for you to review.

    Honest results

    A repair is called verified only when its tests prove it; anything else is reported as unverified.

    Explore the Trust Centre ↗

    15 · Questions

    Good to know

    What are the two services?

    Videos: narrated explainer videos of your software, one short video per task, with captions, transcripts and step guides, filmed from your live app or your source code. Bug fixes: from your source code, each defect Vidabug meets in the flows you choose is documented; the ones within scope are repaired, retested, filmed again and committed to a repair branch you own, with before and after proof. It can miss defects and does not certify an app as bug-free. A production from source code does both.

    Can we see or change how Vidabug tests and films?

    You decide what is covered: the chapters, the video type and length, the checks from the catalogue and your own checks written in plain words. How the work is done, the testing procedures and the recording and narration methods, is Vidabug's, and it gets better with every production without you writing or maintaining a single script. What you always get is the proof: every check has its result and evidence, every repair its failed action, root cause, change and re-test, and nothing reaches your production code until you choose to merge.

    What if a production does not deliver?

    It costs nothing: what it held comes back to your balance by itself, and you are told in plain words what stopped it. Stop a production yourself and the unfinished share comes back too.

    What do we keep?

    Everything is delivered in standard formats you keep and use anywhere: the video as MP4 with a captions file, the report as PDF and Word, the repairs as a patch and a pull request in your own repository, and the whole package as one ZIP. Your source code stays yours, and the Studio shows the engineering time each production saved, with how it is estimated.

    How does pricing work?

    You fund your account, once with a top-up or every month with a plan, and each video is paid from that balance. Before you start, the studio shows an estimate line by line, and it updates as you describe the video you want. Starting holds the estimate; when the video is delivered you pay what it really used and the rest comes straight back. Start as many videos as your balance covers, and top up whenever you like. Larger organisations can talk to us about an enterprise agreement.

    Do you need our source code?

    Not for videos. From your live app, Vidabug needs only the address of your running, hosted software, a test login and your user manual. Source code is the other way in, and the one that brings bug fixes with proof.

    How is our live-app login kept safe?

    Use a test account, not a real person’s. The login secret never enters the cloud machine that films your app: it is substituted only on the way to your own site, so it is never stored in the video or the report. You can change or remove the test account whenever you like.

    What do we upload?

    For the live-app way in: your user manual as PDF, Word or Markdown, your logo, your colours, and the intro and outro text you want on every explainer. For the source way in: a repository on GitHub, GitLab, Azure DevOps, Bitbucket or any Git host, or a ZIP of the source.

    How long is each explainer?

    You set the target duration. Short micro-explainers answer one question each; a training video takes a whole workflow step by step, more slowly, with every action numbered. As a guide, a walkthrough chapter runs about 45 seconds and a training chapter about 90, plus a short introduction and summary.

    Do we get transcripts, and in which languages?

    Every production has burned-in subtitles, a captions file with real timings and an interactive transcript you can search, follow and download as text. Narration is in English, with natural US and British narrator voices. The timed transcript is the starting point for translating captions, guides and help articles in your own localisation workflow.

    How does the library stay current?

    Set a schedule and Vidabug re-films on it. For source projects, repository sync follows your default branch and shows what changed since the last video, and recurring productions film the new version on schedule.

    What does Vidabug need from our repository?

    Access to the repositories you choose: through the Vidabug GitHub App, or a token for GitLab, Azure DevOps, Bitbucket or another Git host, kept in an encrypted vault and bound to that host. It reads the code for discovery, and, only when an owner authorises repair branches, a production commits its fixes to a new branch and opens a pull request for you to review. Without that authorisation the fixes come back as a patch and nothing is pushed. You can revoke access at any moment.

    Will it change our code?

    Only on a fix branch you review. Your default branch is never touched; every repair is its own commit with its test, listed in the pull request and the report.

    What happens to our code and data afterwards?

    The cloud machine exists for your production only and is removed afterwards. Uploaded archives and manuals stay in your Vidabug workspace until you delete the project.

    Two services, one start

    See your software explained. See its bugs fixed.

    Choose a package, or connect your live app or your repository first and get a package recommended. Then watch the first explainer and the first repair come together live.

    Start a project Book a pilot conversation Monthly or annual packages, or a custom quote · Read the Trust Centre
    STYLE