<hyperframes-player> and renders it to MP4 on server-side
Chrome and FFmpeg.
Use these templates for a small hosted application. For managed rendering,
distributed infrastructure, or a Node backend, start with
Choose a rendering path.
Vercel
The Vercel template is a Next.js application. Its/api/render route restores
a prepared Sandbox, runs hyperframes render, uploads the MP4 to Blob, and
returns a public URL.
Deploy the Vercel template
Deployment provisions the Blob store. Sandbox access uses Vercel’s runtime
identity. Follow the repository README for current account requirements and
platform limits.
Cloudflare
The Cloudflare template is a TanStack Start application on Workers. ARenderContainer Durable Object runs the renderer and streams the result to
R2. The template also includes optional prompt-based generation with a user’s
own OpenRouter credential.
Deploy the Cloudflare template
Cloudflare Containers require a Workers Paid plan. Disable the optional AI
generation surface before hosting a public demo unless you intend visitors to
submit their own compositions.
Modal
The Modal template exposes a FastAPI application.POST /api/render starts a
separate render function and returns a call ID; the browser polls until the MP4
is available from a Modal Volume.
Use your own composition
Author and check the project locally first:
If the authored canvas is not 1920×1080, also update the player dimensions in
the template. Each repository README names the current file.
Before exposing the endpoint
These repositories are working examples, not a complete multi-tenant render service. Add authentication, request limits, input validation, and cost controls before accepting public render requests. Add a queue when jobs need retries, priorities, or controlled concurrency. For infrastructure designed around distributed jobs, use AWS Lambda or Google Cloud Run.Source
Vercel
Next.js, Sandbox, and Blob
Cloudflare
TanStack Start, Containers, and R2
Modal
FastAPI, spawned functions, and Volume storage