Runway launches App Studio to turn creative workflows into shareable no-code apps
The builder is included with every paid plan, but building, hosting and generations consume credits. Public app links still require a Runway account.
Loading page…
The builder is included with every paid plan, but building, hosting and generations consume credits. Public app links still require a Runway account.
Listen to this story
Runway’s App Studio turns saved Agents, Workflows, or plain-language instructions into hosted apps that lock in prompts, model sequences, and settings for repeatable team use. Launched October 26, 2026, it lets creative teams distribute specialist workflows through Runway accounts, with app-building, hosting, and generations charged against existing credits rather than a separate add-on. Apps can use workspace assets and brand materials, but public-link users must sign in and spend their own credits; Enterprise administrators can restrict access and monitor usage.
During early access, architecture firm KPF built a tool that lets designers mark image regions and draw camera paths to generate directed video of its designs.
Creators can start from a saved Agent or Workflow, or describe an app; they can inspect its code, preview revisions, and restore earlier versions without setting up infrastructure.
Apps can use Runway’s image, video, and audio models, plus workspace Brand Kits, Workflows, Assets, and References.
A creative workflow in Runway can now become an app that teammates use without rebuilding its prompts or model settings. Runway launched App Studio on October 26, 2026, letting paid customers describe tools in plain language and publish them without writing code. Building, hosting and running those apps consume existing Runway credits.
Runway’s starting point is a familiar bottleneck in its own account of creative production: one person figures out the useful combination of models, references and prompts. Others then depend on that person for help or get different results. App Studio is the company’s response—a way to put that person’s process behind a simpler interface for colleagues.
During early access, architecture firm KPF built an app around its design renderings, according to Runway. Designers mark the parts of a still image that should move and draw a camera path. The app then produces directed video of the design, packaging those inputs into a tool for the studio.
Runway’s App Studio lets us build our own AI tools around the way our teams work, so every designer in the studio can use them, not just a few specialists, all within our own environment.
Andy Christoforou, KPF Associate Principal, in Runway’s launch announcement
Customers can start with an existing Agent session or Workflow—a saved generation process—and turn it into an app in one click. They can fix the prompt, sequence of models and settings, leaving teammates only the inputs they need. Runway’s example is a product-photo upload that triggers an on-brand reshoot without asking the operator to choose models or rewrite prompts.
Building from scratch starts with a plain-language description. Runway says App Studio writes, tests and deploys the app, while creators request revisions through further instructions. They can preview changes before publishing and restore earlier versions. The underlying code remains visible for inspection; publishing requires no API keys, hosting setup or separate infrastructure.
At launch, apps can draw on Runway’s image, video and audio models, along with Brand Kits, Workflows, Assets and References. These connect the tool to a workspace’s brand materials and saved creative resources. Creators can update workflows, references or Brand Kits later, with new outputs reflecting those changes.
Every app starts private. Team and Enterprise customers can share with selected teammates, a project or the whole workspace. Paid customers can also publish a public link with a customizable preview. That link is not anonymous access: visitors must sign in with a Runway account, and their generations use their own credits.
Free users can run built-in apps and apps shared with them, but need a paid plan to build their own. When someone generates using their own credits, the output belongs to them and saves to their Assets. Creators choose whether generated assets stay private or go to a project or workspace.
App Studio requires no separate purchase or add-on, but inclusion does not mean unlimited use. Creators pay credits to build an app, generate through it themselves and keep it hosted. Each app displays its usage so customers can track spending across apps and their workspace.
Enterprise administrators retain workspace controls. They can disable App Studio, decide whether public links are allowed and inspect usage across apps. Existing model restrictions also carry over: a model disabled in the admin panel remains disabled inside every app, and users receive an explanation.
Loading discussion...
Join the conversation
Explain when simplicity would help and when you would want more control.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.