vos vs HyperFrames: where the video lives

Both make video from code an agent writes. They differ on what happens after: a file to claim, or a link that plays and keeps every version.

Updated October 2026

HyperFrames (Apache 2.0, backed by HeyGen) moves fast: a large registry of ready-made blocks, a desktop studio, an extensive agent-skills library and frequent releases. vos is smaller and younger. It competes on what a video becomes once it exists: a program whose words and colours are data, hosted on vos.so at one address, with every version kept.

Side by side

vos vs HyperFrames comparison, October 2026
	vos on vos.so	HyperFrames
Authoring	A JSON config compiled once; words and colours are data with a control over each	HTML, CSS and JavaScript files with timing attributes
Sharing a finished piece	A watch page that plays on arrival, unlisted or public, embeddable	publish: an import page someone signs in to claim, with no player
Changing it later	Drag a control in the studio, or an agent pushes the next version	Edit the composition and publish again
History	Every version kept, with who pushed it, readable on the page	Publishing again updates the page in place
Rendering	One compiled artifact for the preview, the browser export and the server render	Headless Chrome capture, encoded with FFmpeg
Agents	Skills, a headless CLI, and one line each for hosting and for making	Skills catalog, block registry, hosted MCP
Editing by hand	A browser studio	A desktop studio
License	MIT	Apache 2.0

Authoring

vos on vos.so: A JSON config compiled once; words and colours are data with a control over each
HyperFrames: HTML, CSS and JavaScript files with timing attributes

Sharing a finished piece

vos on vos.so: A watch page that plays on arrival, unlisted or public, embeddable
HyperFrames: publish: an import page someone signs in to claim, with no player

Changing it later

vos on vos.so: Drag a control in the studio, or an agent pushes the next version
HyperFrames: Edit the composition and publish again

History

vos on vos.so: Every version kept, with who pushed it, readable on the page
HyperFrames: Publishing again updates the page in place

Rendering

vos on vos.so: One compiled artifact for the preview, the browser export and the server render
HyperFrames: Headless Chrome capture, encoded with FFmpeg

Agents

vos on vos.so: Skills, a headless CLI, and one line each for hosting and for making
HyperFrames: Skills catalog, block registry, hosted MCP

Editing by hand

vos on vos.so: A browser studio
HyperFrames: A desktop studio

License

vos on vos.so: MIT
HyperFrames: Apache 2.0

Where HyperFrames is the better choice

If your team or your agent thinks in HTML and CSS, HyperFrames meets it where it is, and its registry makes the first render very fast. Its desktop studio is a real editor, its CLI is well designed for agents, and HeyGen’s distribution is behind it. For composing from known blocks and rendering in a pipeline, it is an excellent tool.

Where vos fits

vos is for the video that keeps living after the first render. On vos.so it is a link that plays, and the same link is still right after a typo fix, a new colour or the next release, because a change is a new version of the same program rather than a new file. The words and colours are controls, so the person who asked for the video can change it without starting another agent session. If you already have a HyperFrames piece, you do not have to choose: your agent can port it and put it on vos.so.

The honest verdict

Composing from HTML blocks and rendering in CI: HyperFrames, whose registry, skills and pace are real advantages. A video that lives at a link, keeps its history and changes without a prompt: vos. Both are open source, so judge them yourself: github.com/vosjs/vos and github.com/heygen-com/hyperframes.

Frequently asked questions

What is the difference between vos and HyperFrames?

Both turn code an agent writes into deterministic video. HyperFrames compositions are HTML, CSS and JavaScript files rendered by capturing headless Chrome. vos compiles a JSON config whose words and colours are data, and vos.so hosts that program at a link that plays, keeps every version and opens in a studio with a control over each value.

How do I share a HyperFrames video as a link?

HyperFrames publish gives you an import page that someone signs in to claim; it has no player, and publishing again updates it in place. To get a link that plays and keeps every version, paste the vosso host line to your agent: it ports the composition into a vos program and pushes it to vos.so.

Which is better for AI agents?

Both are built for agents. HyperFrames ships an extensive skills catalog, a registry of ready-made blocks and a hosted MCP, and agents author HTML directly. vos keeps the content as data, so a later change is a patch or a drag on a knob rather than another round of generated markup, and every change lands as a version with who made it.

Are vos and HyperFrames both open source?

Yes. vos is MIT and HyperFrames is Apache 2.0. HyperFrames is backed by HeyGen; vos is the engine under vosso, the hosted platform where the same engine plays the watch page, the studio and the export.

Something else? hello@vos.so