Try
Every product here has a demo, and each one says exactly what it is running. A real engine and a recreation are different claims, so they are not allowed to share a label.
Real product code
Lifted out of the app unmodified, with the hash of what was taken recorded in the repository beside it. two of the eleven demos qualify, and they qualify because there was a clean boundary in the product to lift.
Light every row, every column and every garden — with no two fireflies touching.
The rule check is Glow Garden’s own code, vendored unmodified, including the solver that refuses any placement which would leave the board unsolvable. The board is fixed rather than generated, and was searched for with that same solver until one with exactly one solution turned up.
Turn one of Veyra’s own drawings into a clean tattoo stencil.
Both halves are the product’s. The drawing is one of the four samples the Veyra app bundles, and the stencil is produced by Veyra’s own image-processing function, vendored unmodified and running in your browser — nothing here is precomputed. The app does generate artwork, on a GPU the studio owns, and that part is deliberately not in this demo: it would need a model running behind this site, and a page that quietly generated nothing while looking like it did is the thing this whole section exists to avoid.
Real product assets
No product code runs, but nothing on screen was made for this website: the recordings, the artwork and the numbers are the ones the app ships. The loop around them is ours.
Learn four colours by ear, then prove it — in a language you may not speak.
Every word you hear is a file from Pivumo’s shipped voice package — the same recording, the same encode, at the same loudness the app plays it at. Six of the 29 locales are here, and the age toggle really does swap the take. The round itself is written for the web; the voice is not.
Repair the front gate — the game’s real first order.
The pictures and the numbers are the game’s. Every sprite is one of its own rasters, the board is its 5-column, 35-cell board, the chain is its 5-tier clean chain, and the order is h1 — the actual first order of 100, with the item it asks for and the 20 coins it pays, read out of the content file the shipped build loads. What is rewritten is the merging itself: the game runs on Flutter and Flame, which cannot be put in a web page at a weight this site would accept.
Take the grove back — the game’s real first level, four waves and a Warden.
The fight is the game’s. These are level 1 of 1000, with the hit points, damage, counts and timings the shipped build reads out of its own campaign file; the shrine offers the two routes that level really offers, and the Bloomwell’s +24 kin and the Thorn Oath’s 1.35× attack are its own balance numbers. The Warden is boss family 1 of 50, with its real root and nova patterns and its real colour, and the grove is drawn in the palette region 1 declares. Every word is the game’s own string, in any of its 10 languages. What is rewritten is the combat loop itself: Godot’s web runtime is 10.3 MB before any content and this campaign is another 5.9 MB, so a real build would be roughly fifty times the weight of anything else on this site.
Interactive recreation
The mechanic or the flow, written for this site rather than lifted from the app — because in these four there was no boundary to lift from. Two of them still speak in the product’s own words, in ten languages.
Keep the Pulse Core alive for thirty seconds without ever holding still — and save the Pulse for what the shield cannot stop.
A recreation, written for this site. It is not ZUPI’s code and does not claim to be: the shipped game’s source is not in the studio’s repository, so this was built from the public App Store listing — the Pulse Core, the three-second stillness rule, deflections charging a Pulse, six of them per Pulse, armour-plated threats that only the Pulse breaks, splitters, trackers and guard bands. The numbers and behaviours come from that listing and its screenshots; the levels, the difficulty curve and the feel are this site’s, not the game’s. Until 2026-10-03 this page ran the previous game’s engine and said it was the shipped one.
Sort every spirit so each jar holds a single colour.
The mechanic is the shipped game’s, rebuilt for the web rather than ported: lift the top spirit, drop it on a matching one or an empty jar. The board is hand-set and solvable in six moves. The app generates its boards and guarantees them; this one does not need to.
Answer “has the dog been walked?” — then add something of your own.
A web recreation of one Didi flow with sample household data, not the app itself. Didi’s logic is bound to its native UI layer and there is no engine boundary to expose, so what you are using is the interaction, not the product.
Pick the language you think in, then a language you do not — and order a coffee in it.
The teacher’s words are Vela’s. Every line here is a string from the app’s own lesson script, in whichever of its ten interface languages you choose, and the sentence you assemble is the phrase the app holds for that target language. The lesson flow is rebuilt for the browser, and there is no speech recognition anywhere in it — which is not a limitation of this page. Vela has never run a model, recognised a word or made a network request, and the line the teacher uses to say so is the app’s own.
Log a day, add a meal, and see how carefully the app refuses to over-read it.
The words are Auren’s, in ten languages including Arabic right-to-left, copied out of the app’s own string table rather than rewritten for this page — because the hedging in them is the product. The history behind the chart is the app’s sample fixture, which the app itself marks as fictional, and the insight at the end is deterministic: the same taps produce the same sentence every time. Nothing you enter leaves your browser, nothing is stored, and no part of this is a health record or a health claim.
Guided demo
For the products whose work genuinely cannot happen in a browser. You step through what the app does, and what you are shown at the end is real output from it.
Take one sprint from a phone clip to a single coaching cue.
A walkthrough, not an analysis. Nothing is uploaded and nothing is computed in your browser — you step through the stages the app performs, and the report at the end is a real screen captured from SPRIVO rather than a number invented for this page.
Why it is labelled
Two of these eleven demos run code lifted straight out of the product. If the rest were allowed to imply the same thing, the claim would be worth nothing on any of them — so each one carries its own label, and the pages say what is running.
