Holostaff vs. product tour libraries
Shepherd.js and Intro.js give developers complete control over a tour in a few kilobytes of JavaScript. If you want to hand-craft the guidance, use them. Holostaff exists because most stalls happen where nobody wrote a tour.
What tour libraries do well
- Tiny, dependency-light, and fully under your control.
- Genuinely cheap: Shepherd.js is a one-time $50 commercial license, Intro.js starts at $9.99.
- No vendor runtime and no data leaves your app.
- Wrappers for React, Vue, and friends.
- You own every pixel and every word of the experience.
If a hand-crafted tour is what you want, Shepherd.js or Intro.js is a fine choice.
Where Holostaff is different
Learns your product from the codebase
One CLI scan draws your real customer journey: routes, workflows, and the exact steps where users stall. No event instrumentation, no content to write first.
Acts in the session, with guarded actions
A copilot can take the stuck step together with the user, on their screen. Every target is highlighted first. Consequential clicks wait for an inline Allow button. No answer means no.
Rehearses before meeting anyone
Simulated users run your real flows in real browsers and get stuck on purpose. Every run is graded. A copilot that fails rehearsal does not go live.
Ships like code, not like a widget
holostaff deploy opens a pull request: SDK init, journey stage markers, the embed. Your engineers review the diff. Merging is going live. Reverting is rollback.
Bills per engagement
The scan and your journey map are free. Going live starts a trial. After that you pay when a copilot actually helps someone. Nudges your users ignore are free.
Side by side
| tour libraries | Holostaff | |
|---|---|---|
| Setup | npm install, then your engineers write and maintain each tour step in code. | One CLI scan. The journey map skeleton is live in about 90 seconds. |
| How it learns your product | It does not. Your engineers encode the knowledge step by step. | Reads your codebase: routes, workflows, and the steps where users stall. |
| When it acts | When your code triggers the tour. Same steps for everyone. | Per user, at the moment that user gets stuck. |
| In the session | Step-by-step popovers you authored. | Nudges, voice conversations, and guided on-screen actions behind an Allow button. |
| Pre-launch testing | Your own QA. | Rehearsal evaluations: simulated users run real flows and every run is graded. |
| How it ships | Part of your frontend code, shipped like any feature. | A pull request your engineers review. Merging is going live. |
| Pricing model | Open source with commercial licenses: Shepherd.js one-time $50 to $300, Intro.js from $9.99. The real cost is engineering time on tour upkeep. | The scan and journey map are free. Going live starts a trial. Then billing follows engagement, and ignored nudges are free. |
| Best for | Teams that want to hand-build a small, stable set of tours. | Teams that want per-user help without authoring or maintaining tours. |
Pick a tour library if
- You want hand-crafted control and are happy to maintain it.
- Your guidance needs are small, stable, and known in advance.
- Your budget rounds to a one-time license fee.
Pick Holostaff if
- Tour code rots every time the UI changes.
- Users need help in places you did not predict.
- You want help that adapts per user instead of replaying a script.
See it before you install anything
Want proof first? Explore a live journey map. It is Documenso, the open source document signing platform, scanned by our CLI. No sign-up needed.
Common questions
No. Keep the tours that earn their keep. Copilots cover everything the tours do not: the unpredicted stalls, the questions, the moments that need a hand on screen.
It is a CLI plus a hosted service. The CLI is open source, Apache 2.0, on GitHub. Going live adds an SDK and a script tag through a pull request your engineers review.
The scan uploads a structured artifact you approve first: routes, workflows, copy strings, and identity. Source code, env files, secrets, and git history never leave your machine. The trust report shows exactly what uploads before anything does.
Libraries cost a license fee plus the engineering time to build and maintain every tour. Holostaff bills on engagement, with nothing to build. The scan and your journey map are free.
Last verified August 6, 2026. Spotted something out of date? Tell us: hello@holostaff.ai.