Appearance
Sharing your demo
Every built VM has a Share this demo card on its page, with three tabs, easiest first.
Share link
A full-page demo hosted by us:
https://build.demoshell.com/launch?snapshot=acme/web:helloREADME badge
Markdown for GitHub: your demo's screenshot, linking to the hosted demo.
md
[](https://build.demoshell.com/launch?snapshot=acme/web:hello)READMEs cannot run scripts, so the link is the only way to refer to the demo. The image is the screenshot taken when the VM was last built.
Embed on your site
A small script tag that runs the demo inside your own page. See Embedding.
Link and badge work on every plan. Putting the demo inside your own site is part of the paid and open-source plans.
Public and private
Demos are public by default: anyone with the link can run them and they be embed on any website.
A private demo needs the project's embed key, and it only runs on the domains you list for that key. The share panel handles both: it puts the key in the snippet and links you to the domain list.
Keys are meant to be published
A pk_ key is written into your page's source and thus exposed to visitors. That is not a problem as that key is not the secret itself, it's rather a public reference to a limited record on Demoshell.
Embed keys live on the project level, not on one VM, and are managed under Keys in the account menu. Revoking one stops every embed that was using it.
A private demo's share link and README badge carry the key too, so anyone holding the link can run the demo. Revoking the key deactivates those links as well.
What visitors can see
Everything a visitor does happens in their browser and disappears when the tab closes.
The VM's page shows how many times the demo was loaded per day over the last 30 days, and, if it has a guide, how many people started and finished it.