How Ra picks a model
You do not need to read this section to use CreatorStudio. It exists for Directors who want to know what Ra is doing underneath.
Ra’s routing inputs
Section titled “Ra’s routing inputs”Ra’s routing logic considers, per shot:
- Shot type — wide establishing, close-up, action, dialogue, abstract, product beauty, text-on-screen
- Motion profile — static, slow drift, dynamic camera, high-action, parallax
- Subject — human, character, object, landscape, abstract
- Continuity constraints — does this shot need to match a prior character, location, or grade?
- Style target — photoreal, stylized, animated, documentary, cinematic
- Outcome goal — watch-time, conversion, brand consistency, narrative density
- Your Memory Graph — which models have historically produced approved takes for you
- Live model health — rate limits, latency, model quality trends, pricing
What Ra outputs
Section titled “What Ra outputs”Ra picks one model for each shot, or several running in parallel for A/B. You can override any choice per scene. You can pin a model globally. You can let Ra fully direct.
New models ship transparently
Section titled “New models ship transparently”When a new model ships (e.g. Veo 4), Ra benchmarks it against existing models on your Memory Graph and starts routing work to it where it wins. No migration. No re-onboarding.
Overriding Ra
Section titled “Overriding Ra”- Per scene — “render this scene with Veo instead of Kling”
- Per project — pin a specific model for the whole project
- Globally — set a preference in workspace settings
- Temporarily — “use Runway for the next three renders”
Memory logs every override. Ra uses overrides as training signal for future routing.