Ripple reads your codebase, verifies every walkthrough on every deploy, and guides your users through the product — or does it for them.
or ask it in Claude Code · Teams and Slack (coming soon) · your app’s ?
Every walkthrough below re-recorded itself the last time its code changed.
Record it once. Ripple keeps it true from then on.
A teammate does the task in staging with the recorder on. Ripple grounds every click to the code that handled it.
The script replays without a human, checking the screen, the network and the database. Only a passing replay earns the badge.
Video, step guide, in-app overlay and autoplay — all projections of the same script, filtered to what the viewer’s role can do.
Code → feature understanding → verified walkthrough → searchable knowledge → guided and autonomous action.
Per-repo analyst agents read routes, forms, handlers and permission checks.
Static analysis supplies the facts; the model supplies meaning and names.
Every capability knows its entry points, inputs, effects and who may call it.
A walkthrough is an executed script, not a recording: camera, captions and voice are applied after.
A verified walkthrough is also an end-to-end test. Docs fail the build.
PII is masked live before a frame is ever captured.
“How do I”, “where can I”, “who can”, “what changed” — answered for the asker’s role.
Permission answers link to the line of code that enforces them.
Anything unverified is labelled. Nothing stale is hidden, nothing stale is presented as fact.
“Guide me” spotlights each step in the user’s own session; Next unlocks only when the step is done.
On the wrong page? “Take me there.”
A locator that needed a fallback is the earliest staleness signal — it feeds the alerts.
“Do it for me” runs the workflow with the user’s own permissions — never more. With auto-save off, the user clicks Save.
Every write is confirmed first, with its effects and reversibility spelled out.
Production needs an admin allowlist, a matching build commit, and a kill switch nearby. Payouts and pricing are excluded by default.
One index, every surface. Developers never write docs by hand.
A script tag, or the extension for apps you can’t modify. Role-aware results, three modes.
Ask in Teams or Slack and get the answer with its verification label. Both are coming soon; channel alerts already post to Slack webhooks.
Impact analysis, re-verification, preview video and auto-repair PRs — before merge.
Author, validate, run and render walkthroughs from your agent. Your agents can query Ripple too.
Read-only repo scopes by default. Ripple only ever opens pull requests — it never merges, and no customer code trains a model.
Console, runner and index on Ripple. Fastest to start.
Videos and traces in your S3, runner in your environment. Ripple keeps metadata only.
The whole stack inside your cloud account. Sensitive code never leaves.
Connect staging, record a task, watch it verify itself on the next deploy.