Demo Maker Pro exports a finished interactive demo as one self-contained HTML file. You put that file wherever you like (an intranet share, an internal web server, a USB stick, a client's own hosting) and it runs there without us.
Self-hosted interactive demo software means the finished demo is a file you hold, not a page on a vendor's server. In Demo Maker Pro that file comes from Publish > Export HTML, which writes a single self-contained HTML file. Everything the demo needs is inside it. Host it anywhere, embed it, or email it. It does not contact our servers when someone views it, and it keeps working regardless of your subscription.
Viewers need no account, no license, no extension and no install. They open the file in a browser and click through.
This is the one thing we could not find anywhere else. None of the competing platforms we checked on October 2, 2026 documents exporting a self-contained HTML file the customer hosts. Several document an "offline" feature, and almost always it is the vendor's own player, which is a different thing entirely. Reprise is the partial exception: it says Tours customers can host their own downloaded demos, without saying what format the download is. The rest of this page explains why the difference matters and gives you the exact questions to put to any vendor in writing.
Vendors use the word for all four. Only the last one is self-hosting.
The demo lives on the vendor's infrastructure. A CNAME points your domain at it, so the address bar reads demos.yourcompany.com. The branding is yours; the hosting is not. Point the DNS somewhere else, or stop paying, and the page stops resolving.
The demo appears inside your own page, which feels like hosting it. It is not. The iframe loads the demo from the vendor at view time. Your page is a window onto their server, and it goes blank if that server does.
An offline player or cached web app can support viewing without an internet connection. Check whether its license, saved content, and redistribution rights allow continued use after cancellation, and whether it depends on vendor services.
Demo Maker Pro exports one self-contained HTML file with the captured content and playback code included. Viewers open it in a modern browser without installing a separate player. The exported demo does not require Demo Maker Pro hosting or an active subscription to remain usable.
The distinction is not academic. Options 1 and 2 leave a live dependency between your demo and someone else's business, and option 3 may. Option 4 removes it.
"Offline" sounds like independence. Read the documentation and it usually is not. What is being described is a way to view a demo when the network is unavailable, through software the vendor wrote, on terms the vendor sets.
Here is what the vendors' own materials describe, as of October 2, 2026:
Each of those is a reasonable feature. None of them is documented as a single file you own. A progressive web app is still served and updated from an origin you do not control. A hosted player at the vendor's URL is a hosted page whose content happens to be cached. A downloadable player is an installable program your viewer must obtain, run and keep, which is a support conversation with every person you send the demo to, and an approval conversation with anyone whose laptop is locked down.
The test we would apply is simple: if the vendor switched off tomorrow, would this still open? For a self-contained HTML file the answer is yes, because there is nothing to switch off. It is a document.
From the vendors' own materials, checked October 2, 2026. "Not documented" means their materials do not describe it, not that it is impossible.
| Platform | Documented offline option | What that offline option is | Self-contained HTML file you host |
|---|---|---|---|
| Demo Maker Pro | Not applicable, the export is already a local file | One HTML file, opened by any browser | Yes, Publish > Export HTML |
| Navattic | Yes, on Enterprise | A progressive web app | Not documented |
| Supademo | Yes | A hosted Offline Demos Player at their URL | Not documented |
| Walnut | Yes, as a paid add-on | A download to the presenting device | Not documented |
| Arcade | Yes, on Enterprise | An offline copy at its own Arcade URL | Not documented |
| Reprise | Yes | A downloadable player application | Not documented as a single file; downloaded Tours demos can be self-hosted |
| Storylane | Yes, from Growth | A secure download link for offline viewing | Not documented |
| Guideflow | Yes, from Growth | A copy saved locally from the Guideflow workspace | Not documented |
| Tourial | Not documented | Not applicable | Not documented |
A fuller feature-by-feature breakdown is on the interactive demo software comparison.
Because it is one file with no external dependencies, the list of places it works is roughly "anywhere a browser can reach a file".
If you would rather not host anything, Publish > Publish to DemoMakerPro gives you a link on demos.demomakerpro.com instead, and re-publishing the same project updates that demo in place so a link you already sent stays current. The two are not exclusive, the same project can be exported and published. Note that a published link is unguessable but not password protected, so treat it as public.
Double-clicking the file from Explorer can look soft. Opened straight off the filesystem, an exported demo may render less crisply than it should. Serve it over http (from your intranet server, a local static server, or any normal web host) and it looks correct. Demos published to demos.demomakerpro.com are unaffected. This is the single most common surprise and it is worth knowing before you send the file to a client.
Updates replace the file. To update a self-hosted demo, export the revised HTML and replace the file on your server. Keeping the same file URL lets existing links continue to work. If viewers received downloaded copies, send them the revised file. Republishing updates a demo hosted by Demo Maker Pro in place.
Creating demos needs a live license. When a paid plan ends you can no longer record, edit, export or publish. HTML demos already exported to your computer keep working (that part is unconditional) but you cannot make new ones. Demo Maker Pro also needs the desktop application, which is Windows only.
Self-hosting is not access control. An HTML file has no login. Whoever can reach the file can watch the demo, so put it behind whatever authentication your intranet or web server already applies.
Ask by email, not on a call. The answers to these separate the four meanings above in about two minutes.
Ask for the exact output of the export function: a filename and an extension. "You can export your demo" is not an answer. "It produces one .html file" is.
Does it fetch anything from your servers, assets, fonts, scripts, analytics, a license check? Ask them to confirm in writing that it makes no outbound requests, then verify it yourself with the browser's network tab.
Do demos we already exported keep working, indefinitely, with no further payment? Does "offline" mean a player we install, and does that player still work once the account is closed?
Two more worth adding: can we give the file to a client as a deliverable they host themselves? and which plan is this on? An offline capability that exists only on a custom-priced Enterprise tier is not a feature you have, it is a feature you can apply for.
Demo Maker Pro's answers: one self-contained HTML file, no outbound requests, keeps working after cancellation, yours to hand over, and HTML export is on every plan from $149/month, see pricing and the docs.
Record a real workflow, choose Publish > Export HTML, and see how a demo behaves when it is a file you hold rather than a page someone else serves.
Request trial