Updated 2 days ago
Runway App Studio packages creative workflows as apps, with public sharing still unclear

Runway App Studio packages creative workflows as apps, with public sharing still unclear

Paid Runway users can turn an Agent session or Workflow into a reusable creative app. Building, running and hosting use credits, while conflicting official documents leave external public sharing unconfirmed.

An interface around a workflow a team already uses

Runway’s [October 26 App Studio launch](https://runway.com/news/company‑news/introducing‑runway‑app‑studio) introduces a way to turn creative work into a reusable app inside its platform. A user can describe a tool in plain language or convert an existing Agent session or Workflow into an app. The app presents its own interface while using Runway’s image, video and audio models. The workflow‑conversion route is the useful distinction. Instead of asking every teammate to recreate a prompt and model sequence, the creator can fix the prompt, chain and settings and expose only the inputs another person needs to supply. That packages a process for reuse; it does not establish that the resulting media will be accurate, consistent or suitable for release without review.

Runway supplies the app‑building layer

According to the [launch description](https://runway.com/news/company‑news/introducing‑runway‑app‑studio), App Studio writes, tests and deploys the app while the user refines it through plain‑language instructions. Runway says the code remains visible for inspection, changes can be previewed before publication and a previous version can be restored. These are the company’s stated capabilities, rather than an independently tested software‑development guarantee. Apps can draw on existing Brand Kits, Workflows, Assets and References. They also follow the account’s model controls: a model disabled by an administrator is described as disabled inside the apps too. For a team, that means the reusable interface is still connected to its existing model and workspace choices, rather than automatically creating a separate permission policy.

Publishing guidance supports a bounded workspace use

The [sharing help article](https://help.runwayml.com/hc/en‑us/articles/56447820059539‑Sharing‑apps‑from‑App‑Studio) describes an app as a private preview before publication. It documents audiences for the creator alone, everyone in the workspace or specified people who can already sign in to that workspace. It also says later builder changes remain in preview until the creator publishes again, with the live version shown separately. External sharing is less clear. The [launch post](https://runway.com/news/company‑news/introducing‑runway‑app‑studio) says paid customers can publish a link for anyone with a Runway account. The [help article](https://help.runwayml.com/hc/en‑us/articles/56447820059539‑Sharing‑apps‑from‑App‑Studio), however, says sharing is restricted to the workspace and its FAQ says there is no public‑link option. Its own publishing instructions then list “Anyone with a link” among the choices. Those statements conflict. The captured sources therefore do not confirm that sharing outside a workspace is available as described in the launch. The documented private and workspace workflow is a useful subset on its own. Teams planning access for clients or other outside users should keep that external‑sharing question open, rather than treat the announcement as verified access. The help page also says an app cannot currently be deleted or unpublished; restricting its audience to the creator is described as the way to stop teammates opening it.

Paid‑plan access still consumes credits

Runway [says App Studio is included in paid plans](https://runway.com/news/company‑news/introducing‑runway‑app‑studio), without a separate purchase or add‑on. That does not make app operation free: building, running and hosting apps all draw from the existing Runway credit balance. The announcement says each app shows its usage so a customer can monitor spend. The supported starting point is a bounded tool for an existing creative process, with its inputs, version and workspace audience made explicit. Credit use and generated‑media review remain part of using that tool. Broader public distribution remains unresolved in the official guidance captured for this report. Runway founder and CEO Cristóbal Valenzuela at Web Summit in Lisbon on November 11, 2025. Historical company context, not the App Studio launch. Photo: Lukas Schulze / Web Summit via Sportsfile, [via Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Crist%C3%B3bal_Valenzuela,_Founder_%26_CEO,_Runway_(54916364486).jpg), [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Native crop and downscale; no artificial upscaling.

Share this article

PostShare

Related News