Runway Media Router auto-picks the best AI model per job — but it's a developer API that returns raw media. Kompozy routes models and publishes to 9 platforms.
Runway's Media Router, introduced July 23, 2026, is a smart idea aimed at the wrong end of a creator's workflow. It sits inside Runway Dev, Runway's developer platform, and automatically routes each image, video, or audio request to whichever model best fits your priority — quality, speed, or cost — across Runway's own models and third-party ones like Seedance, GPT Image, and ElevenLabs. If you write code and want one API that picks the right generator per job, it's genuinely useful, and this page won't pretend otherwise.
But it's infrastructure, not a content app. I run Kompozy, and the honest framing is that the Media Router and Kompozy solve two different halves of the same problem. The router answers "which model should generate this?" and hands the result back to your application as raw media — a clip, a frame, an audio track. It does not caption for social, reframe per feed, build a carousel or a blog, hold a brand voice across a batch, or schedule and publish anywhere. That other half — turning generated media into a finished, on-brand, published week of content — is the whole job for most creators, and it's what Kompozy is.
So this is a build-versus-buy fork more than a feature fight. If you're a developer or a team assembling your own media pipeline, Runway Dev's router is a strong building block. If you want the model-routing already done and the output already turned into scheduled posts across every platform, you're looking for an engine, not a gateway. Everything below reflects the Media Router as of 2026-07-23; details change, so confirm current specifics on Runway's own pages.
Runway Dev is Runway's developer platform: one API for image, video, audio, and real-time character models, spanning Runway's proprietary models (such as Gen-4.5) plus third-party options, with model swaps done by changing a line of code and spend tracked in a unified billing dashboard. The Media Router is the layer on top that removes the model choice entirely — you set a priority and it selects the best model for the request, using what Runway describes as an intelligence layer built on its creative team's judgment of output across media types (motion in video, composition in images, lip-sync in audio). Runway also ships Recipes (pre-built endpoints for tasks like product ads) and Workflows (custom multi-model pipelines). What it returns is generated media to your code. It is aimed at developers and enterprise teams — Runway cites companies like Adobe, ElevenLabs, Shutterstock, and Cloudflare — who are building their own products and want frontier models behind one billing relationship. It is not a place a non-technical creator logs in to produce and publish posts; captioning, per-platform reframing, carousels, blogs, newsletters, brand-voice governance, scheduling, and publishing are all outside its scope by design.
You'd look past the Media Router for content work not because it's weak, but because it stops three steps before a published post. Even with perfect model routing, you still have to wire the API into an app, take the raw clip or image it returns, caption it, resize it per feed, write the surrounding copy in a consistent voice, generate the formats it doesn't (carousels, quote cards, blogs, newsletters), and build a scheduler that fans everything to every platform. That's an engineering project, not an afternoon. A creator-facing engine that already routes across models internally and ships finished, on-brand content closes the 90% of the workflow the router leaves open — without you writing a line of code.
| Feature | Runway Media Router | Kompozy | Note |
|---|---|---|---|
| Auto-routes each job to the best model | Yes (core feature) | Yes | The router exposes routing to developers; Kompozy routes across models invisibly behind creator-facing formats. |
| Third-party + first-party model access | Yes | Partial | Runway Dev spans many external models via API; Kompozy uses a managed provider set (Claude, OpenAI, Gemini, HeyGen, fal.ai, gpt-image, Pexels). |
| No code required | No | Yes | The Media Router is an API for developers; Kompozy is a no-code app. |
| Returns finished, captioned posts | No | Yes | The router returns raw media to your code; Kompozy renders publish-ready, captioned outputs. |
| Persona / avatar video generation | Partial | Yes | Runway offers character models via API; Kompozy generates HeyGen persona video with face-lock and a Persona Brief. |
| Carousels, quote cards, image posts | No | Yes | Brand-exact carousels and graphics via HyperFrames — outside the router's scope. |
| Blog + email newsletter generation | No | Yes | Long-form text in your voice, governed by the Persona Brief. |
| Multi-platform scheduling & publishing | No | Yes | Kompozy publishes to eight social platforms plus blog and email from one queue. |
| Brand-voice / persona governance | No | Yes | Kompozy enforces voice and banned-word rules across every output; the router is model-agnostic infrastructure. |
| Autopilot (source to published) | No | Yes | Kompozy runs generate-caption-schedule-publish on a recurring basis; the router is a per-request API call. |
| Unified cross-model billing dashboard | Yes | Partial | Runway tracks spend across every model; Kompozy meters finished content in credits across all five buckets. |
| Enterprise API controls (SOC 2, indemnity) | Yes | Partial | Runway Dev targets enterprise builders; Kompozy is a creator/SMB engine with team workspaces on higher tiers. |
| Tier | Runway Media Router plan | Runway Media Router price | Kompozy plan | Kompozy price |
|---|---|---|---|---|
| Entry | Runway Dev (usage-based) | Credit-based, pay-as-you-go per model — see runway.com; no flat creator tier | Kompozy Starter | $99/mo (5,500 credits across all 5 buckets) |
| Mid | Runway Dev (scaled usage) | Scales with credits/generation volume; billed across models in one dashboard | Kompozy Pro | $299/mo (18,000 credits) · API + webhooks + workspaces |
| Top | Runway Enterprise | Custom (sales-led) · SOC 2, IP indemnification, SLAs | Kompozy Enterprise | Custom (sales-led) · white-label + API |
The Media Router proves the direction of the whole market — that no single model wins every job and the value is in the layer that chooses — but it draws that layer for developers, not creators. Its output is a well-chosen clip returned to your application; the content operation around that clip is still an engineering project. Kompozy is that operation, delivered as a product. It routes across a managed set of models under the hood so you never touch a model picker, then turns one idea into persona video, carousels, images, blogs, newsletters, and text posts held to your Persona Brief, and schedules and publishes them to eight social platforms plus email and blog from one review queue — with autopilot if you want it to run on its own. Choose Runway Dev's router when you're building infrastructure and want the best model per API call. Choose Kompozy when you want the routing already done and the content already shipped. Most creators need the second one, and they need it without writing code.
Only in that both route across multiple AI models. The Media Router is a developer API that returns raw generated media; Kompozy is a no-code content engine that routes across models internally and delivers finished, captioned posts published to nine platforms. They serve different users — developers versus creators — so for most people they're not substitutes but different layers.
If you're technical, yes: a team could generate media through Runway Dev's router and bring the output into Kompozy to caption, repurpose into carousels, blogs, and text posts, and publish across platforms. But most creators won't need the router at all — Kompozy already handles model selection behind its formats.
No. It selects the best model for an image, video, or audio request and returns the result to your code. Reframing per platform, captioning, repurposing, scheduling, and publishing are not part of it. Kompozy does all of that after generating the media.
They price for different jobs, so a direct comparison misleads. Runway Dev uses credit/usage-based pricing metered per model; Kompozy sells credits for finished, published multi-format content (Starter $99/mo, Pro $299/mo). Reconcile both against their live pricing pages before deciding.
Effectively yes — it's a feature of Runway's developer platform, accessed through an API, aimed at developers and enterprise teams. If you want model routing without code, a creator-facing engine like Kompozy handles it invisibly behind its output formats.