Kelvin Biffi
EN PT
Résumé

Renderster

Send JSON or use the editor. Get a finished video back.

Role
Founder, design and engineering
Status
In production
Stack
Go 1.23 · chi · pgx · Redis
Link
renderster.com ↗

01The problem

Rendering video from code usually means babysitting FFmpeg on a server that falls over under load and loses jobs when it does.

02What I built

Video rendering as a service, and the media engine behind ViralRecast. A visual editor or a JSON spec goes in, a finished video comes out. Go API and workers on a Redis queue, FFmpeg underneath, output on Cloudflare R2.

03The decision that mattered

The same render has two doors: a visual editor for people and JSON for machines. The API docs are generated from the code, including an llms.txt, so an agent can read the API without a human translating it.

04Receipts

  • Go in production: Go 1.23 backend with chi, pgx and go-redis
  • asynq queue with retry, backoff, visibility timeout and dead-letter
  • Concurrent FFmpeg workers with goroutines, output on Cloudflare R2
  • OpenAPI and llms.txt generated from the code

05Stack

  • Go 1.23
  • chi
  • pgx
  • Redis
  • asynq
  • FFmpeg
  • Cloudflare R2
  • React
  • Konva
  • Zustand
  • OpenAPI
Next case Mentezinha An AI for kids that knows when to say no.