Webflow Cloud | Standalone apps now run without a Webflow site
Webflow has expanded Webflow Cloud so apps can now run on their own domains without requiring a Webflow site. Updated on June 1, 2026, the announcement explains that teams can deploy Next.js, Astro, and other full-stack app projects as standalone Cloud apps, or mount them alongside existing Webflow sites while keeping deployments, storage, logs, secrets, and runtime infrastructure in the same workspace.
Webflow Cloud now supports standalone app projects
Webflow Cloud is becoming more flexible for teams that want to build more than marketing pages. Until now, Cloud apps were tied to a Webflow site and lived at a URL sub-path. With the new app project types, those apps can now run on their own domains as standalone projects.
This is especially interesting for web designers, template creators, and development teams because it lets Webflow support a broader project range. A team can keep a Webflow marketing site, build a separate full-stack app, or combine both approaches while staying inside the same Webflow workspace.
How standalone Webflow Cloud apps work
According to Webflow, Cloud apps are regular code projects, not a special Webflow-only format. Developers can deploy frameworks such as Next.js or Astro, connect a GitHub repository, trigger automated deployments through git push, and use Git branches when a project needs multiple environments.
Teams can start from the project dashboard by creating a new app, connecting GitHub, importing an existing repository, or deploying a starter. Webflow also provides CLI commands such as webflow cloud init and webflow cloud deploy for teams that prefer to begin from the terminal.
New workflow options for app and site teams
The most useful change is project flexibility. A Webflow Cloud app can now live on its own domain as a standalone app, or it can sit alongside an existing Webflow site. That gives teams more room to separate marketing pages, tools, dashboards, customer portals, product experiences, and supporting apps without moving to a completely different platform.
Webflow Cloud also includes storage options for different app needs. The article describes key-value storage for sessions, feature flags, and small configuration data, object storage for files such as images and PDFs, and SQLite for relational data, all built into the Webflow Cloud environment.
For teams combining Webflow sites with custom apps, DevLink is another important piece. A component designed in Webflow, such as a header, hero, or footer, can be exported as a React component and reused inside a Next.js or Astro app, helping the site and app share the same visual language.
Why it matters for modern web creators
For animetemplates, the key takeaway is that Webflow is moving closer to a unified workspace for both visual site building and code-based app development. This matters because modern web projects often include more than static pages: they may need app routes, API routes, storage, dashboards, account flows, or interactive tools.
The update also reinforces the importance of design consistency. If a standalone app and a marketing site share the same components, brand system, and deployment workflow, teams can create more cohesive web experiences while reducing the number of platforms they need to manage.
Daisuki's Take: What This Means for Web Designers
We see Webflow Cloud standalone apps as a meaningful step toward bridging visual site building and full-stack development. The real value is not only running apps on their own domains, but giving teams a way to manage sites, app projects, storage, logs, secrets, and deployments inside a more unified workspace.
For web designers and creative teams, this can be useful when a project needs more than a marketing site. Dashboards, customer portals, interactive tools, product experiences, and app routes can live alongside Webflow-built pages while still sharing components, brand direction, and a consistent visual system.
The limitation is that standalone app support still requires strong technical review. We still need to check framework setup, deployment behavior, storage choices, accessibility, performance, security, and whether the app and site actually work together as one coherent user experience.
Sources and Recommended Links
- Webflow Cloud. One workspace for your site and your app. Or just the app. | Webflow Blog (Official)
- Webflow Cloud | Webflow Developers (Official)
- Webflow Cloud CLI | Webflow Developers (Official)
