Case study10 / 12

Video Machine

Video rendering SaaS I built and ran. You typed a few slides or pasted a URL and got a finished video in one to two minutes. Three free videos to start, credits after that.

Year
2026
Video Machine
5 images
View gallery

Overview

Video Machine turned written slides into finished videos. You typed a title, picked a theme, shape, and pace, and added slides as headline plus detail lines while a preview rebuilt itself as you typed. Point it at a source instead and it drafted the slides for you, either a client-ready SEO audit from a URL or a market recap from a handful of ticker symbols. Renders ran in the cloud and landed in one to two minutes as either vertical 1080x1920 for social or widescreen 1920x1080, with an email when the file was ready. The platform ran on React Router with Remotion for rendering, Trigger.dev for background jobs, Railway S3 for storage, and Polar as merchant of record for credit purchases.

What I learned

Running this as a live product taught me more than building it did. Remotion made the rendering tractable but the hard part was everything around it: long-running jobs that outlive a request, retries that do not double-charge a credit, and progress states that keep someone informed while a render takes ninety seconds. Trigger.dev handled orchestration and gave me a place to reason about failure instead of scattering try/catch through route handlers. Wiring credits through Polar webhooks meant treating balance as something that must reconcile, not a number to decrement optimistically, since a failed render has to return the credit it took. Drafting free and charging only on render turned out to be both a pricing decision and an architecture one, because the split forced a clean boundary between the editor and the render pipeline.

Why it matters

Video Machine was a product with a pricing page, not a demo. It covered the full path from an idea to a live checkout: rendering pipeline, background job orchestration, object storage, transactional email, authentication, a free trial, and credit purchases through a merchant of record. Owning every layer meant making the tradeoffs myself, including where to spend on reliability and where a simpler answer was good enough. For anyone evaluating whether I can take something from empty repository to a running service with real billing, this is a clear example.

Screens

04 images, select to enlarge
Next projectLone Star UIA React 19 component library on Base UI, Tailwind CSS 4, and CVA, published to npm as ESM with full type declarations.

Hiring a senior frontend engineer?

I'm looking for my next role on a product team, building design systems and AI tooling. The resume has the details, and my inbox is open.