Inspectable routing
Model selection, capability rules, fallbacks, and credit estimates remain visible in application code.
OPEN-SOURCE CORE
Own your
creative stack.
Inspect the routing, keep control of your data, and deploy the core with infrastructure you own. Use the hosted studio when you want convenience, or self-host when control is the requirement.PORTABLE BY DESIGN
The important layers stay visible.
Your data model
Workspaces, agents, assets, generations, and the immutable credit ledger live in your Supabase project.
Your media
Uploads and generated files stay private in your R2 bucket and use short-lived signed delivery links.
SELF-HOSTING
From clone to a private creative cloud.
The deployment is a standard Next.js application with explicit provider boundaries. Nothing depends on a hidden media proxy.Clone and configure
Copy the environment template and choose the provider accounts that your deployment will use.
Apply the data model
Run the Supabase migrations to install workspace isolation, RLS policies, credits, agents, and generation history.
Connect private media
Create an R2 bucket and provide the credentials used for private uploads and signed asset delivery.
Build and deploy
Typecheck, test, and build the same Next.js application that runs the hosted product.
npm install
npm run typecheck
npm test
npm run build
npm startREQUIRED SERVICES
Four boundaries.
No mystery layer.
Node.js and a Next.js-compatible runtime for the web application and route handlers.
Supabase Auth and Postgres with the included migrations and row-level security policies.
A private Cloudflare R2 bucket for source media, finished assets, and signed delivery.
An OpenRouter key for the models enabled in the capability registry.
WHAT SHIPS
A useful core,
not a landing-page shell.
The repository includes the product surfaces, model routing, tenant data model, private media flow, generation metering, and tests needed to extend the studio with your own provider accounts.Image
Route prompts through the model registry, keep generation history, and save finished work to private media storage.
Video
Submit asynchronous video jobs and poll provider status without asking the local machine to transcode media.
Voice and dubbing
Generate multilingual speech or transcribe uploaded audio and supported video containers.
Music
Generate provider-backed music when the selected OpenRouter model is available to your account.
Avatars
Store consented identities and use approved source media in presenter workflows.
Agents
Create workspace-scoped agents with separate knowledge, voice, sessions, messages, and usage.
CONFIGURATION CHECKLIST
Bring four service boundaries.
Copy.env.example, add these server and public variables, then apply the included Supabase migrations. Secret values never belong in client components or source control.HOSTED OR SELF-HOSTED
Control when you need it.
Convenience when you do not.
Your infrastructure
- Bring provider, database, and storage accounts
- Run migrations and deployment yourself
- Own upgrades, observability, and incident response
- Inspect and adapt provider routing
Ready workspace
- Start without provisioning infrastructure
- Managed credit accounting and private media
- Provider routing configured for the product
- Product updates without manual deployment work
SECURITY MODEL
Workspace isolation is part of the architecture.
Tenant boundaries
Every commercial record is scoped to a workspace, and database policies verify membership before access.
Server-only secrets
OpenRouter, Supabase service-role, and storage credentials stay in the server runtime.
Metered generations
Credits are reserved before provider work, settled after success, and returned when a job fails.
CONTRIBUTING