Regale Studio
Where the demo gets built
Studio is the desktop application your team authors in. Capture the real product two ways, at the operating-system level or straight from HTML, then compose, publish and keep the whole library current as the product moves.
Capture it. Compose it. Publish it. Keep it current.
Capturing a product once is easy. Composing it into something a seller can run, and keeping it current through four releases, is the work. It is also the work you can hand to the AI agent your company already runs, over Regale MCP, which is what changed the economics of all of this.
- Step 01
Capture
Screen capture and HTML capture are both native to Studio, and both publish to the same player and the same library. Record the real product at the operating-system level: shell, dialogs, native desktop software, mobile, and web.
- Step 02
Compose
Assemble pages, branches, presenter notes and theme. Branching and notes are authored once and used by every delivery mode, so a demo built for a live call already works as an unattended one.
- Step 03
Publish
Hand the finished build to the Portal: versioned, access-controlled and draft by default. One artifact, one source of truth.
- Step 04
Keep it current
Then the product ships again. Project-wide replace re-versions, rebrands, re-localizes or brings a whole project current in one pass rather than page by page. This is the step that decides whether the library is still an asset in year two.
Content that keeps up with the roadmap
Demos shouldn’t be the slowest thing you ship. Most demo libraries are not abandoned on purpose; they are abandoned two releases after the person who built them moved on, and nobody could justify updating forty of them by hand.
- Screen capture and HTML capture. Both native to Studio, publishing to the same player and the same library, so the method is a per-project decision your audience never sees
- OS, desktop, mobile and web coverage. Surfaces a browser extension structurally cannot reach
- Project-wide replace. Rebrand, re-version, re-localize or bring an entire demo current after a release, in one pass
- Branching and presenter notes authored once, used by every delivery mode
- Live-browser capture and staging for products that move week to week
Your own AI agent can do all of this, over Regale MCP.
The method is your decision. The buyer sees the same thing either way.
Screen capture
Records the product as it actually runs, at the operating-system level. Installers, file dialogs, native admin consoles, mobile flows and anything else that never lived in a browser tab. This is what over two decades of capture engineering went into, and it is the one a browser extension structurally cannot reach.
HTML capture
Native to Studio, publishing to the same player and the same library as screen capture. The captured page stays live markup, so text, data and branding can be changed later without going back and capturing it again.
Both methods are native, both publish to the same player, and both land in the same library. Which one a project uses is a production decision your audience never sees.
Bring us the product surface nobody has managed to demo properly
We will walk your team through capture on something of yours, not something of ours.