Bug reports that skip the back-and-forth

The slow part of a bug report is rarely the writing. It is the three messages afterwards asking what you clicked, what you expected, and whether it happens every time. A recording answers all of them at once, and anyone on the team can make one, not only QA.

Clicks are visible, not described

Click highlights show every click as it happens, and a chapter marker dropped at the moment it broke lets the engineer jump straight there.

Comments land on the frame

An engineer replies at 1:12, not "about halfway", can pin the note to a point on the frame, and can answer with a short recording of their own. Resolve the thread when it is fixed.

Blur what should not be in the ticket

Drag a box over an API key, a customer name or a private message in the web editor before you share it.

Screenshots too

Some bugs are one frame. The extension captures the visible area, a full scrolling page, a selected area or your screen.

Questions

Can I attach it to a ticket?

Paste the link into Jira, Linear, GitHub or any tracker. There is also an embed for pages that render HTML.

Can people outside my company watch?

Yes, without an account. On Pro you can also protect a link with a password.

What does it cost?

The Free plan keeps up to 50 videos and 5 GB, with recordings of up to 10 minutes in up to 1080p, AI transcripts and automatic titles; free videos carry a small VeoRec badge. Pro is $7.99 a month or $79 a year: unlimited videos, 1 TB of storage, recordings of up to 10 hours, no branding, view analytics, password-protected links, custom thumbnails, and AI summaries, chapters and translation.