Onboarding without third-party scripts: private, self-hosted product tours
Most onboarding tools load a vendor’s script on every page of your app. There is another way to build it, with trade-offs worth knowing before you choose.

The usual way to add product tours to a web app is to paste a vendor’s snippet into your layout. From then on, every page your users open also loads code from that vendor’s servers, and tells those servers who is looking.
That is a reasonable trade for many teams. It is a poor fit for others: apps that handle sensitive data, teams with a strict content security policy, companies whose customers ask where every byte goes. This post describes the other architecture, the one Stepsome uses, including what it costs you.
What a third-party onboarding script means in practice
None of this is specific to one vendor. It follows from how hosted onboarding tools are built:
- Another origin on every page. The script and the tour content are fetched from the vendor at page load. It needs an entry in your content security policy, and it is one more thing that has to be up for your page to behave as designed.
- Your users’ data goes to the vendor. To target tours and report on them, the tool receives user ids, traits such as plan or role, and what each person saw and clicked.
- The script runs inside your app. Any script on your page can read what is on that page. You are trusting the vendor’s security as much as your own.
- One more name on the list. If you keep a record of the companies that process your customers’ data, the onboarding vendor goes on it, and customers who review that list will ask about it.
Whether any of that is a problem depends on your product and your customers. This is not legal advice; ask your own counsel what your obligations are.
The alternative: one file you host yourself
Stepsome does not host anything. What your visitors get comes from a single file that you put on your own website: the site file, named stepsome-<your-site>.js. It contains the runtime and everything you set to Published.
<script src="/stepsome-<your-site>.js" defer></script>
The file is self-contained. It has no dependencies, it loads nothing from another server, and it only draws something when a tour or widget should show. Because it is served from your own origin, there is no extra script origin to allow in your content security policy.
There are two exceptions, both of your own making: if you put a YouTube, Loom or Vimeo embed in a popup, the visitor’s browser loads that player from its provider, and an image you add by link is fetched from wherever you linked it. Uploaded images become part of the site file itself.
Publishing works in three moves:
- Publish. Set the tours and widgets that should go live to Published.
- Download. The Install page builds one site file with everything that is published.
- Deploy. Put the file in the public folder of your website and ship it like any other asset.
Where your tours live while you build them
The authoring side follows the same idea. Stepsome is a Chrome extension. Tours, widgets, themes and settings are kept in Chrome’s extension storage on your computer. There is no account, and none of it is uploaded.
That has practical consequences you should know up front:
- Another computer, or another Chrome profile, starts empty. You move your work with a workspace file.
- Removing the extension from Chrome removes its data. Export a backup first: Settings → Team → Export workspace gives you
stepsome-workspace.json. - The workspace file holds every site, tour, widget and setting. API keys, analytics read keys and your profile are left out on purpose.
Two things do talk to an outside service. The license check sends your license key and a random installation id to Stepsome’s billing server, which is how Pro keeps working; payments go through Stripe. And the optional AI copywriter rewrites step texts with your own Anthropic or OpenAI key, sending them only to the provider you picked. If you never set a key, no step text is sent anywhere. Neither ever sees your app or your visitors.
Analytics on a server you control
Measuring onboarding normally means sending visitor behaviour to someone. Here that someone is you. The collector is a small service that ships with Stepsome in two versions:
| Option | What you run |
|---|---|
| Cloudflare Workers | A Worker with a D1 database, deployed with three wrangler commands. |
| Your own server | A Node server (Node 22 or newer, no dependencies) with one SQLite file. Put it behind HTTPS. |
The dashboard only reads from the collector. A few details matter for privacy:
- The read key stays in your browser. It never ends up in the site file; only the collector address does.
- Do Not Track is respected. Visitors with Do Not Track or Global Privacy Control switched on are never sent to the collector.
- You can erase a person. On the Users page, click the person and then Delete their data. That removes everything the collector stored about them and cannot be undone.
- The receiving address is public, as with any analytics that runs in the browser. Limit it to your own websites with the collector’s
SITESsetting.
If you would rather not run anything, Stepsome also sends its events to PostHog, Plausible, Google Analytics, Umami or Mixpanel when your app already loads one of them. What to do with the numbers is covered in How to measure user onboarding.
The trade-offs, plainly
Keeping everything on your side means some conveniences of hosted tools are missing. Better to know before you start:
- Changes go live with a deploy. Edited text, a new tour or an item set back to Draft all need a new download of the site file. Until then your website keeps showing the previous file. The dashboard tells you when your file is out of date, but it knows what you downloaded, not what you deployed.
- Scheduled items still need a deploy to start. A promotion ends by itself on its last day; starting it requires the file that contains it to be live.
- No shared team accounts and no live sync. You share by sending a workspace file. If two people change the same tour, the last import wins.
- No share links. A tour or a video cannot be opened from a Stepsome address, because there is none.
- “Seen” is remembered per browser. The same person on another device sees a first-visit tour again.
For a team that already deploys several times a week, the first point is a non-issue: the site file is one more asset in the pipeline. For a team where marketing wants to change a tooltip without involving anyone who can deploy, a hosted tool will feel smoother.
Is this the right setup for you?
It probably is when:
- your customers or your security team ask which third parties run code in your app;
- you want user traits and behaviour to stay in your own infrastructure;
- you deploy often and are comfortable adding one file to your public folder.
It probably is not when several non-technical people need to edit the same tours at the same time, or when you need changes live within minutes without a deploy.
The short version of how Stepsome handles data is on the home page under Private by design. To see what building the onboarding itself looks like, start with User onboarding for SaaS: a practical guide for small teams.


