Infrastructure
CreatorStudio’s orchestration tier is deliberately light. The heavy compute (GPU-bound model inference) is provider-side, across the fifteen-model stack. Everything else, the app logic, the Director Memory Graph, the media artifacts, the public surfaces, lives on the Cloudflare ecosystem: Pages, Workers, R2, and D1.
Why Cloudflare-native
Section titled “Why Cloudflare-native”Four reasons, in order of importance for this product.
- Edge-first delivery. Creators land on
creatorstudio.mediafrom every region. The Channel Analyzer runs on every continent. Edge distribution means sub-second first paint and low-latency API calls without regional deploys. - Low cost-per-request at scale. Workers and Pages are priced in a way that holds up at creator-scale traffic. Pennies-per-analysis economics on the free Channel Analyzer only work if the ambient request cost is near zero.
- Integrated primitives. Pages, Workers, R2, and D1 are one account, one billing line, one mental model, one auth story. No five-way integration tax.
- Margin widens as models commoditize. Model-layer compute declines roughly 30 to 50 percent every six months. The orchestration tier does not. Keeping the tier light on Cloudflare means per-story margin improves as stage costs fall.
Compute
Section titled “Compute”| Layer | Choice | What it runs |
|---|---|---|
| Front end hosting | Cloudflare Pages | Marketing site, documentation, app shell |
| Application logic | Cloudflare Workers and Pages Functions | API endpoints, auth, orchestration glue, Ra routing decisions, webhook handling |
| Model inference | Provider-side (fifteen-model stack) | All GPU-heavy generation: Veo 3, Sora 2, Kling, Runway, Pika, Luma, Seedance, Hailuo, ElevenLabs, MINIMAX, FLUX 1.1 |
CreatorStudio does not operate a GPU fleet. That is deliberate. The orchestration tier is a thin, stateless, edge-deployed layer that tells external models what to do. The expensive work happens at the providers, paid per-second, per-shot. As those per-second costs decline, the Studio’s cost structure improves automatically.
Storage
Section titled “Storage”Three stores, three jobs.
| Store | Role |
|---|---|
| Cloudflare R2 | Media artifacts: keyframes, per-stage shot outputs, final renders, per-platform variants, audio beds, dialogue takes. Large, append-heavy, read-often. R2’s zero-egress pricing matters when creators download and re-publish. |
| Cloudflare D1 | Relational data: accounts, projects, renders, billing, publishing calendars, subscription state. Small per-row, high cardinality, transactional. |
| Vector store | Embeddings for the Director Memory Graph: voice, visual fingerprint, audience signal, format DNA, outcome data. Queried on every brief to condition Ra’s routing decisions. |
The Director Memory Graph is the most important object on this infra. It is the moat. It survives every model swap underneath. Every render enriches it. Every brief reads from it. For the routing logic that consumes it, see Model Orchestration.
Edge delivery
Section titled “Edge delivery”- Pages serves the marketing site, the documentation, and the app shell worldwide from the edge.
- Image transforms handle per-platform variants (YouTube long, TikTok or Reels vertical, X or LinkedIn square) without round-tripping through origin.
- Workers run close to the user for auth, session, and API calls that do not need heavy state.
For what sits on the marketing edge versus the authenticated app, see Website.
Why this infra choice supports the moat
Section titled “Why this infra choice supports the moat”The moat is the Director Memory Graph and the conversion signal flywheel it feeds. Both are data assets, not compute assets. The infrastructure choice protects them two ways.
- Cost margin widens over time. Because the heavy compute is provider-side and commoditizing, and the orchestration tier on Cloudflare is light, per-story margin improves even without price increases.
- Data gravity stays inside. The Graph lives on CreatorStudio infrastructure. Switching cost for a creator is not just “move to another tool”; it is losing their cast, voice, format DNA, and conversion intelligence. That switching cost grows every render.
The right shape is: a thin, cheap, global orchestration tier on Cloudflare, spending generously at the model layer because the model layer is getting cheaper, while the compounding asset (the Graph) stays owned, stable, and local to the Studio. Public beta opens April 20, 2026.