Async video for teams·Free for everyone, pay for what you keep

Free for your whole team. You only pay for the videos you keep — delete the rest and your bill drops with them.

Velo demo video

Real product recordings land here. Pass a public share slug to this slot to embed one.

Two minutes with Velo

How much would Velo save your team?

Move the sliders. The first column is what other tools charge you for every person on the team — even the ones who never record a video. The second is what you'd actually pay us.

About 1 GB equals 20 minutes of high-quality screen recording. Delete a video and your bill drops the next day.

Other tools

50 people × $24 each, every month

$1,200/mo

Velo

Only the videos you keep

$10/mo

You save

$1,190/mo · $14,280/yr

That's 99% less than Loom Business for the exact same usage.

Record, share, find. Three things that should just work.

01 · Record

One click. No download.

Capture your screen, your camera, your microphone — or all three at once with a circular cam bubble. Works in any browser. No extension, no installer, no upload waiting.

  • Screen, window, or single tab
  • Camera bubble in the corner
  • Mic and system audio
  • Pick your devices on the fly

02 · Share

One link, anyone can watch.

Drop a link in Slack, in a ticket, in an email. Viewers don't need an account. Comments and view counts come back to you. Public, workspace-only, or password-protected — your call.

  • Public, workspace, or password-gated
  • No sign-up required to watch
  • Comments come back to you
  • View tracking on every link

03 · Find

A library that earns its keep.

Tag every recording with the project, ticket, or theme it belongs to. Filter by tag, search by title. Three months later when someone asks “wasn't there a video about that?” — you'll find it in two clicks.

  • Tag any video, any time
  • Filter library by tag
  • Search by title
  • Anyone on the team can tag

Every video gets a brain.

Velo transcribes, summarises, and pulls structure out of every recording you keep. Action items, test cases, chapters, suggested next steps — generated automatically and ready by the time the video is.

● Recording
Auth refactor walkthrough12:04

✨ Summary

Walkthrough of the new auth middleware. Replaces the legacy session-token approach with short-lived JWTs, adds rotation, and moves the refresh-token store off the API server.

Chapters

  • 00:00Why we're replacing the old middleware
  • 02:14JWT rotation strategy
  • 05:48Refresh-token storage
  • 08:30Migration plan & rollout

Action items

  • Migrate session_tokens table to redis @riley
  • Add rotation to /auth/refresh endpoint @taylor
  • Document the new flow in the runbook @jamie

Suggested test cases

it("rotates refresh token on /auth/refresh");
it("rejects expired access tokens");
it("invalidates old session on logout");
it("allows concurrent sessions per user");

Transcripts on every video

Searchable, copyable, accurate. Find the exact moment someone said the thing you remember.

One-paragraph summaries

Skim a 20-minute recording in 20 seconds. The summary lands the moment the recording finishes processing.

Action items pulled out

To-dos extracted from the conversation, ready to copy into Linear, Jira, or your standup notes.

Test cases for engineering

When you walk through a feature, we draft the test cases for it. A nudge toward the work that comes next.

Auto-generated chapters

Long recordings get a clickable table of contents. Jump straight to the part you need.

Suggested next steps

What naturally follows from what was said. Recommendations for what the team should look at next.

Search across your library

Find recordings by what was said, not just by title. Semantic search across every transcript in your workspace.

Chat with any video

Ask a question about a recording. Get the answer, with the timestamp where it was discussed.

AI features ship with the paid plan. Free workspaces get transcription on every video.

This is what your library looks like.

Tagged, searchable, filterable. Send the link to a teammate and they see the same view.

govelo.ai/acme/library

velo.

New recording

Library

Filtered by#auth-refactor
  • Auth refactor walkthrough

    #eng#auth-refactor
    ready12:04
  • Q1 design review — payments flow

    #design#payments
    ready08:21
  • Onboarding — new hire setup

    #onboarding#people-ops
    ready21:55
  • Sprint 23 demo

    #sprint-23#demo
    ready15:40
  • Sales call — Acme follow-up

    #sales#acme
    uploaded06:12

Why we built this

Videos are the asset. Recording them should be free. Every other tool charges by the person — so teams ration access, and the library shrinks to whoever the budget allows. We flipped it.

01

Bring your whole team

Engineers, sales, designers, the intern, the contractor here for 90 days. Recording should never be a permission you have to budget for. Add everyone who might want to explain something with a video.

02

Pay only for what you keep

Free for your first videos. After that, you pay a few cents a month for each video that stays in your library. Delete one and the bill drops with it. No seat math, no surprise renewals.

03

Tag it so you can find it

Tag every recording with the project or ticket it belongs to. Three months from now when someone asks “wasn’t there a video about that?” you’ll find it in two clicks.

Start recording freeHow it worksFree for your first videos. No credit card needed.

Velo makes sense for whoever's recording.

For Engineering

Velo for Engineering

Engineering teams use Velo to capture knowledge that would otherwise live in someone's head. Bug walkthroughs, architecture decisions, code reviews, post-mortems — all recorded once and tagged so the next person who asks the question finds the answer instead of asking you.

Recordings you might find in the library

  • Bug walkthrough · #auth-refactor #ENG-234

    Five-minute reproduction of the JWT rotation race. Tagged with the Linear ticket so the assignee finds it from their inbox.

  • Architecture decision · payments rewrite

    Twenty minutes explaining why we picked the new event-sourced model. Becomes the canonical reference instead of a Notion doc no one updates.

  • Code review · caching layer

    Walks the reviewer through the diff with voice-over and a cam bubble. Faster than a synchronous review meeting.

  • Production incident · 2024-02-15

    Live recording during the fire. Tagged with #post-mortem. The incident write-up references the timestamps.

Tags this team would use

#eng#bug#post-mortem#architecture#review

For Sales

Velo for Sales

Sales teams use Velo to replace dense PDF decks with personalised 90-second video walkthroughs. Track who watched, see how far they got, and follow up with the people who never opened it. The library becomes your reusable demo asset, tagged by deal stage and customer.

Recordings you might find in the library

  • Acme demo · Q1 expansion

    Personalised walkthrough of the features Acme cares about, with their logo on the playback page.

  • Pricing follow-up · Northwind

    Three-minute explainer of the custom pricing, sent in lieu of a 60-minute call. Closed in two days.

  • Renewal pitch · Disney

    Recapping the year and pitching the upgrade. Tagged with #renewal #q4 so the team can find similar past pitches.

  • Discovery recap

    End-of-call summary recorded immediately after the call ends. Sent to the prospect within 30 minutes.

Tags this team would use

#sales#demo#renewal#discovery#pricing

For Design

Velo for Design

Design teams use Velo to capture intent. A 4-minute walkthrough of a Figma file beats a 30-minute review meeting — and leaves a trail. Designers tag recordings by feature and sprint, comments come back asynchronously, and the library becomes the audit log of every design decision.

Recordings you might find in the library

  • Checkout v2 · Figma walkthrough

    Voice-over of the new flow with the rationale. Engineering watches at 1.5×, comments with timestamps.

  • Design crit · onboarding

    Recorded weekly crit so designers in different time zones can join async. Tagged with #crit #onboarding.

  • Design system update · Q1 refresh

    Walks through the new tokens and where they apply. Reused in the next four onboarding cycles.

  • Prototype handoff

    Captures the micro-interactions that don't survive a static export. Engineers reference it during build.

Tags this team would use

#design#crit#figma#design-system#handoff

For Onboarding

Velo for Onboarding

People-ops and engineering managers use Velo to scale themselves. Day-1 setup, expense reporting, code-of-conduct, the unwritten team norms — record it once, tag it #onboarding, and every new hire gets the same experience without you having to be in the room.

Recordings you might find in the library

  • Day 1 setup

    How to get your laptop, which Slack channels to join, where to find the wifi password. Updated whenever the process changes.

  • Filing your first expense report

    Three-minute screen recording of the entire flow. Replaces a help-desk ticket.

  • How we run sprints

    Engineering manager walks new joiners through the team's process. New hire watches before standup on day three.

  • How to request time off

    The kind of mundane process that should not require a 1:1.

Tags this team would use

#onboarding#people-ops#process#day-1