Usertour
Open-source user onboarding platform — in-app product tours, checklists and surveys
Usertour is an open-source user onboarding platform: you build in-app product tours, checklists, launchers and surveys against your own running app, target them using your own user attributes and events, and either self-host the whole thing with Docker or use the project's hosted cloud. It positions itself as the open alternative to Appcues, Userpilot, Userflow and Chameleon. For a founder it is a conversion tool pointed at people who are already inside the product, which makes it genuinely useful on activation and completely silent on demand.
What Usertour is
Usertour (github.com/usertour/usertour) is an open-source platform for building the guided parts of a product's first session. Its README describes creating in-app product tours, checklists and surveys in minutes, and names the commercial tools it is positioned against: Appcues, Userpilot, Userflow, Userguiding and Chameleon. It is written in TypeScript, had 2,131 stars when this page was written, and runs either from the project's Docker Compose file on your own infrastructure or on its hosted cloud. The licence takes one line: community code is MIT, while directories marked as enterprise carry a separate enterprise licence.
- Works with any browser app The README's framing is that if your app runs in a browser it integrates, and it explicitly covers both single-page and multi-page applications.
- Targeting on your own data You define custom user attributes and track events, then segment who sees which flow — so a checklist can be shown to the people who have not finished setup rather than to everyone.
- Environments and version history Production and staging live in one account, and changes to a flow are tracked with who made them and when. That is the difference between a tool a team can use and a script somebody once pasted in.
- Themed to your product Text, button colours, font family and size are adjustable, and multiple themes can coexist so different flows do not have to look identical.
- Flow analytics Views and completion rates per flow, plus step-level data intended to surface exactly where people get confused or abandon.
Where it fits a founder's growth stack
A tour is a conversion tool and it acts only on traffic you already have. That places it squarely in the activation stage, between someone signing up and someone getting a first real result, which is a high-leverage place to work precisely because everything upstream of it has already been paid for. It also means the tool is the wrong purchase for two very common problems: if people arrive on your site and do not sign up, see turning visitors into signups; if nobody arrives at all, see SEO for a brand-new site. Neither improves because a tooltip appeared inside the product.
The honest tension in this whole category is worth naming before you install anything. A product tour is what you reach for when an interface is not self-evident, which means it can quietly become the way you postpone making the interface self-evident. The tool cannot tell you which of those you are doing — though its own analytics can. A step where a large share of people abandon the flow is usually not a step that needs a better tooltip, it is a step that needs to stop existing. Read completion rates as a bug report about the product rather than as a scoreboard for the tour.
The step we deleted instead of explaining
First-hand note from building AgentCeres — the AI Growth Officer at agentceres.com. The largest onboarding improvement we have shipped removed a decision rather than annotating it. Our setup flow used to ask a new customer which specialists they wanted before anything could run, which is exactly the sort of screen a product tour exists to explain. We deleted the screen and now set the full team up by default. Nobody had to understand the choice, because nobody had to make it.
- Is the step necessary at all? A screen you can delete beats a screen you can explain, every time.
- Is the friction comprehension or time? Guidance fixes the first and does precisely nothing for the second.
- Can the product show rather than tell? Delivering one real result before configuration teaches faster than any description of that result.
- Will the flow survive the next release? A tour anchored to an interface that changes weekly goes wrong silently, and wrong guidance is worse than none.
The second of those is the one we got wrong for longest. The friction that mattered in our own signup was never that people misunderstood a screen — it was that they waited while infrastructure was built for them, and no amount of in-product guidance shortens a wait. The fix was infrastructural: workspaces are now warmed in advance so the final step resolves in seconds instead of minutes. None of this is an argument against Usertour, which is a clean and genuinely self-hostable implementation of a real category. It is an argument for spending the diagnosis first, because a tour pointed at the wrong kind of friction produces a beautifully guided version of the same problem.
FAQ
- Is Usertour free?
- The community code is MIT-licensed and self-hostable from the repository with a Docker Compose file, so there is no software cost if you run it yourself — you pay for the infrastructure and the time to operate it. The LICENSE file carves out directories marked as enterprise, which are governed by a separate enterprise licence, and the project also runs a hosted cloud as its paid managed option. For most founders the practical question is whether operating another service is worth avoiding a subscription.
- Usertour versus Appcues or Userpilot — what is the trade?
- They do the same core job, and the README positions Usertour explicitly against that set. The trade is the familiar one: the commercial tools are more polished and there is nothing to run, while the open-source option gives you the data, the ability to self-host on your own domain, and no per-seat or per-active-user pricing as you grow. Choose on whether owning the deployment is worth real operational work at your stage, not on the feature list, which converges quickly in this category.
- When is a product tour actually the right fix?
- When the step is genuinely necessary, the interface is as simple as it can be, and people still do not know what to do next — a real gap in knowledge rather than in design. Tours are also good at surfacing a capability people would never find on their own, and checklists are good at giving a multi-step setup a visible finish line. They are a poor fix for a step that should not exist, for a wait, or for an interface nobody has tried to simplify yet.
You built it. Now grow it.
AgentCeres is a managed AI marketing team — specialists draft the SEO, social, and outreach that fill your links, you approve what ships. 14-day free trial, from $39/month.