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.
Cloudinary is a media platform for storing, transforming, optimizing, and delivering video at scale. Rendley is a compositional video editor: an in-browser SDK, a REST API, and an MCP server for building and rendering edits. They solve different problems and often work well together.
Cloudinary is media infrastructure: upload, URL-based transformation, transcoding, adaptive streaming, and CDN delivery at enormous scale. Rendley is a compositional timeline editor and render engine. They are adjacent, not head-to-head. A common pattern is to edit and render in Rendley, then store, optimize, and deliver those outputs through Cloudinary.
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 key distinction. Cloudinary applies URL-based transformations to media assets. Rendley composes multi-layer edits on a timeline and renders the result. Different jobs.
This is Cloudinary’s home turf and a genuine strength. Rendley focuses on producing the edit rather than running a global media CDN.
Rendley’s REST API and hosted MCP server are built around editing and rendering. Cloudinary’s API is built around upload, transformation, and delivery.
Rendley aggregates 25+ generation models inside a project. Cloudinary adds AI features around media transformation and analysis rather than a multi-vendor generation catalog.
| Rendley Studio | Cloudinary | |
|---|---|---|
| Primary use case | Compositional video editing and rendering | Media storage, transformation, optimization, and delivery |
| In-browser editing SDK | Yes — @rendley/sdk renders client-side (WebCodecs/WebGL) | No timeline editor SDK; URL-based transformation SDKs |
| Timeline composition | Yes — layers, transitions, effects, audio, captions | No — per-asset transformations, not multi-clip editing |
| CDN and delivery | Not a CDN; exports via signed URLs | Yes — global CDN, adaptive streaming, optimization at scale |
| Official MCP server | Yes — hosted, 18 tools | No editing MCP server |
| AI generation models | 25+ aggregated (Veo, Kling, Seedance, Sora, Flux, DALL-E…) | AI transformation and analysis features |
| Object storage region | EU — Hetzner, Nuremberg (Germany) | Check vendor docs |
| Pricing model | Plans + credits: Free, $15, $30, $70/mo (1 credit = $0.01) | Credit-based: free tier (~25 GB), Plus 225 credits/mo, Advanced $224/mo, Enterprise custom (1 credit = 1,000 transforms or 1 GB) |
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.