Demo videos that keep up with your releases

Redemo films your real product in a browser, following the script you approve. For a private app, you provide a dedicated demo or staging account with sample data. You review the first captured footage and final video before publication. If you then enable automatic updates, we can re-film the same approved script and publish the finished replacement after verifying its path, without another review. No SDK or repository access is needed. Credentials are encrypted. When you provide an account, you can choose to keep it for updates while your subscription is active. You can change that choice or delete the account from your project. Turning retention off stops automatic recordings. Manual recordings you already approved can finish, then we delete the account after all current walkthroughs are approved and the retention period ends. Cancellation also schedules deletion. Your project shows the timing. Existing accounts are not opted into longer retention automatically. A later recording may need you to provide the account again.

No. A site is the product you connect to Redemo, with one subscription. It can contain an overview and multiple feature videos, each with its own script and reviews. Those videos share the site’s monthly update allowance. A different site needs a separate subscription; making another video for the same site does not.

Contact contact@redemo.io to discuss a cloned-presenter pilot before subscribing for this feature. Availability and terms must be confirmed separately; it is not included automatically with a Scale purchase. The pilot pairs your own face and voice in the language you record, requires your consent, and includes a preview for you to approve before it can be used in a final video.

Standard presenters are available in US English. The presenter and its paired voice are not separate settings. An AI presenter narrates over your real product footage, with subtitles. You review the first finished video before publication. Automatic updates reuse that approved script and presenter.

Redemo differs from Synthesia and HeyGen in what sits behind the presenter: those avatar tools generate a talking head over slides or stock backgrounds, while Redemo films your real, live product and puts the presenter on top of it. The footage is your actual application, captured by a headless browser at the moment of the render, not a screenshot someone pasted into a slide weeks earlier. The gap shows up on the second video. With an avatar tool, shipping a redesign or a new feature means rebuilding the visuals by hand before you can re-record. With automatic updates enabled, Redemo checks the approved path after a detected release, then records and publishes a new cut within your monthly allowance. If the path no longer works, the published version stays live while we review what needs to change. Avatar generators are good at generic talking-head content, training clips and localised voice-over. A product demo is a different job.

Redemo differs from Arcade and Storylane in format: interactive tours are click-through widgets a prospect has to drive themselves, and — useful as they are — they are not a video. Redemo produces a real video with voice-over that prospects can watch, share, and that you can post anywhere: your homepage, emails, social, sales decks. Both approaches show real UI, so this is not an argument about quality, it is about where the asset can travel. A tour lives in an iframe on a page someone already opened. A video autoplays in a feed, sits above the fold, goes out as a thumbnail in a cold email, and can be handed to someone who never visits your site. You also place no hotspots and maintain no steps when the flow changes. Plenty of teams run both: a tour for hands-on evaluation, a video for the top of the funnel.

We check your product daily for changes in its build assets, when the site exposes a usable signal. For videos with automatic updates enabled, a changed build triggers verification of the exact approved path, then capture, rendering and publication if all checks pass. Enabling starts with the next detected change. You can still request an update from your account, connected assistant or release pipeline; those requests join the review queue and share the same monthly allowance.

For an opted-in video, we first verify its approved path. If it still works and access, subscription and budget remain valid, we re-film the same script and publish the complete replacement automatically. A broken path, missing access, unavailable check or incomplete render leaves the previous video live and opens an intervention in the app. A rewritten script needs your approval. Publication history lets you restore an eligible earlier version in one click, without rendering or spending another update. That choice holds for the current detected release; later releases can update the video again. Release notifications appear in the app, without a routine email.

The standard allowance is 4 video updates per month on Launch, 30 on Grow and 100 on Scale, shared by all videos on the same site. Requesting updates to three videos uses three updates. The allowance resets on the first of each month. Automatic rebuilds and requests from your account, release pipeline and connected assistant use the same allowance; sending a request again while that video already has an update queued does not count twice. An automatic attempt reserves one update per video, including its already published formats; a failed attempt after reservation still counts. Contact us if you need a different allowance.

Your approved final videos are available as 1080p MP4 downloads and through a hosted embed while your subscription is active. You can keep and self-host the files you download. Scale includes a hosted player without Redemo branding. When the subscription ends, new renders and hosted embeds stop, and downloads remain available for 30 days so you can save your files.