Capture the premise, audience, and constraints.
AI production studio for long-form makers
Your studio. Your hardware. One agent from blank page to final cut.
Say what you want; Algernon carries the project memory across manuscript, visual generation, Resolve handoff, launch assets, and approval gates. Taste stays in charge.
Local files on diskNo credit-meter postureNothing publishes without approval
Project: feature proof cutapproval required
Canoncharacter lock active
Visuals3 approved, 8 alternates
Resolvebins ready
Launchdraft-only
Taste is the only prerequisite.
Say it. The studio does it. You approve it.
The line
Most tools stop at the artifact. Algernon keeps going through the launch.
The commercial moat is not another chat box. It is one persistent production line: project memory, creative work, post workflow, and campaign materials moving together.
Draft with canon, research, and receipts attached.
Generate shots and organize Resolve handoff bins.
Prepare publishing-grade files where the lane is wired.
Draft launch pages, SEO seeds, and outreach.
Stage the storefront path without making earnings claims.
Three doors
The same studio, sold through the work people already care about.
Filmmakers
Script breakdown, local visual iteration, consistent characters, and a DaVinci Resolve round-trip that keeps approved, alternate, and source material separated before the edit.
Authors
A persistent canon that remembers book one while you draft book five, then carries the same project into cover, trailer, edition, and launch work.
Educators
Teach the whole production line honestly: where AI helps, where it breaks craft, and how approval gates keep the maker in the chair.
Product lines
Six doors into one studio.
Subdomains can come later. For V0, the site makes the catalog clear on one Algernon URL: editions, packs, and proof surfaces without pretending every owner-grade tool is already packaged for customers.
Live
Algernon Writer
The project remembers what the chat window forgets.
Draft, revise, and keep canon consistent from the first chapter through the trailer. Research, series bible, reference sheets, and manuscript work live in one project memory.
01Chapter 03 revision
02Character canon lock
03Series bible recall
Trust layer
The safety promises are product architecture, not marketing garnish.
One project organism
Manuscript, canon, references, shots, exports, launch materials, and approvals stay attached to the project instead of scattered across tools.
Files you can audit
Every generation leaves local artifacts: drafts, alternates, prompts, source outputs, and receipts you can inspect before approving the next step.
Your hardware, your keys
Local engines do the heavy lifting where they can. Cloud model calls go through your accounts and your spend gates; Algernon is not a credit meter.
The economic wedge
Their agent works for their meter. Yours works for you.
Iteration is where taste lives. Algernon is designed around local engines, BYO model accounts, and operator-controlled spend gates so the studio can work without turning every experiment into a credit anxiety problem.
Built in public
A working production system first, a sales page second.
Algernon is being built by a film professor and working documentarian for the actual work of writing, cutting, teaching, and launching. The page you are reading was drafted through Launch Forge, then revised under human review.
Review the proof layerFounding cohort
Be first in when the studio opens.
Waitlist members get private beta access priority, founding-member rate-lock language before public rates, and the Honest Field Guide to AI-Assisted Production.