Start for free

Do more with a browser video SDK than you can with Editframe

Editframe is a code-first video SDK with browser (WebCodecs) rendering and an optional cloud render API. Rendley shares that client-side approach but adds a mature editing engine, a prompt-to-video REST API, an official MCP server, and 25+ AI models.

Start for freeSee comparison
Unlimited exportsFree planBrowser-based

Editframe is arguably the closest architectural match to Rendley: a genuinely client-side JS SDK that renders in the browser via WebCodecs, with an optional cloud render API and a generous free tier. Rendley builds on the same in-browser foundation but is a more established engine, adds a deterministic REST API with a prompt-to-video agent, a first-party hosted MCP server, and 25+ aggregated AI models.

One platform, three surfaces

Everything ships in code.

SDK
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.

REST API
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
# 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.

3
Surfaces in one platform: SDK, API, MCP
25+
AI models built in, added as they launch
18
Tools in the hosted MCP server
EU
Assets stored in Germany (Hetzner)
How they compare

Where Rendley Studio pulls ahead.

Both render in the browser — the engine underneath

Editframe and Rendley agree on the hard part: real client-side rendering with WebCodecs. The difference is maturity and scope of the engine you are building on.

Rendley Studio
  • @rendley/sdk renders client-side with WebCodecs and WebGL, FFmpeg (WASM) fallback
  • The same engine powers app.rendley.com and export.rendley.com in production
  • Published on npm; Pixi.js and Lottie under the hood for layers and motion
  • Framework-agnostic JS/TS — drops into any front end
Editframe
  • Genuinely client-side SDK with browser rendering via WebCodecs
  • CLI rendering plus AnimeJS and SVG integrations
  • Newer and smaller, but a true in-browser approach like Rendley’s

Cloud render and streaming

Both offer cloud rendering beyond the browser. Editframe’s cloud path is maturing with usage pricing; Rendley’s render API is deterministic and job-based with signed-URL delivery.

Rendley Studio
  • REST API at api.rendley.com/v1 with an OpenAPI schema
  • Deterministic edit spec — the same request returns the same edit
  • Long operations run as jobs; poll to done, then pull a signed URL
  • Cloud renders run on GPU workers; client-side rendering also available
Editframe
  • Optional cloud render API with parallel rendering
  • Cloud storage plus CDN streaming for outputs
  • Transparent usage pricing per minute; cloud path still maturing

MCP, agents, and AI models

Rendley adds an official MCP server, a prompt-to-video agent, and 25+ aggregated models. Editframe is focused on the SDK and cloud render.

Rendley Studio
  • Hosted MCP server (mcp.rendley.com) with 18 tools; open source, Apache-2.0
  • Prompt-to-video agent endpoint (/agent/sessions)
  • 25+ AI models: Veo, Kling, Seedance, Sora, Flux, DALL-E, ElevenLabs
  • Works with Claude, ChatGPT, Cursor, Codex; requires a paid plan
Editframe
  • Developer-friendly docs, including an llms.txt for AI tooling
  • No first-party MCP server
  • AI generation is not the core focus
The details

Rendley Studio vs Editframe, side by side.

Rendley StudioEditframe
Client-side browser renderingYes — @rendley/sdk (WebCodecs/WebGL)Yes — client-side SDK (WebCodecs)
CLI renderingRender via SDK and REST APIYes — CLI rendering
Cloud render APIYes — api.rendley.com/v1, OpenAPI, jobs + signed URLsYes — optional cloud render (maturing), CDN streaming
Deterministic edit specYes — same request returns the same editCheck vendor docs
Official MCP serverYes — hosted, 18 tools (Apache-2.0)No first-party MCP
Prompt-to-video agentYes — /agent/sessions endpointNo
AI generation models25+ aggregated (Veo, Kling, Seedance, Sora, Flux, DALL-E…)Not the core focus
Object storage regionEU — Hetzner, Nuremberg (Germany)Check vendor docs
Pricing modelPlans + credits: Free, $15, $30, $70/mo (1 credit = $0.01)Free ≤3 employees; Team $49/mo; Cloud $99/mo + usage

Competitor details are from public pricing and documentation and can change. Verify current specifics on the vendor’s own site.

Credit where due

Where Editframe is the stronger choice

  • Editframe’s free tier is genuinely generous: the client SDK, browser and CLI rendering, and commercial use are all included for companies with ≤3 employees, so small teams can ship at no cost.
  • Its cloud render pricing is transparent and usage-based ($0.02/min at 1080p up to $0.07/min at 4K), which is easy to reason about for pay-as-you-go workloads.
  • On pure architecture it is the closest match to Rendley: a real client-side WebCodecs SDK, with AnimeJS and SVG integrations that some code-first teams will prefer.
  • It is developer-first and lightweight, including an llms.txt for AI tooling, which can be appealing if you want a focused SDK without a broader platform around it.
Best-in-class AI models, built in

Generate clips, images, and voiceovers without leaving the editor. New models are added as they launch.

KlingVeoSoraSeedanceNano BananaElevenLabs
FAQ

Asked. Answered.

They share the same core idea — real client-side rendering in the browser with WebCodecs. The main differences are maturity and scope: Rendley’s @rendley/sdk is the production engine behind app.rendley.com, is framework-agnostic, and sits alongside a deterministic REST API, a hosted MCP server, and 25+ AI models. Editframe is a newer, more focused SDK with a maturing cloud path.

Create your next video in minutes.

Free to start, with no length caps. Try it on a real project.

Start for free