Point it at a URL.
Get the whole demo kit.
my_demo_ turns any URL or local build into scroll-demo videos, GIFs, stills and device-frame reels, all captured and rendered on your own machine. No demo-hosting platform, no account, no share link sitting on someone else's server. The files are yours.
A product demo is a preview of your unreleased work.
The build that isn't public yet. A client site under NDA. A feature you haven't shipped. Make that demo with a cloud platform and it gets uploaded to their servers, wrapped in an account, and served from a share link you don't control. my_demo_ captures on your machine and hands you the files. Point it at a local build and nothing leaves at all.
It renders on your machine
my_demo_ loads the page, then captures and renders every frame locally. There is no demo-hosting service in the loop and nothing to harvest.
Demo work that isn't live yet
Aim it at a local build, a folder, or localhost and nothing leaves your machine. Polished demo assets of unreleased work, with zero exposure to a third party.
Own the files, not a share link
The output is plain video, GIF and image files on your disk. No cloud library, no link that expires, nothing that gets paywalled later.
No account, no seat
Install it and capture. There is no sign-up, no workspace on someone's server, no per-editor licence between you and your own demo.
One URL in. A whole kit out.
The scroll is a real eased animation inside the page, so scroll-triggered animations, intersection observers and lazy-loaded images all fire and get captured. Mobile uses a true device profile, not a shrunk window. From a single link you get:
Not just private. A better demo maker.
Privacy is the foundation. The reason makers will actually switch is that my_demo_ does more, and it bends to how you ship.
Cadence you control
Dial the scroll speed, add still beats at the top and bottom, fade in and out. The demo moves the way you want it read.
Composed, not raw
Drop in background music, brand it with a logo watermark, and hide the noise (sticky nav, cookie bar) before capture. Closer to finished, straight out.
Device frames built in
Sit the capture inside a clean phone or laptop mockup, screen corners masked, aspect ratios matched so nothing distorts.
Batch and reel
Feed it many URLs at once. It captures each, then stitches every mobile clip into one reel and every desktop clip into another. A portfolio in one pass.
Privacy is not the trade-off. It is the unlock.
Because my_demo_ never hands your demo to a platform, it does things a cloud tool structurally cannot. Their business needs the host, the account and the storage tier. Ours needs none of it, so you get more, not less.
No caps, no seats
No per-demo limit, no editor seats to buy, no view quota. Make as many as your own disk allows.
Demo the sensitive stuff
Unreleased builds, client work under NDA, internal tools. Capture from a local build and there is no cloud copy to leak.
Instant files
The assets are ready the moment capture ends. No processing queue, no render credits, no waiting on a server to hand you your own demo.
Full-quality originals
Nothing is transcoded for a streaming player. The files on your disk are the demo, at the quality you captured them.
The demo platforms all work the same way.
Arcade, Supademo, Storylane, Navattic, the interactive-demo category: your product goes up to their servers, behind an account, and the useful parts sit behind a subscription. It is a good business for them. It puts a preview of your work on infrastructure you do not own.
Your demo, on their servers
The capture leaves your machine and lives in their cloud, served from a link they control. Held by someone else means it can be governed by terms you did not read, or vanish when the plan lapses.
Paywalled where it matters
Free tiers cap demos, views and branding, and the features you actually need sit behind a per-editor monthly bill. You rent access to your own marketing assets.
my_demo_ breaks the pattern
Nothing is hosted for you, so there is no cloud tax and no link to lose. The files are yours, made on the machine that has your build already.
my_demo_ vs the demo platforms, on the facts
The interactive-demo tools are capable. The difference is where your product goes and what you walk away owning, and it holds across the category.
| my_demo_ (Local Gorilla) | Arcade | Supademo | |
|---|---|---|---|
| Where the demo lives | Files on your machine | Hosted in their cloud | Hosted in their cloud |
| Uploads your product | No, renders locally | Yes, by design | Yes, by design |
| You own the output files | Yes, plain video and images | Served from their link | Served from their link |
| Pricing model | Own it, on-device | Free tier + subscription | Free tier + subscription |
| Account required | No | Yes | Yes |
| Demo an unreleased local build | Yes, nothing leaves | Upload required | Upload required |
| Platforms | macOS now, Windows coming | Web app | Web app |
Arcade (arcade.software) and Supademo (supademo.com) are cloud-hosted interactive-demo platforms by category: your captured demo is stored and served from their infrastructure, an account is required, and they run free tiers plus paid subscriptions. Storylane and Navattic sit in the same category. Facts stated at category level; corrections welcome: admin@lionsedge.tech
Made once, yours to keep.
my_demo_ launches soon, macOS first. No per-demo hosting fee, no view quota, no editor seats. You run it on your machine and the assets it makes are files you own outright. Pricing lands at launch and will sit under the platforms it replaces.
Questions
Is there a local, private alternative to Arcade or Supademo?
Yes. my_demo_ turns a URL or a local build into scroll-demo videos, GIFs, stills and device-frame reels, all captured and rendered on your own machine. The interactive-demo platforms (Arcade, Supademo, Storylane, Navattic) host your demo on their servers behind an account and a subscription. my_demo_ hands you the finished files and keeps nothing.
Does my_demo_ upload my site or product to the cloud?
No. my_demo_ loads the page you point it at, then captures and renders every frame on your machine. Nothing is uploaded to a demo-hosting service and there is no share link on someone else's server. Point it at a local build or localhost and nothing leaves your machine at all, so you can demo unreleased work safely.
What can my_demo_ produce from one URL?
A mobile scroll video and a desktop scroll video, a looping mobile GIF, a full-page still and a hero still, and phone and laptop device-frame scenes. It can add fades, background music and a logo watermark, hide elements like cookie bars, and batch many URLs into one reel. The scroll is a real eased animation inside the page, so scroll-triggered animations and lazy-loaded images fire and get captured.
Can I make a demo of a site that isn't live yet?
Yes, and this is where local wins. Point my_demo_ at a local build, a folder, or localhost and it captures directly, with nothing uploaded anywhere. You get polished demo assets of unreleased work without exposing it to a third-party platform.
Do I own the demo files?
Yes. The output is plain video, GIF and image files written to your own disk. There is no account, no cloud library and no share link that expires or gets paywalled. Use them in ads, socials, pitch decks or docs, forever.
Is my_demo_ available for Windows?
macOS ships first; Windows is on the roadmap. The goal is system-agnostic, so the same private demo maker runs wherever you build. Local Gorilla's browser extensions are already cross-platform.
Keep your demos yours.
Launching soon, macOS first. Leave your email and you will be the first to know.
Notify me at launch