npm i @rendley/sdk import { Engine } from '@rendley/sdk'const engine = await Engine.create()await engine.addClip('intro.mp4')await engine.export() // WebCodecs
A real editing engine that renders in the browser.
Mux is developer video infrastructure for encoding, storage, streaming, and analytics. Rendley is a compositional editor and render engine: an in-browser SDK, a REST API, and an MCP server. They live at different points in the pipeline and can pair up.
Mux is best-in-class streaming infrastructure: just-in-time encoding, VOD and live streaming, player SDKs, and Mux Data analytics. Rendley is a compositional editor and render engine. There is minimal direct overlap; the two are adjacent. Edit and render in Rendley, then encode, stream, and measure with Mux.
npm i @rendley/sdk import { Engine } from '@rendley/sdk'const engine = await Engine.create()await engine.addClip('intro.mp4')await engine.export() // WebCodecs
A real editing engine that renders in the browser.
curl api.rendley.com/v1/agent/sessions \ -H "Authorization: Bearer $KEY" \ -d '{ "prompt": "30s launch promo" }' # poll the job, then pull a signed URL
Prompt to video from one deterministic endpoint.
# mcp.rendley.com — Apache-2.0claude mcp add rendley \ https://mcp.rendley.com "Cut a 15s teaser from these clips"
Hosted server, 18 tools, open source.
The core distinction. Mux encodes and streams your video and measures playback. Rendley builds the edit and renders the output. Different jobs.
This is Mux’s home turf and a real strength. Rendley focuses on producing the edit rather than running streaming infrastructure.
Rendley’s REST API and hosted MCP server are built for editing and rendering. Mux’s API is built for encoding, streaming, and analytics.
Rendley aggregates 25+ generation models inside a project. Mux focuses on infrastructure rather than a generative model catalog.
| Rendley Studio | Mux | |
|---|---|---|
| Primary use case | Compositional video editing and rendering | Encoding, storage, streaming, and playback analytics |
| In-browser editing SDK | Yes — @rendley/sdk renders client-side (WebCodecs/WebGL) | No editing SDK; player SDKs for streaming |
| Timeline composition | Yes — layers, transitions, effects, audio, captions | No — streaming infrastructure, not multi-clip editing |
| Streaming and analytics | Exports via signed URLs; no playback analytics | Yes — VOD + live, player SDKs, Mux Data analytics |
| Official MCP server | Yes — hosted, 18 tools | No editing MCP server |
| AI generation models | 25+ aggregated (Veo, Kling, Seedance, Sora, Flux, DALL-E…) | Not a generative model catalog |
| Object storage region | EU — Hetzner, Nuremberg (Germany) | Check vendor docs |
| Pricing model | Plans + credits: Free, $15, $30, $70/mo (1 credit = $0.01) | Usage-based per minute: encoding from $0.015/src-min, storage $0.0030/min, delivery ~$0.025/min; free trial credits |
Competitor details are from public pricing and documentation and can change. Verify current specifics on the vendor’s own site.
Generate clips, images, and voiceovers without leaving the editor. New models are added as they launch.
Free to start, with no length caps. Try it on a real project.