Who it is for
Product teams who turn screen recordings into walkthroughs.
What it does
- Vistralo cuts a recording into the screens it passes through, each with its number and timecode.
- Every screen gets a short line that explains what happens on it, ready to edit.
- The whole recording lays out like a contact sheet, so a walkthrough can be reviewed at a glance.
How we built it
ArcLayer did the product design, the design system and the engineering. AI agents wrote code and tests against Vistralo’s design system, and a person reviewed each change before it merged.
Build note: Why every product gets its own design system
How we work on Vistralo
Every change goes through a pull request
Work happens on a branch, and main only accepts a merge once the Validate source check passes.
CI validates the source
The check builds the server, runs the tests, type-checks the web app, lints the design rules, audits dependencies and checks the worker scripts.
Journeys are tested in a real browser
Playwright drives the main journeys, accessibility and billing flows in Chromium and keeps the screenshots as evidence.
Preview first, then production
Vercel builds a preview for every pull request and deploys production when it merges, behind a strict content security policy.
The worker can be rolled back
The video worker is updated by hand with a backup of each changed file, so a release can be undone.
Keys are sealed and costs capped
Provider keys are sealed in the browser, so the database only holds ciphertext, and every job has a cost cap.