Start here
Rendemo in one tag. What a demo is, what a tour is, which one you want, and the single script tag that installs either.
One tag
Rendemo is interactive walkthroughs of your product, on the marketing site or in the app.
<script src="https://www.rendemo.com/embed.js" data-demo="acme/onboarding" async></script>The script mounts the experience where the tag sits. One capture, two ways to publish.
Guided demo or overlay tour?
One capture, two ways to publish. Guided demo and overlay tour are modes of the same walkthrough, not two products.
Guided demo
Overlay tour
Same tag either way. A tour adds data-mode="tour" and needs markers in your source, which is the one real difference in effort: a demo touches no code, a tour edits your components.
One near-collision, because it is a different thing rather than an old name: the browser extension’s Live Guide replays a recorded demo over a live page from captured DOM, with no markers involved. “Guide” in this product always means that.
Where to go next
Three jobs. Each page ends with a working thing rather than a complete specification.
- Put a demo on a page — the tag, where the demo id comes from, inline versus a Watch-the-demo button, and what to check when nothing appears.
- Guide people through your app — mark the elements, turn the tour on, preview the draft against your running app.
- Keep tours from breaking — a tour anchors to elements in your source, so deleting one breaks it silently.
rendemo checkcatches that in CI, offline and with no token.
Reference has every attribute, event and exit code the task pages link out to. Driving it from an agent covers the Claude Code plugin and connecting any MCP client directly — worth reading when you want the tour authored for you rather than by hand.