Your video, made by chat.

No. The agent writes scenes for you. JavaScript is just the underlying surface — read it if you're curious, ignore it if you're not.

Claude Code and Codex today. Anything that speaks ACP or supports MCP can drive Libi.

No. Libi runs locally — a SQLite database and your own files, on your machine. It never holds an API key: generation providers live in your own agent's config, and requests go straight from your machine to the provider you chose.

Three backends — instant ffmpeg stream-copy when nothing's been re-rendered, ffmpeg with overlays for declarative comps, and the canvas pipeline for code-driven scenes. The router picks automatically.

Yes. Add any MCP server to your own Claude Code or Codex and the agent uses it inside Libi too — Agents → Providers sets up the common generation ones for you. Write Skills as Markdown files, or use Libi's own tools from any MCP client. The protocol surface is open by design.

Yes — properly. Libi is licensed under GPL-3.0-only, an OSI-approved open source license, and the full source is on GitHub. You can read it, build it, modify it, fork it, and use it commercially — including selling a fork — without paying us anything. The one thing GPL asks in return is reciprocity: if you distribute a modified version, you ship its source under GPL too, so improvements that reach other people stay open. See the LICENSE file and LICENSING.md in the repo.

Yes. Free for individuals, agencies, and companies of any size. No seat caps, no signup, no time limit. Use it on commercial projects, ship videos to paying clients, build internal tooling on top of it. Private use and internal modification carry no obligations at all — GPL only asks for source when you distribute the software itself to someone else. And the videos you make are yours: the license covers libi's code, not your output.

Yes — genuinely. Fork it, change anything, run your modified version internally forever with no obligations, distribute it, or sell it. GPL explicitly permits selling. Run your own backend services that the libi client talks to, too. The only condition is reciprocity: anyone you distribute the software to gets its source under GPL-3.0 as well. One ask that isn't legal boilerplate — please give your fork its own name. The code is licensed to you; the libi name and logo aren't.

The editor is free, forever. We sell one optional membership — for a single user or a team — that adds cloud services on top: sharing pieces, assets, and characters across teammates, cloud backup you can restore from any machine, and an opt-in managed model offering with usage tracking and per-member limits. More joins the membership over time, including a Viral DB of trending-video analyses the agent can search, and a posting scheduler with performance analytics. All optional, and none of it gates what's already in the box. There's a waitlist you can join from inside the app.

For using libi as a tool — almost certainly. GPL obligations attach to distributing the software, not to using it, so making videos with libi creates no obligations at all and your output is completely unencumbered. Internal use and internal modification are equally unrestricted. The conversation to have with legal is only if you plan to embed libi's code into a product you then distribute — that's when copyleft applies and your distributed work would need to be GPL too. GPL-3.0 is among the most-reviewed licenses in existence, so most legal teams already have a settled position on it. Point them at the LICENSE file and LICENSING.md in the repo.