Price terms as published

Each line is the vendor’s own wording, split from the price capture checked on 2026-10-11. Nothing here is rounded, converted or re-worded — the full sentences stay in the review below. Lines that carry only a price continue the plan named on the line above, in the vendor’s own order.

2 price terms for HyperFrames
#Plan / termChecked
1Free (Apache-2.0, no license fee, no per-render charge)2026-10-11
2you pay compute and your agent's own model spend2026-10-11

One-liner: HyperFrames is HeyGen’s open-source (Apache-2.0) framework that turns a plain HTML page into a deterministic MP4: you describe a video as a finite HTML document with timed clips and media, a headless browser seeks each frame, and FFmpeg encodes the result. Agents write the HTML; the framework renders it.

Verified facts (GitHub API + raw README/LICENSE + release feed + docs + npm, 2026-10-11)

Attribute Value Source
GitHub stars 60,412 (5,395 forks, 163 watchers) GitHub API, 2026-10-11
Open issues 243 open (GitHub issue+PR combined counter) GitHub API, 2026-10-11
License Apache-2.0 LICENSE raw file, 2026-10-11
Language / stack TypeScript; Puppeteer-core 25 + bundled Chromium + FFmpeg; Node >=22 npm package metadata, 2026-10-11
Contributors 83 (non-anonymous) GitHub contributors API pagination header, 2026-10-11
Created / last push 2026-03-10 / 2026-10-11 (day of this check) GitHub API
Latest release v0.8.145, published 2026-10-10 — the five most recent tags span 2026-10-08 to 2026-10-10 GitHub Releases API, 2026-10-11
Distribution hyperframes on npm, 0.8.145, SLSA-attested build npm registry, 2026-10-11
Recent volume 731,315 npm downloads in the week 2026-10-03 to 2026-10-09 npm downloads API, 2026-10-11
Pricing No license fee, no per-render charge, no team-size threshold, no requirement to use HeyGen’s cloud README license note + GitHub repo page, 2026-10-11

What it actually does

The unit of work is a composition: a finite HTML document with an explicit viewport (data-width / data-height), timed clips carrying data-start and data-duration, media, and zero or more seekable animation runtimes. The runtime reads those timing attributes to control clip visibility and media playback, and when an animation runtime is present it seeks the registered timeline as well — so the HTML stays inspectable and editable by ordinary web tooling while the renderer can jump to any frame.

Everything hangs off one source. The docs lay out the surfaces as a ladder, deliberately ordered smallest-first:

  • CLI — the highest-level surface: npx hyperframes create, check, render --output video.mp4, preview, capture review frames, publish, and drive cloud backends. This is where most people start.
  • SDK — query and change composition HTML programmatically (find an element, edit it, save).
  • Player — embed a seekable composition in a page.
  • Producer — the Node rendering pipeline: capture, encode, audio mix.
  • Engine — low-level seekable-page capture with exact-frame control.
  • Cloud, AWS Lambda or Google Cloud Run — run renders at scale, either managed or on infrastructure you deploy and own.

The docs state the rule plainly: do not start with the rendering engine when the CLI already does the whole job, and do not add the SDK when you only need playback. Most applications should begin with the CLI or Producer.

Agent-first, in a concrete sense

HyperFrames does not ask an agent to learn a new visual tool. It hands the agent a language the agent already writes fluently — HTML, CSS, JavaScript — and ships the knowledge as skills (for Claude Code) and as plugins (for Codex and the wider plugin stores), so the agent can be pointed at the framework and start authoring compositions rather than debugging a video SDK. That is the whole premise: an agent that already knows how to write a webpage becomes a competent video director because the video’s format is the webpage.

A concrete benefit of keeping HTML as the source of truth is a SHA-256 fingerprint on the rendered package, which the preview verifies — the file you see in preview is the code that produced the MP4, not an approximation of it.

The honest read on cost

On licensing, HyperFrames is about as good as it gets: Apache-2.0, no license fee, no per-render charge, no commercial-use threshold, no team-size cutoff, and no obligation to route anything through HeyGen’s cloud.

The two costs that are real:

  • Compute. Rendering runs headless Chrome plus FFmpeg, so you pay for a local machine, or for your own AWS Lambda or Google Cloud Run account when you scale out. Managed cloud rendering exists but is not free either — the README’s “no per-render fees” refers to license fees, not infrastructure.
  • Engineering time. This is the one easy to undercount. You are maintaining a production pipeline on a pre-1.0 framework: staying on a supported Node version (22 or newer), handling FFmpeg, authoring each composition, and tracking a release that lands roughly every day or two.

There is also no HeyGen cloud bill to worry about in the ordinary case, which is worth saying explicitly since the project’s author is HeyGen and the default assumption is otherwise.

The two limits, stated plainly

  • Scope is narrow on purpose. HyperFrames renders one clip and stops. It writes no script, generates no avatars, no images, no voice, and publishes nowhere. If you want a finished marketing video from a prompt, this is one stage of that pipeline, not the pipeline.
  • It assumes a developer’s setup. Node 22 or newer, FFmpeg, a headless browser, and the willingness to read HTML. A marketer with no terminal will not finish the Quick Start unaided.

A third-party review from the week of 2026-10-08 put both limits into a single sentence: scored as a rendering framework it is near best-in-class and costs nothing; scored as a turnkey video product it is deliberately not that thing. That framing matches what the README and the docs actually claim.

Who should run this

  • Developers who already drive a coding agent and want video inside that same workflow rather than a separate visual editor.
  • Teams building automated or personalized video at scale who need deterministic, reproducible MP4s and are willing to own the rendering infrastructure.
  • Anyone blocked by Remotion’s two-tier license — see the comparison entry, which covers the license boundary directly.

Skip it if you need prompt-to-finished-video with a timeline UI, or if you need avatar and voice generation inside the same tool; those live upstream of this framework.

Sources

  • GitHub API: stars 60,412 / forks 5,395 / watchers 163 / open issues 243 / created 2026-03-10 / pushed 2026-10-11 — fetched 2026-10-11
  • GitHub contributors API pagination header: 83 contributors — 2026-10-11
  • GitHub Releases API: v0.8.145 published 2026-10-10, five most recent tags spanning 2026-10-08 to 2026-10-10 — 2026-10-11
  • LICENSE raw file: Apache License 2.0, Version 2.0 — fetched 2026-10-11
  • npm registry hyperframes@0.8.145: Apache-2.0, Node >=22, Puppeteer-core ^25.10.0, SLSA provenance attestation — 2026-10-11
  • npm downloads API: 731,315 in the week 2026-10-03 to 2026-10-09 — 2026-10-11
  • hyperframes.heygen.com /introduction: “The rendering framework that turns HTML into deterministic video” — 2026-10-11
  • hyperframes.heygen.com /developers/overview: composition contract, CLI / SDK / Player / Producer / Engine / cloud surface ladder — 2026-10-11
  • GitHub repo page (heygen-com/hyperframes): Apache-2.0, “no per-render fees or commercial-use thresholds” — 2026-10-11
  • Kompozy “HeyGen HyperFrames Review (2026)” — third-party scope and cost cross-check, published the week of 2026-10-08

All facts above were checked against primary sources on 2026-10-11. This entry follows the official-information policy: we have not run a production account, there is no hands-on claim in this page, and no rating is assigned. The release cadence and star count are point-in-time readings and will move.