The overlay marketplace: free to start, premium when you need it

The overlays are what make a demo feel like your product instead of a generic tour. MyAISE's overlay marketplace is a growing catalog of themes, overlay animations, and procedural Three.js transitions — built to match a brand and drop straight into any demo. And on Solo and AI SE you don't just pick from it; you design your own, with any AI.

A catalog that matches your brand

Browse the marketplace from the studio and choose the look that fits — a glassy theme, a cinematic dissolve, a snappy slide-up. Recolor any theme to your palette and it carries across every overlay decoration: cards, outlines, hotspots, the Return-to-Demo pill, video bubbles, callout arrows. Pick it, and it just works in your next demo. The catalog keeps growing — and on Pro or Team, you can add to it yourself.

Solo & AI SE: design your own, with any AI

On Solo and AI SE the marketplace stops being a catalog you pick from and becomes one you author. Download the design kit — a self-contained HTML file that renders every overlay with the exact delimited blocks MyAISE reads back in — open it in whatever AI you already use (Claude, ChatGPT, a local model; bring your own AI, we don't sit between you and it), and describe the look: "dark plates, a neon hairline, a paint-wipe in our purple." It edits the kit; you re-import the file; MyAISE turns the result into real Library assets — a theme, overlay animations, and one or more Three.js transitions.

The file is data, and the shader gets compiled

Handing a tool an HTML file an AI just wrote should make a security-minded person nervous, so the importer never renders or executes the kit. It extracts only the delimited MYAISE:<NAME>:START … :END blocks by regex; the theme becomes CSS variables, animations become keyframes, each transition becomes a scene. Every block is then verified: CSS through a parser that rejects network loads and host-page selectors; transition JS through an AST gate limited to an allowlist of runtime globals — no fetch, no document, no eval.

Then the part that took us a black-screen incident to learn: with WebGL, broken is silent. A shader that uses a reserved word or drops a semicolon doesn't throw — it fails to compile, falls back to black, and the surrounding JavaScript runs happily rendering nothing. So the verifier compiles the shader in a real headless WebGL context and hooks the compile callback. If the GLSL won't compile, the asset is rejected as shader_compile_error with the exact line — at import time, where you can hand it back to your AI and say "active is reserved, rename it." It never becomes approved, so it can never reach a prospect.

"Pick a look that matches your brand — or, on AI SE, describe one to your own AI and import it back, verified before it ever reaches a prospect."

— The overlay marketplace + AI design kit

Open the marketplace in the studio and find a look that fits — download the Mac app to start. On Solo and AI SE, the design kit turns "find a look" into "make one": restyle a kit in your own AI and import it back, sandbox-verified so a broken shader never reaches a prospect.