LizzFlix Docs

Architecture and Runtime

How the production runtime is split today and how the large services should be decomposed next.

Production boundary

  • Cloudflare lizzflix-backend is the canonical backend for studio state, uploads, jobs, billing, the model catalog, and generation orchestration.
  • Vercel serves the frontend, auth/session shell, and Stripe redirect flows.

Maintainability rules

  • Active studio UI should use studio-client-api.ts.
  • Active product routes should not depend on src/lib/studio/service.ts.
  • Inline bilingual UI copy should live in dictionaries or dedicated localized content modules.
  • Oversized modules should be guarded by CI.

Web runtime

Split src/lib/studio-runtime/service.ts into:

  • queries
  • commands
  • jobs
  • billing
  • catalog
  • media
  • mappers
  • prompts

Worker runtime

Split cloudflare-worker/src/index.ts into route modules:

  • auth
  • billing
  • catalog
  • uploads
  • jobs
  • studio-read
  • studio-write

Split cloudflare-worker/src/studio.ts into:

  • series
  • characters
  • locations
  • episodes
  • scenes

Split cloudflare-worker/src/studio-workflows.ts into:

  • voices
  • dialogue
  • start-frames
  • renders
  • scene-proposals

LizzFlix Overview

What LizzFlix does, how the app is structured, and what a creator can expect in production today.

Characters, Locations, and Scenes

How reusable assets preserve consistency across a series.

On this page

Production boundaryMaintainability rulesRecommended splitWeb runtimeWorker runtime