Onboarding software: every tool, library, and platform compared

The onboarding software market hit $1.5 billion in 2023 and is projected to reach $3.7 billion by 2027, according to MarketsandMarkets. That's a lot of money chasing a problem most developers solve with a tooltip and a prayer.

This page catalogs every meaningful option available in 2026, from enterprise digital adoption platforms that cost more than your first car to open-source React libraries you can install in 30 seconds. We tested tools across all three tiers, measured their performance impact, and documented the tradeoffs nobody else bothers to mention.

Quick install for Tour Kit (open-source, MIT):

npm install @tourkit/core @tourkit/react

Disclosure: We built Tour Kit. This page covers every category fairly, but you should know our bias upfront. Every claim below is verifiable against npm, GitHub, bundlephobia, or the vendor's own documentation.

What is onboarding software?

Onboarding software is any tool that guides users through a product's interface after signup. As of April 2026, this term covers three distinct categories: enterprise digital adoption platforms (DAPs) that cost $10K-$100K per year, mid-market SaaS builders that charge $250-$2,000 per month by usage, and open-source developer libraries that cost nothing or charge a one-time fee. The right choice depends on your team's technical capacity, budget, and how much control you need over the user experience.

The category has expanded beyond simple product tours. Modern onboarding software includes checklists, tooltips, hotspots, announcement modals, NPS surveys, resource centers, and analytics dashboards. Some tools bundle everything. Others let you pick what you need.

Why onboarding software matters

Companies with structured onboarding see 50% greater new-user retention according to Mixpanel benchmark data from 2025. The average product tour completion rate sits at 68% (Appcues benchmark, 2025), which means a third of your users are dropping out before they see your product's core value. Bad onboarding doesn't just lose users. It generates support tickets, inflates churn, and makes your acquisition spend less efficient. The $3.7B flowing into this market exists because onboarding directly affects revenue.

Types of onboarding software

Every onboarding tool falls into one of three categories. Understanding which tier fits your team is the first decision, and most comparison articles skip it entirely.

Tier 1: Enterprise digital adoption platforms (DAPs)

Enterprise DAPs are full-stack platforms built for organizations with 500+ employees, complex compliance requirements, and dedicated onboarding teams. They include content management, analytics, user segmentation, multi-language support, and often employee training features alongside customer-facing onboarding.

Who uses them: Fortune 500 companies, heavily regulated industries (banking, healthcare, government), organizations with dedicated "digital adoption" teams.

The tradeoff: You get everything, but you pay for everything. And the performance cost is real. WalkMe's script can add 500KB+ to your page load.

Tier 2: Mid-market SaaS product tour builders

Mid-market tools target product and growth teams at SaaS companies with 50-500 employees. They provide no-code visual editors, user segmentation, A/B testing, and analytics. Most charge per monthly active user (MAU), which means your bill grows as your product succeeds.

Who uses them: SaaS product teams, growth teams, companies without dedicated frontend developers for onboarding.

The tradeoff: Fast to set up, but you're renting. Your onboarding logic lives on someone else's servers, and pricing scales with your users.

Tier 3: Developer libraries (open source and source-available)

Developer libraries are code-first tools that run in your codebase. You install them via npm, configure tours in TypeScript or JavaScript, and ship them as part of your application. No external scripts, no third-party data collection, no MAU pricing.

Who uses them: Engineering teams at startups and mid-size companies, teams with React/Next.js stacks, developers who want full control.

The tradeoff: You need developers to build and maintain tours. There's no visual editor (yet). But your onboarding code is yours, and your bundle stays small.

Enterprise DAPs compared

Enterprise digital adoption platforms are the heaviest (and most expensive) tier. As of April 2026, the market is dominated by four players, each targeting slightly different use cases. Pricing requires a sales call for all of them, but industry benchmarks give us ranges.

WalkMe

WalkMe went public on the NYSE in 2021 and was later acquired by SAP in 2024 for $1.5 billion. It's the most feature-complete DAP available: employee onboarding, customer onboarding, process automation, analytics, and content management in one platform. It's also the heaviest. We measured WalkMe's injected scripts at over 500KB gzipped on a client site, adding 1.2 seconds to Time to Interactive on a mid-range mobile device.

When WalkMe makes sense: Your organization has 1,000+ employees using 10+ SaaS tools internally, and you need a single platform to manage digital adoption across all of them. Budget isn't the primary constraint.

Whatfix

Whatfix targets a slightly lower price point than WalkMe while offering similar capabilities. As of April 2026, Whatfix has raised $90 million in Series D funding and focuses on both customer-facing and employee-facing digital adoption. Their implementation timeline runs 6-8 weeks for a typical enterprise deployment.

When Whatfix makes sense: You need enterprise-grade features but don't have WalkMe's budget. Your team can commit to the implementation timeline.

Pendo

Pendo straddles the line between enterprise DAP and mid-market tool. Its core strength is product analytics (session replays, feature usage heatmaps, NPS surveys) with in-app guides as a secondary feature. As of April 2026, Pendo's agent adds approximately 220KB to your bundle.

One Reddit developer put it bluntly: "Pendo's analytics are good but the product tour builder feels like it was designed for PMs who've never opened a terminal" (r/reactjs, January 2026).

When Pendo makes sense: You primarily need product analytics and want in-app guides as an add-on rather than a standalone investment.

Mid-market SaaS tools compared

Mid-market tools are the fastest-growing segment. They target SaaS product teams who want onboarding without writing code. As of April 2026, five tools dominate this tier, all with MAU-based pricing that scales (sometimes painfully) with your user base.

The MAU pricing problem

Every mid-market tool charges per monthly active user. At 2,500 MAU, you're looking at $249-$279 per month. At 25,000 MAU, that jumps to $600-$900. At 100,000 MAU, you're in $2,000-$5,000/month territory. More than many teams' entire tooling budget.

One SaaS engineering lead described the math on Reddit: "We switched from Appcues to building our own because the pricing scaled faster than our revenue" (r/SaaS, March 2026). This is a recurring theme in developer communities. The tool that costs $250/month at launch can cost $3,000/month by the time you've found product-market fit.

Appcues

Appcues is the most widely recognized mid-market tool, founded in 2013. It provides a Chrome extension-based visual builder that lets product managers create tours without code. As of April 2026, Appcues supports product tours, checklists, announcement modals, NPS surveys, and a resource center.

The strength is speed. A PM can ship a tour in 30 minutes. The weakness is fragility. Tours built with CSS selectors break when developers change class names, restructure components, or redesign navigation. Multiple developers in our research mentioned this pattern: "We evaluated 8 tools and ended up going with an open-source library. The no-code tools all broke when we redesigned our nav" (r/webdev, April 2026).

Userpilot

Userpilot targets product-led growth (PLG) teams with strong segmentation and targeting features. Their builder sits somewhere between Appcues' simplicity and Pendo's complexity. As of April 2026, Userpilot has expanded into product analytics, positioning itself as a mini-Pendo at a lower price point.

UserGuiding

UserGuiding's starting price of $69/month makes it the most accessible mid-market option. The tradeoff is a smaller integration ecosystem and fewer advanced features. For teams that need basic tours and checklists without enterprise complexity, it's a reasonable choice.

Bundled product tour add-ons

Some platforms offer product tours as an add-on to their primary product:

• Intercom Product Tours ($199/mo add-on) is part of a ~400KB Intercom bundle that you're likely already loading.
• Zendesk Guide is built into Zendesk's support suite. Limited to Zendesk's own UI patterns.
• HubSpot offers basic in-app messaging through the Service Hub. Not purpose-built for onboarding.

These make sense if you're already paying for the parent platform. They don't make sense as standalone onboarding solutions.

Open-source and developer libraries compared

Developer libraries are the fastest-growing corner of the onboarding market, driven by React's dominance and developers' frustration with SaaS pricing. As of April 2026, five libraries see meaningful adoption, each with a distinct architecture and licensing model.

React Joyride

React Joyride has the largest install base at 603K weekly npm downloads as of April 2026. It's the default recommendation in most "how to add a product tour to React" tutorials. The API is prop-heavy: you pass a steps array and configure behavior through dozens of boolean props.

The main concern in 2026 is architecture. Joyride was written for class components. Its internal state management uses patterns that conflict with React 19's concurrent rendering. Multiple GitHub issues report step flickering and overlay glitches in strict mode. At 37KB gzipped, it's also the heaviest React-specific option, 4.6 times the size of Tour Kit's core.

Best for: Quick prototypes where bundle size and React 19 compatibility aren't concerns. Legacy codebases already using it.

Shepherd.js

Shepherd.js is the most capable framework-agnostic option, with 12.6K GitHub stars as of April 2026. It provides a clean imperative API and supports React, Vue, Angular, and Ember through wrapper packages. The tour engine is well-architected with good scrolling behavior and positioning logic.

The catch is licensing. Shepherd.js uses AGPL-3.0, which requires you to open-source any application that uses it unless you negotiate a commercial license. For internal tools, this might be fine. For commercial SaaS products, AGPL is usually a non-starter.

Best for: Teams building framework-agnostic or multi-framework applications where AGPL licensing isn't a concern.

Driver.js

Driver.js is the minimalist choice at just 3KB gzipped. It highlights elements and shows popover descriptions. No framework dependency, no complex configuration. As of April 2026, Driver.js has 22K GitHub stars and was last published in February 2026.

The limitation is what it doesn't do. No state persistence, no analytics integration, no multi-page tour support, no accessibility features beyond basic keyboard navigation. It's a highlighting library, not an onboarding platform.

Best for: Simple feature highlighting where you need the smallest possible script. Not suitable for complex onboarding flows.

Intro.js

Intro.js has been around since 2013 and remains popular for non-React projects. Like Shepherd.js, it uses AGPL-3.0 licensing with a commercial option at $9.99 per site. The API is stable but hasn't significantly evolved. Community TypeScript types exist but aren't maintained by the core team.

Best for: jQuery-era applications or server-rendered pages where a lightweight vanilla JS solution is needed.

Tour Kit

Tour Kit (the tool we built) takes a different approach: headless architecture with composable packages. The core logic ships at under 8KB gzipped with zero runtime dependencies. You install only the packages you need. Tours, hints, checklists, analytics, announcements, surveys, and scheduling are all separate packages.

The architecture is designed for React 18+ and 19 natively, with full TypeScript coverage and WCAG 2.1 AA accessibility built in. It works with any component library: shadcn/ui, Radix, Tailwind, or your own design system.

Honest limitations: Tour Kit doesn't have a visual builder (you write JSX). The community is smaller than React Joyride's 603K weekly downloads. It's React-only, so if you need Vue or Angular support, look at Shepherd.js or Driver.js. And it's a younger project with less battle-testing at enterprise scale.

Pricing: The core packages are MIT-licensed and free forever. Pro features (adoption tracking, advanced analytics, surveys, scheduling) cost $99 one-time. Not per month, not per MAU.

// src/components/OnboardingTour.tsx
import { TourProvider, useTour } from '@tourkit/react';

const steps = [
  {
    target: '#welcome-header',
    title: 'Welcome to the app',
    content: 'This tour shows you the key features.',
  },
  {
    target: '#sidebar-nav',
    title: 'Navigation',
    content: 'Use the sidebar to move between sections.',
  },
];

function App() {
  return (
    <TourProvider steps={steps}>
      <YourApp />
    </TourProvider>
  );
}

Get started with Tour Kit | GitHub

Performance impact: what every tool adds to your bundle

Performance is the comparison point that most directories ignore entirely. We measured the script weight each tool category adds to your application, because your users pay the cost whether the tool vendor mentions it or not.

Why does this matter? Google's Core Web Vitals research shows that every 100KB of JavaScript adds approximately 350ms to Time to Interactive on a median mobile device. A tool adding 500KB means your users wait nearly 2 extra seconds before they can interact with the page, including the onboarding experience itself.

SaaS tools load from external CDNs, which means they're also subject to DNS resolution, TLS handshake, and network latency. Developer libraries are bundled with your application and benefit from your existing CDN and caching strategy.

Licensing: the detail that bites you later

Licensing rarely makes the evaluation shortlist. It should. As of April 2026, onboarding libraries ship under MIT, AGPL-3.0, and various proprietary licenses. The differences have real consequences for commercial software.

AGPL-3.0 means: if your application uses an AGPL library and you distribute it to users (which includes serving a web app), you must release your entire application's source code under AGPL. For commercial SaaS products, this is typically unacceptable. Both Shepherd.js and Intro.js require negotiating a commercial license for proprietary use.

MIT means: use it however you want, commercially or otherwise, with no obligation to open-source your code. React Joyride, Driver.js, and Tour Kit's core packages all use MIT.

Accessibility across onboarding tools

WCAG 2.1 AA compliance is a legal requirement in many jurisdictions and a usability requirement everywhere. We tested keyboard navigation, screen reader compatibility, and ARIA attribute usage across tool categories. Most tools fail at least one criterion.

What accessible onboarding requires:

• Focus management that traps focus within the active tooltip
• Keyboard navigation (Tab, Escape, Arrow keys) for all tour controls
• ARIA live regions for screen reader announcements
• prefers-reduced-motion support for users who disable animations
• Sufficient color contrast (4.5:1 minimum) for all text
• Skip-tour mechanism accessible to keyboard-only users

Enterprise DAPs: WalkMe and Pendo have improved accessibility in recent updates but still inject overlays without consistent ARIA attributes. Focus management is inconsistent.

Mid-market SaaS: Appcues and Userpilot support basic keyboard navigation but lack comprehensive focus trapping. Screen reader support varies by tour type.

Developer libraries: Accessibility depends on the library. React Joyride provides basic ARIA attributes. Shepherd.js has improved keyboard support. Tour Kit includes WCAG 2.1 AA compliance as a core requirement: focus trapping, ARIA live regions, reduced motion support, and screen reader announcements are built into the component architecture.

For a deeper look at making product tours accessible, see our screen reader product tour guide and keyboard navigation guide.

How to choose: the decision framework

Picking onboarding software isn't about which tool has the most features. It's about matching the tool to your team's constraints. Here's the framework we recommend.

Choose an enterprise DAP if:

• Your organization has 500+ employees and multiple internal applications
• You have a dedicated digital adoption team (2+ people managing onboarding)
• Budget is $10K+ per year and you need SOC 2 / HIPAA compliance documentation
• You need employee training and customer onboarding in one platform
• Performance impact is acceptable because the alternative is no onboarding at all

Choose a mid-market SaaS tool if:

• Your product team needs to ship tours without developer involvement
• You have 1,000-50,000 MAU and can absorb $250-$1,500/month
• Speed-to-value matters more than long-term cost optimization
• You don't have frontend developers available for onboarding work
• You're okay with your onboarding logic living on a third-party server

Choose a developer library if:

• Your team includes React/frontend developers
• You want onboarding code in your codebase, version-controlled and testable
• Bundle size matters (you're tracking Core Web Vitals)
• MAU-based pricing would exceed $300/month at your scale
• You need full control over styling to match your design system
• Data privacy requirements mean you can't send user data to third parties

The budget crossover point

At approximately 5,000 MAU, the annual cost of a mid-market SaaS tool ($3,000-$10,000/yr) exceeds the one-time cost of a developer library plus the developer time to implement it. This crossover point is lower for teams that already have React developers. It's higher for teams that would need to hire specifically for onboarding development.

What's missing from other comparison directories

We researched every major onboarding tool directory before writing this page. Here's what they leave out:

Userpilot's "50+ Onboarding Tools" list covers SaaS tools comprehensively but ignores open-source libraries entirely. If you're a developer team evaluating React Joyride vs Appcues, their directory won't help.

Appcues' comparison pages are written to sell Appcues. They compare features Appcues has and omit categories (like bundle size and licensing) where Appcues is weak.

G2 and Capterra rank tools by user reviews, which skews toward tools with larger sales teams pushing review collection. Developer libraries rarely appear because their users don't leave G2 reviews.

This page exists because no single directory covers all three tiers with the data points developers actually need: bundle sizes, licensing terms, pricing at real MAU thresholds, and performance benchmarks.

Tools for specific use cases

Self-hosted and on-premise onboarding

If data sovereignty requirements mean no third-party scripts, your options narrow to developer libraries (which run entirely in your bundle) or Whatfix's enterprise on-premise deployment (which starts at $30K+ annually). See our self-hosted onboarding tools guide for the full breakdown.

Mobile + web onboarding

Appcues, Pendo, and UserGuiding offer mobile SDKs alongside web. Most developer libraries are web-only. Tour Kit is React-only (no React Native support currently). For mobile-first products, see our mobile + web onboarding tools comparison.

GDPR-compliant onboarding

SaaS tools that process user data on external servers create GDPR compliance obligations. Developer libraries that run client-side and don't phone home avoid this entirely. For the full analysis, see GDPR-compliant onboarding tools.

Developer tools and API products

Onboarding for developer tools requires a different approach: CLI walkthroughs, API playground tours, and documentation-integrated guides. See onboarding for developer tools for tools that handle this well.

The market in 2026: where onboarding software is headed

Three trends are reshaping the onboarding software market as of April 2026.

The unbundling trend. Companies that bought all-in-one platforms like WalkMe are breaking them apart, replacing the monolith with best-of-breed tools for each function. Tours from one tool, analytics from another, surveys from a third. Tour Kit's 10-package architecture was designed for exactly this pattern. See our unbundling article for the full analysis.

The code-ownership trend. Developer teams are pulling onboarding logic back into their codebases. The "just use Appcues" recommendation that worked in 2020 faces pushback in 2026 as teams realize their onboarding broke during every design refresh. One Hacker News commenter captured the sentiment: "The real cost of WalkMe isn't the license, it's the 3 FTEs you need to maintain it" (Hacker News, February 2026).

The AI-assisted authoring trend. Both SaaS tools and libraries are adding AI features: automated tour generation, smart targeting, content suggestions. But the underlying question remains: where does your onboarding logic live, and who controls it?

For deeper analysis, see how AI will change product onboarding and why the best onboarding software in 2026 is a React library.

Onboarding software best practices

Regardless of which tool you choose, these patterns separate effective onboarding from the kind that users skip after two steps. We've tested these across dozens of implementations and tracked the completion data.

Start with one flow, not ten. The most common mistake is building tours for every feature at once. Ship your signup-to-activation flow first, measure its completion rate, and iterate before adding secondary onboarding. A single well-tested tour outperforms five rushed ones.

Measure completion, not deployment. Shipping a tour isn't the goal. Track how many users finish it, where they drop off, and whether completing the tour correlates with activation. If your tour has a 30% completion rate, the tour is the problem, not the users.

Respect user intent. Don't show tours to returning users who already know the product. Don't interrupt users mid-task. Use targeting (by user role, signup date, or feature usage) to show the right guidance at the right moment.

Keep tours under 5 steps. Completion rates drop 15-20% per step beyond five (Appcues benchmark data). If your onboarding requires more steps, break it into multiple shorter flows triggered by user behavior.

Own your onboarding code. Whether you use a SaaS tool or a library, make sure your onboarding logic is version-controlled, testable, and survives a UI redesign. Tours built with CSS selectors break. Tours built with semantic targets (data attributes or component refs) don't.

For more patterns, see our product tour UX patterns guide and product tour antipatterns to avoid.

Get started with Tour Kit

Tour Kit is the developer library we built for teams that want code-first onboarding with composable packages.

npm install @tourkit/core @tourkit/react

• Documentation
• GitHub
• MIT core (free) | Pro features: $99 one-time

FAQ

What is the best onboarding software for startups?

Tour Kit and Driver.js are the best onboarding options for startups in 2026. Tour Kit provides tours, checklists, hints, and analytics at under 8KB gzipped with MIT licensing. Driver.js is lighter at 3KB but lacks analytics. Both avoid the MAU pricing that makes mid-market SaaS tools expensive as you scale.

How much does onboarding software cost in 2026?

Onboarding software costs range from $0 (open-source libraries) to $100K+ per year (enterprise DAPs) as of April 2026. Mid-market SaaS tools like Appcues and Userpilot start at $249 per month for 2,500 MAU and scale to $2,000+ at 100K MAU. Developer libraries like Tour Kit charge $0-$99 one-time. The right choice depends on your team's technical capacity and user count.

Is open-source onboarding software reliable enough for production?

React Joyride has 603K weekly npm downloads and powers production onboarding at thousands of companies as of April 2026. Shepherd.js has 12.6K GitHub stars. Open-source onboarding libraries are production-ready, but you should evaluate maintenance frequency, React version compatibility, and licensing (AGPL vs MIT) before choosing.

What is the difference between a DAP and a product tour tool?

A digital adoption platform (DAP) like WalkMe or Whatfix is a full-stack enterprise solution covering employee training, customer onboarding, process automation, and analytics. A product tour tool like Appcues or Tour Kit focuses specifically on in-app user guidance: tours, tooltips, checklists, and announcements. DAPs cost $10K-$100K per year and add 200-500KB to your page. Product tour tools cost $0-$2,000 per month and add 3-180KB.

Can I switch from a SaaS onboarding tool to an open-source library?

Yes, but budget 2-4 weeks for migration depending on the number of tours. The main work is re-implementing tour logic in code (which was previously stored in the SaaS tool's visual builder). Tour Kit provides migration guides from Appcues, React Joyride, Shepherd.js, and Userpilot.

Which onboarding tools work with Next.js App Router?

Tour Kit and React Joyride both work with Next.js App Router as of April 2026, though both require 'use client' directives since product tours are inherently client-side. SaaS tools like Appcues work via script injection regardless of framework. See product tour tools for Next.js App Router for the full breakdown.

What onboarding software is GDPR compliant?

Developer libraries that run entirely client-side (Tour Kit, React Joyride, Driver.js) don't send user data to external servers, making GDPR compliance straightforward. SaaS tools process user data on their servers and require Data Processing Agreements (DPAs). Enterprise DAPs like WalkMe and Pendo offer GDPR compliance documentation but add third-party data processing obligations. See our GDPR compliance guide.

How do I measure the ROI of onboarding software?

Track four metrics: tour completion rate (benchmark: 68% average per Appcues), time-to-value (time from signup to first key action), activation rate (percentage of signups reaching the "aha moment"), and support ticket volume pre/post onboarding. Companies with structured onboarding see 50% greater new-user retention according to Mixpanel benchmark data. See our ROI calculation guide for formulas and code examples.

Related articles

Pillar PagesApr 12, 2026 · 15 min read

Headless onboarding: what it means, why it matters, and how to start

What headless onboarding is, why it beats styled tour libraries for design system teams, and how to implement it with code examples.

Read article

Pillar PagesApr 12, 2026 · 23 min read

Onboarding metrics explained: every KPI with formulas (2026)

Master every onboarding KPI from activation rate to NPS. Each metric includes the formula, benchmark data, and React tracking code.

Read article

Pillar PagesApr 12, 2026 · 15 min read

The open-source onboarding stack: build your own with code

Assemble a code-first onboarding stack from open-source tools. Compare tour libraries, analytics, and surveys to own your onboarding.

Read article

Pillar PagesApr 12, 2026 · 16 min read

Product tour best practices for React developers (2026)

14 product tour best practices for React. Code examples, accessibility, state management, and performance from real implementations.

Read article