First-run onboarding comparison
Bootstrapware Onboard vs Shepherd.js and Driver.js
Last reviewed November 2026. Vendor packaging changes; verify their site before you buy.
Quick comparison
| Dimension | Shepherd.js and Driver.js | Bootstrapware Onboard |
|---|---|---|
| Primary job | Client-side tooltip tours (Shepherd.js, Driver.js) | First-run setup checklist embed |
| What the user sees | Steps anchored to elements on the page | A checklist. Modal, window, and launcher are presentations of that checklist |
| Progress | Not included. No persisted user or workspace record in the library | Dual-scope progress, pinned revision, dismiss, and snooze |
| BFF / auth | None. The library does not mint a host token | Host-asserted user.id and workspaceKey. Live Hosted uses a server-minted author token |
| Price shape | Library you operate. No dollar copied here | Free / BYO $9.99 / Hosted $19.99 workspace. No MAU tax |
Where the libraries are stronger
- A tooltip tour you attach to elements you already render.
- No vendor account when a client-side tour is the whole job.
Where Bootstrapware Onboard is stronger
- Progress for a user and a workspace, on your backend (BYO) or Hosted.
- A server-minted author token for live Hosted writes. The libraries have no BFF.
- Dismiss and snooze without pretending a tour was completed.
- Free locally, then BYO $9.99 or Hosted $19.99. No MAU tax.
Tours without a progress record
Shepherd.js and Driver.js step a person through the DOM. That is a tour. The Onboard first-run checklist does not do that. If you need the step to survive a reload, a second device, or a shared workspace, the libraries leave the store and the authorization to you. Onboard already has both. See Onboard pricing for Free, BYO, and Hosted.
Who should pick an open-source tour or Bootstrapware Onboard
Pick Shepherd.js when you will build the tour yourself. Checked 2026-11-16: free for open-source, personal, and non-commercial projects. Business is $50 lifetime for up to 5 projects. Enterprise is $300 lifetime. For an open-source tour library, treat that as the starting constraint rather than a footnote. The work belongs in the product the customer is already signed into. Bootstrapware publishes configuration and, only on a Hosted plan you choose, the records that plan names. It does not become a second system of record by accident.
Pick driver.js when an MIT tour library is enough. driverjs.com says it is free for everyone, forever. The spreadsheet, message, post, checklist, thread, quote file, or visitor question stays on the path you picked. When the product is Importer, the spreadsheet never leaves the browser: parsing, mapping, validation, and in-file duplicate checks run in the tab. File bytes, parsed rows, and the filename are not posted to Bootstrapware. onComplete is what your own tour code or a hosted checklist is allowed to see.
Those libraries do not store checklist progress, eligibility, or a hosted config revision. Write the server handler so a failed row is reported back instead of half-inserted. Preview errors stay inline. A customer can fix the cell, exclude the row, or download the error file and try again. Do not log payloads you would not want in an application log. Do not send those payloads to MCP or to a webhook.
Pick Bootstrapware Onboard when the checklist state is the product, not a spotlight on a button. Install the package, render it in a client boundary, and point the callback at your server. Publishable keys identify the workspace. Secret keys stay on the server. Local mode and test keys are free. Live config and live Hosted writes follow the price already printed on this product's pricing page. Re-read that page before you quote a number in your own UI. Link the landing page and the pricing page from the install notes so the next reader can see the boundary and the plan without searching.
Ship a thin vertical slice first: one required field, one successful completion, and one deliberate failure. Then add the real schema. If an agent writes the integration, hand it the product AGENTS.md and reject a diff that uploads content Bootstrapware is not supposed to store. The component is typed. The adapter is yours on BYO. Hosted is the plan where Bootstrapware stores that product's customer content, with the cancel rule already stated on the pricing page: writes freeze, export stays for 30 days, then Hosted data is deleted. Switching Hosted to BYO keeps the rows.
| If you need | Pick |
|---|---|
| A tour library you style yourself | Shepherd.js or driver.js |
| Persisted setup progress behind your auth | Bootstrapware Onboard |
Onboarding checklist for React · Onboarding checklist pricing · Bootstrapware Onboard vs Frigade · React onboarding checklist component
FAQ
Are Shepherd.js and Driver.js onboarding products?
They are open-source libraries for tooltip tours: a step points at an element on the page. They do not ship a stored user or workspace progress record, and they do not include a BFF. Persistence, if you want it, is code you write.
Does Onboard run a tooltip tour?
No. Onboard is a checklist. presentation can be section, modal, window, or launcher. A modal shows the checklist. It does not attach tour steps to DOM elements, and there is no visual builder.
Where does progress live?
Your backend on BYO ($9.99) or Bootstrapware on Hosted ($19.99). The host asserts user.id and workspaceKey. Live Hosted writes need an author token minted on your server.
What do the libraries cost?
This page does not copy a vendor price. Shepherd.js and Driver.js are libraries you run yourself. Bootstrapware Onboard is free locally and on test keys, then BYO $9.99 or Hosted $19.99 per workspace.
Related: Onboard first-run checklist · Onboard pricing · vs Frigade Flows · Progress · All Onboard comparisons