Demo Maker Pro is a Windows application for creating interactive training, standard operating procedure, and software walkthroughs from browser and desktop workflows.
This page is intended for IT, information security, risk, and procurement teams evaluating the application. It explains installation, network connections, capture behavior, local storage, HTML export, and optional cloud publishing.
Key point: Demo Maker Pro is local-first. Projects are stored on the user's computer. Exporting creates a self-contained HTML file without uploading the demo to Demo Maker Pro. Cloud hosting is used only when the user deliberately selects Publish.
| Item | Details |
|---|---|
| Product | Demo Maker Pro |
| Publisher | qwerty2 LLC |
| Supported operating systems | Windows 10 and Windows 11 |
| How it works | The Windows app is the editor, where demos are recorded, edited, exported and published; it records desktop programs on its own, and for web-based systems the Chrome or Edge extension captures each click and sends it to the app on the same computer |
| Browser support | Google Chrome or Microsoft Edge for browser recording |
| Desktop recording | Available without a browser extension |
| Local project storage | Projects are saved on the user's computer |
| Export format | One self-contained HTML file |
| Cloud hosting | Optional, used only when the user selects Publish |
| Viewer requirements | A modern web browser, with no Demo Maker Pro account, extension, licence, or installation needed to view a finished demo |
Demo Maker Pro provides two separate distribution options. Exporting and publishing are different actions.
| Action | Where the demo is stored | What Demo Maker Pro receives |
|---|---|---|
| Save or edit a project | On the user's Windows computer | No captured demo content, only the licence verification described below |
| Export HTML | One self-contained HTML file on the user's computer | No captured demo content, though the application may complete a licence and entitlement check before creating the export |
| Publish | Uploaded to Demo Maker Pro cloud hosting, with a link on demos.demomakerpro.com | The complete published demo |
Selecting Export HTML creates a single self-contained HTML file on the user's computer. Exporting does not publish or upload the demo. The finished HTML file:
The exported file does not contain its own authentication system. If access must be restricted, the organization should host it behind its existing authentication and access controls.
Creating a new export may require the installed application to contact Demo Maker Pro for a licence and entitlement check. This authorization request does not upload the project or the exported demo.
Selecting Publish is a separate, optional action. It uploads the finished demo to Demo Maker Pro cloud hosting and creates a link on demos.demomakerpro.com. Publishing is never required to export or self-host a demo.
Published demos are not password protected. They are not publicly listed, and each link contains a long random identifier. However, anyone with the link can open and forward it. Published links should therefore be treated as public and should not contain confidential, regulated, or operationally sensitive information.
By default, a published demo tells search engines not to index it. An author can turn on Search & AI discovery for an individual published demo, which allows search engines and AI assistants to index it and adds a text version of its steps to the published page. The setting is off by default and has no effect on exported HTML files.
Organizations that need their own authentication, retention policies, or access controls should use HTML export and host the file within an approved environment.
Demo Maker Pro is available for Windows 10 and Windows 11 and is published by qwerty2 LLC.
The Windows installer is digitally signed by qwerty2 LLC so administrators can verify its publisher before installation.
Browser recording also requires the official Demo Maker Pro extension:
Desktop recording does not require a browser extension.
Installing the application or extension does not begin recording. Capture occurs only after the user deliberately starts a recording session.
| Connection | When used | Purpose |
|---|---|---|
| Outbound HTTPS, TCP port 443 to demos.demomakerpro.com | Application activation and normal application use | Licence activation, periodic licence checks, export authorization, optional cloud publishing, and management of hosted demos |
| Local loopback on 127.0.0.1, port 47311 | Browser recording only | Connects the browser extension to the Demo Maker Pro desktop application on the same computer |
| Resources used by the recorded website | Browser recording only | Retrieves images, fonts, and styles referenced by the page so they can be included in the local demo |
No inbound network ports or inbound firewall rules are required.
Port 47311 listens only on the local loopback interface. It is not exposed to other computers on the network.
When the extension retrieves images, fonts, or styles for a recording, those requests go only to the recorded website or the servers it loads files from, the same way the browser loads the page itself. If a file can only be read with the user's existing sign-in to that website, the browser's cookies for that website can be included in the request. Nothing from these requests is sent to Demo Maker Pro.
The finished exported HTML file makes no network connections. A cloud-published demo requires internet access because it is served from Demo Maker Pro hosting.
Licence activation and verification send:
Licence verification does not send project contents, captured pages, desktop screenshots, exported HTML, browsing history, or cookies.
After successful activation, the application can continue operating for up to three days without an internet connection. Reconnecting refreshes that period.
Browser recording is performed through the Demo Maker Pro extension for Chrome or Edge while the desktop application is open and licensed.
Nothing is captured merely because the extension is installed. Recording begins only after the user selects Start Recording and ends when the user selects Stop Recording.
While recording, each captured step can include:
The extension does not request the browser's history or cookies permissions, and it does not read the user's browsing history or cookies.
Captured steps are stored in the extension's local storage and transferred to the Demo Maker Pro application over the local loopback connection at 127.0.0.1. Captured demo content is not sent to Demo Maker Pro during recording.
Steps remain in the extension's local storage until the user selects Clear steps or removes the extension.
Desktop recording operates from the Windows application and does not require a browser extension.
Each time the user presses the capture key, Demo Maker Pro captures the application window in front, or a specific window the user selected when starting the session. The step contains only that window. Nothing else on the screen is kept. Anything displayed on top of that window at that moment, such as an open menu or a notification, appears in the step.
Each step also records the application name, window title, and window dimensions needed to create the step.
The capture key is registered only while a desktop recording session is running. Desktop recording does not save anything outside the captured window, and it does not read:
Desktop captures are stored inside the local Demo Maker Pro project. They are uploaded only if the user deliberately publishes that project.
Project files and exported HTML files are stored in locations selected by the user. Demo Maker Pro does not hold a copy unless the user publishes the demo or deliberately provides files for support.
The organization controls the storage, retention, backup, access, and deletion of locally saved projects and exported HTML files.
A user can delete a published demo at any time from File > My Cloud Published Demos. Deleting the demo removes the hosted files and disables the link.
People viewing a finished demo do not need:
A viewer opens the finished demo in a modern web browser. For an exported demo, access is determined entirely by where the organization stores or hosts the HTML file. For a cloud-published demo, anyone possessing the link can view it.
Publishing to cloud hosting is optional. If your organization prefers that demo content never leaves its own systems, export each demo as a self-contained HTML file and host it on your intranet, learning management system, SharePoint or document portal. The file makes no external connections and works under whatever access controls you already use.
A recording captures whatever is on screen at each step, and Demo Maker Pro does not redact anything automatically, so review each demo before you share it.
No. Recording begins only after the user starts a browser or desktop recording session. Installing or opening the application does not capture activity by itself.
No. Browser steps are transferred to the desktop application over a local loopback connection. Desktop captures are stored in the local project. Captured content is uploaded only when the user deliberately selects Publish.
No. Export HTML creates a self-contained file on the user's computer. Exporting and publishing are separate actions.
No. The finished exported file works offline and makes no connections to Demo Maker Pro.
The application may contact Demo Maker Pro to verify the licence and export entitlement before creating a new export. Only licence verification information is transmitted. The project and exported demo are not uploaded.
Yes. Cloud publishing is optional. An organization can save projects locally, export self-contained HTML files, and host those files entirely within its own environment.
Yes. The exported file can be hosted on an intranet, LMS, internal web server, or another environment protected by the organization's existing access controls. Authentication is provided by that environment, not by the HTML file itself.
No. Published demos are not password protected. Anyone with the link can view and forward it. Treat a published link as public.
No. No inbound network ports or inbound firewall rules are required.
Yes. The extension transfers recorded steps directly to the desktop application running on the same computer.
No.
Yes. If sensitive information is visible in the recorded page or application window, it can become part of the captured step. Use demonstration accounts, synthetic information, and an internal review process before sharing a demo.
For security questionnaires, installation assistance, network questions, or requests for additional technical information, contact support@demomakerpro.com.
Also review the Demo Maker Pro Privacy Policy for complete information about data handling and service providers.