How it works
1. Ingest
Scan a code with the Framevane app, or point any RTMP/SRT encoder at your server.
2. Process
Framevane composites dynamic graphics and fans the stream out to multiple destinations.
3. Distribute
Go live everywhere at once, with an uncompressed archive saved directly server-side.
Scroll the diagram sideways to follow the whole path.
Overlays that change mid-broadcast
The only self-hosted infrastructure with live-updating graphics driven by a simple API. Forget post-stream clip generation; control your production live. Update any of the five named slots on the fly:
- title
- subtitle
- caption
- ticker
- badge
Update a lower third in real-time from the terminal or your own dashboard:
curl -X POST /sessions/studio/overlay -d '{"title":"Mall Suleiman"}'Two modes, two costs
We are honest about the processing trade-offs. Choose the mode that fits your hardware.
Passthrough Mode
A simple -c copy remux of your stream to multiple destinations. Perfect for lean hardware.
Composite Mode
Decode, overlay graphics, and re-encode before fanning out. Requires robust compute for realtime.
1.5–2.5 vCPU per 1080p30 streamYour keys, your box, your recordings
Self-hosted without lock-in. Framevane runs comfortably on a single Hetzner AX41 bare metal server for about €37/mo. You control the endpoints, you keep the source video, and you own the infrastructure.
The dependencies were chosen to be permissively licensed and deliberately AGPL-free. The one exception is the compositor image, which ships ffmpeg built with libx264 under the GPL.
What the server stores and what leaves it is written down in the privacy policy.