Settings & integrations
Connect the services behind your studio. Start with the free storyboard demo.
AI video generation
A configurable text-to-video model through the official Replicate API. A modular server adapter creates predictions and checks their real status.
YouTube Data API
Official Google OAuth, encrypted refresh tokens, and resumable video uploads. No Google passwords or client secrets in the browser.
Google API quotas apply. Unverified projects can be restricted to private uploads. Public publishing may require OAuth verification and a YouTube API compliance audit.
Official upload guideUnlock connected studio
The app owner can use their platform session. Other users need the owner-set studio access code to use paid generation and connect their channel. Never enter API keys here.
Access is tied to this browser, not a full user account. Keep your device private; clearing browser storage loses access to that session’s library.
Setup checklist
- In Functions → Secrets, set
REPLICATE_API_TOKENandREPLICATE_MODEL(the exact owner/model identifier from the model’s official API page). Choose a text-to-video model supporting prompt, duration and aspect_ratio or ratio; the adapter verifies its schema before submitting. Add credits to your Replicate account before requesting video. - Create an Upstash Redis store (a limited free tier is available). Set
UPSTASH_REDIS_REST_URLandUPSTASH_REDIS_REST_TOKEN. Add its exact hostname to Functions → Outbound Domains. This external server store is used because built-in data storage is not enabled. - Set
STUDIO_ENCRYPTION_KEYto a cryptographically random, base64-encoded 32-byte key. SetSTUDIO_ACCESS_CODEto a long private access code. Never share your encryption key. - Enable YouTube Data API v3 in Google Cloud, configure the OAuth consent screen, and create a Web application OAuth client. Set
GOOGLE_CLIENT_ID,GOOGLE_CLIENT_SECRET, andGOOGLE_REDIRECT_URI. - The redirect URI must be your published app URL ending in
/oauth/callback(not a hash path). Register this exact URL in Google Cloud and add your Google account as a test user while in testing mode. - Add
replicate.deliveryandwww.googleapis.comto outbound domains for dynamically returned media/session URLs. Other API hosts are detected from the server functions. - Check connections, unlock the studio, and connect your channel. Create a short paid test clip, then test a Private upload first.
What’s supported, and what isn’t?
The demo is an animated storyboard, not an AI-generated video and not an MP4 export. The current adapter requests one 5- or 10-second clip and can describe connected shots in its prompt; continuous characters, exact scene cuts and scientific accuracy are not guaranteed. Narration, synchronized captions, clip stitching, 1080p/4K upscaling and self-hosted open-source video inference are not implemented. Native output resolution is provider-controlled. Background generation continues at the provider; status refresh and chunked uploads resume while this studio is open. Provider download URLs may expire, so download MP4s promptly. Custom thumbnails require channel eligibility. Storage records expire after 30 days. Scheduling uses YouTube’s publishAt, not a promise of eligibility. Official API documentation was consulted for the request formats; deployed credentials are still required for live validation.
What has been tested?
The app’s build and TypeScript checks are verified. The dashboard, draft metadata, demo scenes, forms and routing have been reviewed. No provider credentials or Google OAuth client are supplied, so live generation, token exchange, uploads and thumbnail publishing cannot be claimed as tested. Complete the private-upload checklist above before production use.