Running in two minutes.

Clone, install, run. Open localhost:3000 and the offline Darkroom models work immediately.

git clone github.com/zanni098/moviola
cd moviola
npm install
npm run dev

Copy .env.example to .env.local and add any of these. Each one lights up more of the model catalog — none are required.

Vercel — import the repo, set env vars, deploy. No extra config.

Docker — the standalone image is the exact same build.

docker build -t moviola .
docker run -p 3000:3000 --env-file .env.local moviola

src/
  core/        capability flags, provider contract, presets, cost
  providers/   one adapter per provider (replicate, fal, mock)
  data/        the model catalog + preset packs (data, not code)
  studios/     plugin studios: image, video, storyboard, library
  components/  composer, gallery, shell, marketing
  app/api/     stateless handlers: generate, jobs, models, proxy

Servers are stateless proxies; generation records live in the browser (IndexedDB). That local-first design is what makes Vercel and Docker behave identically.

A provider is one file implementing submit and status, plus a catalog entry with capability flags. The UI rebuilds its controls from those flags — zero UI changes.

// src/providers/myprovider.ts
export const myAdapter: ProviderAdapter = {
  name: "myprovider",
  isConfigured: () => !!process.env.MOVIOLA_MYPROVIDER_KEY,
  submit: async (model, input) => { /* returns { providerJobId } */ },
  status: async (model, jobId) => { /* returns { state, outputs } */ },
};

A studio is a folder under src/studios that registers itself in one array. Adding one requires no changes to core — which is how Lip Sync, VFX and Workflow will arrive.

// src/studios/index.ts
export const STUDIOS = [
  { slug: "image", name: "Image", icon: ImageIcon, component: ImageStudio },
  // ...add yours here
];