How I shipped a 1–2 photo → tip-toe barn meme dance on Cloudflare Workers — template lock, guest Stripe, Seedance via TryAllAPI.
rumpelstiltskindance.video turns 1–2 adult photos into a tip-toe / “Wing In My Jawwdinz”-adjacent meme dance short with sound. Independent fan tool (2026), 18+. The homepage does not ask users to storyboard; it locks the motion template and sells the render.
Angle for this post: template lock done with an optional second dancer — similar family to party sites, different farm/barn beat. Prices and model ids change; treat live site / console as source of truth.
Create panel pattern:
Copy on-site refuses celebrity / MV stills. That is load-bearing product policy for face tools — not a legal afterthought.
Live pricing verified: 500 credits · $8.88 · 720p, with multi-packs (e.g. $16.99, larger tiers). Guest Stripe. Always re-check the create button.
Meme dances are recognizable moves. If you let users rewrite the choreography prompt, you get mush that does not match the sample. Locking the motion:
| Layer | Choice | Role |
|---|---|---|
| Front / SSR | TanStack Start (Vite) | Landing, upload panel, generation status |
| Runtime | Cloudflare Workers | Edge deploy, secrets, API routes |
| DB | Cloudflare D1 | Credits, orders, task rows (table prefixes if DBs are shared) |
| Payments | Stripe Checkout | One-time packs + optional larger packs; guest checkout |
| Video upstream | TryAllAPI → Seedance | Async create + poll |
| Analytics | GA | Funnel sanity check |
lead (+ optional friend) → tip-toe template
→ check credits (else Stripe)
→ Worker creates Seedance task via TryAllAPI
→ poll until MP4 URL → store / show
→ on failure: refund credits
Operational checklist after register / top-up:
rumpel-prod vs sandbox).
TRYALLAPI_API_KEY). Never in the frontend bundle or a blog post.
Conceptually the call shape looks like this (field names follow the aggregator’s v3 contents API; always re-check current docs):
POST /api/v3/contents/generations/tasks
Authorization: Bearer <TRYALLAPI_API_KEY>
Content-Type: application/json
Accept-Encoding: identity
GET /api/v3/contents/generations/tasks/{id}
I send Accept-Encoding: identity from the Worker because some gateways behave badly with transparent decompression. Model ids used in production look like Seedance 2.x family strings — treat console ids as source of truth, not this paragraph.
A few details that bit me across this family of sites:
duration as an explicit integer.resolution and ratio. generate_audio. queued → running → succeeded / failed. Success URLs are often supply_unavailable or hard failures: refund credits, show a short human message, log the detailed upstream error server-side, optionally fall back to another Seedance tier.
Rough mental model for upstream cost (illustrative only — use your own usage fields and invoices):
tokens ≈ duration_sec × width × height × fps / 1024
cost ≈ tokens × price_per_million_tokens
Price the site after you measure a few real runs with retry margin, Stripe fees, and failed-job refunds — not from a spreadsheet fantasy of 0% failure.
Map lead vs friend roles consistently. Rehost short-lived result URLs. Separate keys if you operate a matrix of dance domains.
Demo UIs are easy. The line between toy and product is:
task_id in D1.
Two books of account stay separate: USD balance at TryAllAPI (your cost) vs site credits (what you sold). Mixing them in one mental ledger is how you underprice or invent “mysterious” losses.
When several products share one Stripe account, isolate webhooks by endpoint or by metadata (site / product). Callbacks pointed at the wrong apex domain are a classic multi-site footgun.
Secrets stay in Workers: TRYALLAPI_API_KEY, STRIPE_SECRET_KEY, webhook secret, auth secrets. The browser only ever sees publishable Stripe keys if needed.
Typical loop on this template family:
pnpm install
pnpm cf:deploy
Before calling a deploy “done”:
AUTH_TRUSTED_ORIGINS and Stripe return / webhook URLs match the production HTTPS origin.
Production origin: https://rumpelstiltskindance.video.
Face-based generation is not “just another SaaS CRUD app”:
Those constraints belong in the product, not in a footnote you add after the first dispute email.
Consumer: watch the sample on rumpelstiltskindance.video, upload authorized photos, pay once. Builders: TryAllAPI, prove create+poll, then wrap credits. Lock the tip-toe; meter the GPU.