BabySea
Sign up
Templates
Sherin for Runway icon

Sherin for Runway

Private workspace for generative media with own key, domain, and storage.

View site
Loading preview
Sherin for Runway preview

Best for

Private workspace
Owner-only access
Image generation
Video generation
Schema forms
Reference uploads
Generation gallery
Flexible storage
Custom domain

Overview

Sherin for Runway is a self-hosted private creative workspace for one owner who wants direct Runway image and video generation with their own key, domain, and storage. It ships with Studio, Gallery, References, Usage, and Profile dashboard surfaces gated by Supabase Google OAuth and an owner email allowlist.

Use it when you want a deployable Runway workspace that maps Semantic Lady schema fields into Runway API requests without routing through a managed multi-provider layer. The starter runs on Next.js with direct Runway BYOK execution, optional BabySea mode, Supabase Auth and Postgres, and storage choices across Supabase Storage, AWS S3, Cloudflare R2, and Vercel Blob.

What you can build

  • An owner-only generation studio for Runway Gen-4, Gen-4.5, Aleph, and Act Two models.
  • Schema-aware prompt forms with exact Runway fields, ratios, durations, moderation, seeds, and reference inputs.
  • Image and video input workflows with URL-based and upload-based source assets.
  • A private gallery that can display stored image and video outputs from completed generations.
  • Usage and profile dashboards for provider status, storage status, queue state, quotas, and deployment settings.

What you need

  • Next.js for the dashboard routes, server actions, and worker trigger.
  • Supabase for Auth, Postgres generation records, and owner profile state.
  • Google OAuth for owner sign-in through Supabase Auth.
  • Runway for direct image and video execution with RUNWAYML_API_SECRET.
  • BabySea for optional hosted execution with BABYSEA_API_KEY.
  • Supabase Storage for the default generated media and reference storage path.
  • AWS S3 for optional generated media storage.
  • Cloudflare R2 for optional S3-compatible generated media storage.
  • Vercel Blob for optional Vercel-backed generated media storage.
  • Sentry for optional production observability.
  • Cron or an external scheduler for optional /api/generations/process recovery.
  • For hosting, you can deploy using DigitalOcean, Netlify, Railway, Render, or Vercel.

Description flow

The owner enters through Supabase Google OAuth, and Sherin checks the account email against OWNER_EMAIL before loading the private dashboard. Studio, Gallery, References, Usage, and Profile then operate as a single-owner workspace for that deployment.

In Studio, the owner selects a Runway model, writes a prompt, tunes Semantic Lady schema fields, and attaches supported image or video references from URLs or uploads. Sherin prepares only the fields supported by the selected model and sends direct Runway requests when INFERENCE_PROVIDER=runway.

On submit, the server creates a generation record, persists input assets when needed, stores request metadata, and dispatches queued work through the dashboard or worker route. Runway task responses are polled until completion, and completed outputs can be copied into the configured storage provider.

When a generation settles, Gallery shows the stored image or video output, failed state, or unavailable asset state. References keeps reusable input media links close to the workflow, while Usage and Profile show provider configuration, storage posture, quota settings, and owner-visible deployment details.