Think about what a great film studio actually is. Not one building — a lot. There's the front office where investors and press walk in and take the venture seriously. There are the attractions the public can visit. There's the archive where the canon lives, so a character introduced in 1985 still has the same eyes in 2026. And behind everything, there's the backlot — the soundstages where the next decade of the universe gets made.
Hold that lot in your mind, because it's the question you're really asking when your creative universe starts outrunning your capacity to express it: when the world in your head has hundreds of characters and your pipeline ships one asset at a time, what do you build — another asset, or the studio?
PlayCrypto® chose the studio. Rocket Now built the lot.
The Client
PlayCrypto® is a blockchain game studio — tagline: We Mainstream the Metaverse — anchored by its flagship IP, Metafrenzy®: a narrative metaverse following Blocker the Squirrel and friends through Metawood Forest, the Alt Coast, and DeFi Plains, with hundreds of characters, items, and world elements in canon. The studio operates a portfolio of interconnected properties: the corporate front door at playcrypto.org, the Metafrenzy® IP hub, the Frenzypedia canonical wiki, the DND Corporation narrative property, GM Diner™ — a canonical in-world location that's also a real consumer app — and FrenzyForge, the AI-native production studio that feeds them all.
The engagement was the whole lot, delivered by Rocket Now with Claude as the primary implementation engine at every stage.
The Challenge: A Universe Outrunning Its Studio
An IP-first studio hits a specific wall, and PlayCrypto® had hit all five faces of it at once. Investors and press needed a front door that reads as a serious game studio. Inbound interest — investor, collaborator, press — was arriving through ad-hoc channels with no triage, no ownership, no record. The studio's privacy posture demanded reachability with zero published addresses. A 7680×4320 canonical world map couldn't be communicated as a static image. And underneath everything, the real constraint: every new location, character, or asset required a manual narrative-art-animation-3D pipeline, which meant the studio's growth was bounded by content throughput, not by demand.
Under those circumstances, the right move isn't another asset — it's infrastructure. Build the lot once, and every production afterward walks onto standing sets.
The Lot, Building by Building
The Front Office — the PlayCrypto® studio platform
The corporate surface at playcrypto.org presents the studio in a deliberately distinct visual identity — a minimalist black-and-white angular theme that keeps the corporate layer and the vibrant Metafrenzy® IP from ever visually merging, the way a studio's letterhead never looks like its movie posters. Behind the front desk: three typed intake surfaces (investor/collaborator contact, a multi-step press-inquiry wizard, newsletter signups) writing to dedicated tables, triaged in a role-gated admin portal.
The privacy requirement was solved the way we prefer to solve everything — by architecture instead of policy. Every table carries row-level security with a public-write, admin-read pattern: anyone can reach the studio, and only an authenticated admin role can read what was sent. Roles live in a dedicated table behind a security-definer check, never on a user-writable row. Not one email address or physical address renders anywhere on the public surface, and yet the studio has never been more reachable. When privacy is a property of the schema, then it can't be misplaced by a copy edit.
The Map Room — making the Frenzyverse explorable
That 7680×4320 world illustration became a navigable place: an OpenSeadragon deep-zoom viewer over a tiled image pyramid, with location hotspots anchored by pixel-percentage coordinates so they hold true at every zoom level, opening lore modals for each canonical location. When a visitor can travel the map instead of squinting at it, then the world stops being an illustration and starts being a destination.
The Open Attraction — GM Diner™ and DinerFrenzy
GM Diner is the lot's public-facing ride: a canonical Metawood Forest location that's simultaneously a real consumer product at gmdiner.com — retro-diner marketing site, a genuine real-time game, a player platform, and an on-chain identity layer, all in one codebase of ~40,900 lines across 222 files.
DinerFrenzy itself is real game engineering, delivered as a conversational build: a 60 FPS canvas engine with 5 heroes carrying unique non-stacking buffs, 11 distinct enemy AI behaviours, hold-to-charge combat, a 50-level endless curve, and a full Career Mode — born as the client's unstructured design notes about acorn debt and a rolling-pin penalty, decomposed by Claude into four sequenced sub-phases and shipped as a loan system with continuous interest drain, charge-scaled multipliers with combo stacking, a 7-level restructure with the Chef Rektnut board-clear special, and dual persisted leaderboards aggregated by a Postgres trigger. Performance work you can verify in source — offscreen background caching, object pooling for particles and audio, memoised HUD components, device-adaptive quality — holds 60 FPS on desktop and 30–45 on mobile.
Around the game: accounts with guest play, a GM Points economy with full transaction logging, achievements, monthly tournaments with scheduled close-out, and a 10-screen live-ops console that lets PlayCrypto® run users, avatars, NFT contracts, leaderboard moderation, and tournaments without ever filing an engineering ticket. Capability transfer is part of the deliverable: when the client can operate the ride themselves, then the studio scales without us in the loop — which is exactly how it should be.
And mid-project, the attraction changed foundations without closing: a complete chain migration from Base to ApeChain, with the Glyph SDK mounted app-wide as the primary wallet provider — nonce-based wallet sign-in with server-side signature verification, APE balance panels across mainnet and Curtis testnet, per-chain contract registries. The migration was executed as one coordinated change set across chain configs, wallet connectors, edge functions, and database defaults — undertaken specifically to position PlayCrypto® for Yuga Labs' Otherside 3D SDK, which requires demonstrably native ApeChain + Glyph development. When the qualification standard is "prove you build natively here," then a wrapper won't do — so we built natively.
The Backlot — FrenzyForge, where the world gets made
FrenzyForge is the strategic layer: the studio's answer to the content bottleneck. Ten integrated modules — Narrative Forge, Visual Library, Asset Foundry, Animation Studio, Game Lab, Synthesis, and their supporting surfaces — on one authenticated shell, where a script becomes chapters, concept art, voiced and captioned video scenes, and inspectable 3D assets without leaving the browser.
The differentiator is orchestration, not single-shot generation. Five multi-step agent pipelines run server-side: Script-to-Production's six-stage line (decompose → concept image per scene → voiceover → timed captions → video with the image as first frame → provenance linking, with real stage-level progress); a multi-agent orchestrator routing composite tasks with model fallback; a Creative Oversight agent that builds a style bible from the project's own canon, scores asset batches against it under strict JSON schema, and automatically corrects what falls below threshold; a Story Gap agent that turns "are the visuals behind the script?" into an enumerated, auto-fillable list; and an Image-to-Mesh pipeline that pairs vision analysis with an in-house deterministic GLB geometry engine and an iterative self-critique refinement loop — no third-party mesh vendor anywhere.
Every artifact carries a resource identifier and version history. When provenance is a platform property, then "which script beat produced this clip?" is a query, never an archaeology project.
The Forward Reel: Claude Moves Onto the Lot
Here's the part we'll say plainly, because precision is the brand: Claude built this lot — it has not yet worked on it. The portfolio's runtime reasoning services currently route to other models through a gateway abstraction we designed for exactly this moment: every model call is server-side, every provider is swappable per-function. The registered next act migrates the six reasoning-heavy services — story decomposition, gap analysis, creative oversight, orchestration, production planning, and the in-app copilot — to Claude behind per-service flags, gated by a golden-set evaluation harness built from real Frenzyverse canon. Then comes the Canon Guardian: an automated continuity gate checking every new character, location, and asset against the full world bible before approval — followed by consumer surfaces, from a canon-grounded Frenzypedia lore assistant to in-world NPC dialogue for Blocker and the Fudrats themselves. The lot is built; the new lead engineer is walking through the gate.
The Results
- A complete studio portfolio delivered as one system: corporate platform, press program, deep-zoom world map, a full consumer game product, and an AI-native production studio — each property launching into shared brand, backend, and security patterns rather than starting from zero
- Verified build scope: ~40,900 lines and 18 fully RLS-protected tables on GM Diner; 18,267 frontend and 4,148 backend lines, 17 edge functions, and 19 RLS-protected tables on FrenzyForge; 10 live-ops screens; 447 integrated art and audio assets; 6 AI modalities orchestrated
- A complete mid-project chain migration to native ApeChain + Glyph, executed as a single coordinated change set
- Privacy and security enforced structurally: zero published contact details, public-write/admin-read intake, roles isolated behind security-definer checks across the portfolio
- The content bottleneck has a platform: script-to-scene-set in one operation, automated consistency review, measurable story coverage, and in-browser 3D
"[Quote from Play Crypto Inc. leadership — pending sign-off.]" — [Name, Title], Play Crypto Inc.
Why It Worked: One Lot, Compounding
The Rocket Now principle holds one more time: a single step in the right direction is worth exponentially more than many steps in the wrong one. PlayCrypto®'s many-wrong-steps path was obvious and tempting — keep shipping assets, one at a time, forever. The one right step was building the world as a system: canon as data, provenance as a platform property, one brand architecture, one security pattern, one backlot feeding every property. Now the portfolio compounds — when the next property launches, then it walks onto standing sets, inherits the front office, appears on the map, and draws from the same canon. That's the difference between making content and owning a studio.
Is your universe outrunning your pipeline? Stop building assets. Build the lot. → RocketNow.com
Editor's note — before publishing:
- Replace the placeholder quote and confirm co-marketing permission with Play Crypto Inc.
- Quantitative business metrics are excluded per the customer's direction — codebase-verified figures only; keep it that way in edits
- Yuga Labs / Otherside SDK approval status is [TO CONFIRM] — the piece deliberately says "position/qualify," not "approved"; update once confirmed
- Claude runtime adoption is forward-looking (build-time vs. runtime distinction is intentional and accurate per the deal-registration docs) — don't let edits blur it
- ® marks on PlayCrypto® and Metafrenzy® are enforced per the client's brand rules; preserve them