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 walking a user through a dreaded workflow is still making the user do it.
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 tasks worth taking over. No event instrumentation, no content to write first.
Does the task, with the user watching
The user hands the task over. The autopilot completes it in their own session, on screen. Every target is highlighted first. Consequential clicks wait for an inline Allow. Sensitive fields stay human-typed.
Certified by synthetic users, on every PR
Synthetic users run your real workflows in real browsers, then hand the task to the autopilot under test. Every run is graded. An autopilot ships only while its workflow passes.
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.
Two meters, nothing else
Simulation runs while you build and certify. Completed handovers when an autopilot finishes a task for a real user. A handover that stops or fails costs nothing. Creation is never metered.
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 tasks worth taking over. |
| When it acts | When your code triggers the tour. Same steps for everyone. | When the user asks. The offer sits on the workflow; handover is always the user’s explicit act. |
| In the session | Step-by-step popovers you authored. | The autopilot does the task on screen, step by step. Sensitive fields stay the user’s to type. Consequential clicks wait for their Allow. |
| Pre-launch testing | Your own QA. | Certification: synthetic users run the workflow and the handover on every PR. A failing suite takes the offer down. |
| 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. | Two meters: simulation runs and completed handovers. A handover that stops or fails costs nothing. The scan and your journey map are free. |
| Best for | Teams that want to hand-build a small, stable set of tours. | Teams that want the workflow done for the user, with nothing to author. |
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.
- The tour plays and the task still does not get done.
- You want an agent certified on every PR, not a script you QA by hand.
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. Autopilots cover what tours cannot: actually completing the workflow when a user hands it over.
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. In production, the autopilot runs in the user’s own session; no credentials pass through Holostaff.
Libraries cost a license fee plus the engineering time to build and maintain every tour. Holostaff meters simulation runs and completed handovers, 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.