Who it is for
Teams who built a product and need to explain it.
What it does
- You record the product in the browser as you use it, and ReqTalk asks for approval before anything is captured.
- Sensitive fields are masked before the recording is used.
- Each scene gets a script, and the finished explainer is approved before it renders.
How we built it
ArcLayer did the product design, the design system and the engineering. AI agents wrote code and tests against ReqTalk’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 ReqTalk
Sensitive fields are masked at capture
The recorder masks sensitive fields in the page while it records, so they never reach the video.
Checks on every change
CI type-checks, tests and builds the extension, scans the source and runs the renderer tests on every push to main and every pull request.
Database rules are tested
SQL tests check the database rules and row-level security.
The renderer is tested in a locked-down container
On main, the renderer image is built, tested in a restricted container and published to the registry.
The API deploys with a smoke test
The Supabase function deploys from a manual workflow and is followed by a smoke test.
Releases are tagged
A version tag creates a draft release, and the tag has to match the package version.