Webflow Cloud Guide 2026: Full-Stack Apps on Webflow

Webflow Cloud went generally available in July 2025 and has been building out fast since. As of 2026, it is a serverless hosting and deployment platform that lets you deploy Next.js and Astro apps - either mounted at a path on an existing Webflow site or hosted independently on their own domain. Apps run on Cloudflare Workers using V8 isolates, distributed across Cloudflare's global edge network.

For agencies and SaaS teams that already work in Webflow, Cloud removes a common architectural split: marketing site in Webflow, product or app experience on Vercel or Netlify, inconsistent component systems between them. Webflow Cloud brings the app into the same platform, with DevLink keeping components shared.

For teams considering Cloud for the first time, this guide covers what it is, what it runs, how the storage and limit model works, what DevLink does, and when Cloud is the right choice versus a separate hosting provider.

What Webflow Cloud Is

Webflow Cloud is a serverless hosting and deployment platform for full-stack web apps. It connects to GitHub, deploys via Cloudflare Workers, supports Next.js 15+ and Astro 5+ through the Cloudflare adapter for each framework, and ships with three built-in storage primitives. As of September 11, 2026, it also supports no-framework static apps built with plain HTML, CSS, and JavaScript.

The compute runs in V8 isolates on Cloudflare's global network - the same runtime as Cloudflare Workers. This means fast cold starts, strong isolation, low latency at the edge, and strict resource limits. V8 isolates are lightweight but have stricter constraints than container-based runtimes. Apps with heavy custom logic or large dependency trees can hit CPU time and memory limits faster than they would on a Node.js container platform like Vercel.

Two Deployment Modes

Site-connected apps. Deploy a Next.js or Astro app mounted at a path on an existing Webflow site - for example, yoursite.com/app or yoursite.com/docs. The app and the site share the same domain. The app can access the Webflow CMS via the Data API. DevLink keeps Webflow Designer components available to the app as React components. This is the tightest integration mode.

Standalone apps. Deploy a Next.js, Astro, or static app on its own domain, without a Webflow site attached. Available as a project type in the Webflow dashboard. Apps count toward your Workspace project limits the same way sites do. This mode is for teams that want Webflow Cloud's hosting and storage infrastructure without a Webflow marketing site attached.

Supported Frameworks

The edge-only runtime is the most important constraint to understand before building for Webflow Cloud. Apps run in V8 isolates, not Node.js. APIs that require Node.js-specific modules - fs, path, native binaries, full crypto, certain database drivers - are not available or are limited. This is the same constraint as all Cloudflare Workers apps. If your Next.js app uses Node.js APIs extensively, it may require adaptation or may not be suitable for Cloud without significant refactoring.

Verify current framework support and runtime constraints at developers.webflow.com before starting a build. Webflow's changelog shows active additions to runtime support in 2026.

Cloud Storage: Three Primitives

Webflow Cloud ships three serverless storage types, each scoped to your Cloud environment and deployed automatically with your app. No provisioning, no separate vendor account, no DNS configuration.

The storage is environment-scoped - each environment (production, staging, development) has its own storage instances. Data does not automatically share across environments. This is correct behavior for production safety but worth planning for if you need to seed staging environments from production data.

Storage limits by plan are usage-based and scale with your Webflow site plan. Webflow provides at least 30 days notice before charging for exceeding storage limits. Check the current limits at webflow.com/pricing - Webflow adjusted allocations in the June 2026 plan changes and specific numbers require verification at publication time.

DevLink: Design System Continuity

DevLink is the capability that makes Webflow Cloud meaningfully different from just deploying to Cloudflare Workers directly. It exports your Webflow Designer components - the visual components built in the Designer - as fully-typed React components (TSX) into your codebase.

The result: a button, card, or navigation component designed in Webflow is available as a React component in your Next.js or Astro app, using the same styles, tokens, and design decisions. When a designer updates the component in Webflow, the developer runs a DevLink export and gets the updated React component. Design and code stay aligned without a manual translation step.

DevLink Export in 2026

As of the April 28, 2026 DevLink changelog, the export system was significantly upgraded:

New webflow devlink export command replaces the old webflow devlink sync. It runs interactively on first use, saves configuration to webflow.json, and executes without prompts on subsequent runs - including in CI pipelines.

TypeScript by default. Exported components are fully-typed .tsx files with JSDoc comments. Set ts: false in webflow.json to emit .jsx instead.

CSS scope isolation. Exported styles are wrapped in CSS @scope rules tied to each component's wrapper, preventing DevLink styles from leaking into the rest of the app. Global styles (normalize, defaults, variables, tags, classes, fonts) are imported from a single global.css loaded once at the app root.

Component filtering. New components and componentGroups regex filters in webflow.json scope the export to a subset of your library rather than exporting everything.

Native Slot support. Webflow's native Slot element replaces the old DevLink Slots. Existing DevLink Slots get an in-canvas Convert action.

The CLI 2.0 update (May 29, 2026) consolidated the webflow library command group into webflow devlink and raised the Node.js minimum version to 22.13.0. If you are on an older CLI version, upgrade before running DevLink exports.

DevLink Workflow for Agencies

The practical workflow for an agency building a site-connected app:

1. Design components in the Webflow Designer - buttons, cards, hero sections, navigation
2. Run webflow devlink export to export those components as TSX into the Next.js or Astro project
3. Import and use the exported components in the app's pages and layouts
4. When designs change, run the export again - CI can automate this on every Webflow publish
5. Design tokens from Webflow Variables appear in the exported CSS variables, available to the whole app

The result is a single design source of truth that spans the Webflow marketing site and the app experience. Component updates in the Designer propagate to both without manual coordination between designers and developers.

Pricing and Limits

Webflow Cloud pricing is usage-based and bundled into your Webflow site plan - you do not pay for a separate Webflow Cloud subscription. Compute (app requests and CPU time) is included in monthly plan allotments. App bandwidth counts toward your overall site bandwidth. Storage limits scale with the plan.

The June 2026 pricing update changed specific allotments. Current limits are on the Webflow pricing page at webflow.com/pricing - verify before building a Cloud-dependent app, as Webflow updated these figures in 2026 and numbers change.

What is metered:

• App requests (number of requests processed)
• Active CPU time (time the isolate is actually running, not waiting on external calls)
• Storage (database rows, KV entries, object storage bytes)
• Bandwidth (shared with site bandwidth)

What is not metered:

• Time spent waiting on external API calls (I/O wait time does not count toward CPU time billing)
• Build and deployment actions (separate from runtime compute)

Surge protection is included to prevent unexpected traffic spikes from generating large unexpected bills. Webflow turns on surge protection automatically.

Webflow Cloud vs Vercel: The Cost Comparison

For teams already on a Webflow site plan, Cloud compute is included - you are not adding a hosting bill. For the same workload on Vercel, you would pay Vercel's usage-based rates on top of your Webflow site costs.

The comparison flips for teams that do not already have a Webflow site. If the only goal is deploying a Next.js app, Vercel's free tier and competitive Pro pricing may be more cost-effective than adding a Webflow site plan specifically to access Cloud hosting.

Environments and Deployment Workflow

Webflow Cloud supports multiple environments: production, staging, and development. Each environment is isolated - separate storage, separate deployment, separate domain or path configuration.

Deployment is via the Webflow CLI:

# Install CLI

npm install -g @webflow/webflow-cli

‍

# Authenticate

webflow auth

‍

# Deploy to production

webflow cloud deploy

The CLI connects to your GitHub repository, builds the app, and deploys to Cloudflare Workers. The build happens on Webflow's infrastructure, not locally.

CI/CD integration: The webflow cloud deploy command runs in CI pipelines without prompts after initial configuration. Teams typically deploy on merge to main, with staging deployments on PR branches.

Environments and branches: Each environment can be connected to a specific Git branch. Production connects to main. Staging connects to a staging or preview branch. Development environments are for local testing.

DevLink Practical Setup

For a new Next.js app connected to a Webflow site:

Step 1: Install CLI and authenticate

npm install -g @webflow/webflow-cli

webflow auth

Step 2: Initialize a new Cloud project

webflow cloud init

This connects the project to your Webflow site and sets up webflow.json.

Step 3: Export DevLink components

webflow devlink export

On first run, the interactive setup walks through configuration. Subsequent runs execute without prompts. Components export as .tsx files into the directory specified in webflow.json (default: ./webflow).

Step 4: Import in your Next.js app

// Import DevLinkProvider at app root

import { DevLinkProvider } from '../webflow/DevLinkProvider'

import '../webflow/css/global.css'

‍

// Use exported components

import { HeroSection, PricingCard } from '../webflow/components'

Step 5: Automate in CI Add webflow devlink export to your CI pipeline after Webflow publishes. When a designer updates a component, the CI run on next deployment picks up the change automatically.

Runtime Constraints to Plan For

V8 isolates have specific limits that differ from Node.js containers. Teams building complex apps should account for these before committing to Webflow Cloud.

CPU time limits. Requests have a maximum CPU time budget. Apps with heavy synchronous computation - complex data transformations, image processing, intensive string operations - can exceed this limit. Move heavy computation to external services where possible.

No persistent connections. V8 isolates do not support long-lived connections. Traditional database connections (PostgreSQL, MySQL via TCP) do not work in the V8 isolate context. Use Webflow Cloud's built-in D1 (SQLite at the edge), or HTTP-based database APIs (PlanetScale's HTTP driver, Neon's serverless driver, Supabase REST API).

No full Node.js APIs. The fs module, native binaries, certain crypto APIs, and other Node.js-specific modules are not available. Check each dependency's Cloudflare Workers compatibility before adding it to the project.

Bundle size. V8 isolate deployments have bundle size limits. Large dependency trees - especially those with many transitive dependencies - can exceed these limits. Audit bundle size before deploying and use tree-shaking aggressively.

For workloads that regularly exceed these constraints, Vercel with a Node.js runtime is the more flexible option.

When to Choose Webflow Cloud

Use Webflow Cloud when:

You have an existing Webflow site and want to add an interactive app experience at a mount path. The site-connected mode, Webflow CMS access via Data API, and DevLink component sharing are all only available in Webflow Cloud.

Design-system continuity between a Webflow site and a Next.js app is a priority. DevLink is the only tool that exports Webflow Designer components as production-ready React components. Teams that need the same components in both contexts have no equivalent on other platforms.

You are already paying for a Webflow site plan and want to deploy a Next.js or Astro app without adding a separate hosting bill.

Edge-first, globally distributed hosting is a requirement. Webflow Cloud deploys to Cloudflare's global network by default with no additional configuration.

Consider Vercel or an alternative when:

Your app relies on Node.js-specific APIs that are not available in V8 isolates. Full Node.js compatibility, native modules, and persistent TCP connections require a container-based runtime.

You need Vercel-specific features: ISR (incremental static regeneration), on-demand image optimization, Vercel Workflows for long-running processes, Vercel AI SDK, or mature observability tooling.

The project has no existing Webflow site and does not need Webflow CMS or DevLink. On Vercel, a Next.js deployment requires no additional plan cost at hobby/pro scale.

The app has a large, complex dependency tree that could hit V8 isolate bundle size limits.

Work with Hedrick

Webflow Cloud, DevLink, and the Figma-to-Webflow pipeline are all capabilities our team works with directly. Hedrick is a Webflow-exclusive development and design agency. We build Webflow sites, Webflow Cloud apps, and the DevLink integrations that keep design systems consistent across both. If your team is evaluating Webflow Cloud for an agency or SaaS project, we can help with architecture decisions and implementation.

Get in touch

A Note on Sources

Webflow Cloud general availability (July 2025) and current capabilities from multiple sources including pravinkumar.co, shadowdigital.cc, and help.webflow.com/hc/en-us/articles/40846212086035-Webflow-Cloud-overview. Framework support (Next.js 15+, Astro 5+) and Cloudflare Workers/V8 isolate architecture from vercel.com/kb/guide/vercel-vs-webflow-cloud and vercel.com/kb/guide/astro-on-vercel-vs-webflow-cloud. Storage primitives (D1, KV, R2) from webflow.com/updates/cloud-storage and shadowdigital.cc. DevLink Export major upgrade (April 28, 2026 changelog) from developers.webflow.com/home/changelog/2026/4/28 - official Webflow developer changelog. CLI 2.0 update (May 29, 2026, Node.js 22 requirement) from developers.webflow.com/home/changelog/2026/5/29. Static app support added September 11, 2026 from developers.webflow.com/home/changelog/2026/9/11. Webflow Cloud pricing (usage-based, bundled into site plans, June 2026 changes) from webflow.com/blog/webflow-cloud-pricing. V8 isolate constraints from pravinkumar.co citing official Webflow Cloud documentation. All technical claims verify against official Webflow developer documentation at developers.webflow.com before publication.

Frequently Asked Questions

Does Webflow Cloud Require a Webflow Site?

No. Webflow Cloud supports both site-connected apps (mounted at a path on a Webflow site) and standalone apps (deployed independently on their own domain). Standalone apps count toward your Workspace project limits the same way sites do. DevLink and Webflow CMS access are only available in site-connected mode.

What Frameworks Does Webflow Cloud Support?

Next.js 15+ and Astro 5+ are supported using Cloudflare adapters for each framework. As of September 11, 2026, static apps (plain HTML, CSS, JavaScript with no framework build step) are also supported. Vue, Svelte, and other frameworks are not available as of September 2026. The runtime is V8 isolates, not Node.js - apps that rely on Node.js-specific APIs require adaptation or an alternative platform.

How Is Webflow Cloud Priced?

Usage-based and bundled into Webflow site plans. You do not pay for a separate Webflow Cloud subscription - compute allotments (requests and CPU time) are included in your site plan, with bandwidth counting toward overall site bandwidth. Storage limits scale with the plan. Webflow updated specific allotments in June 2026; verify current figures at webflow.com/pricing before building a Cloud-dependent app.

What Is DevLink and How Does It Work?

DevLink exports components you build in the Webflow Designer as fully-typed React (TSX) components into your Next.js or Astro codebase. Designers update components in Webflow. Developers run webflow devlink export to receive the updated components as TSX files. The result is a shared design system across the Webflow site and the app, without manual translation. CSS scope isolation (added April 2026) prevents DevLink styles from leaking into the rest of the app.

How Does Webflow Cloud Compare to Vercel for Next.js?

Webflow Cloud is better when you have an existing Webflow site and want to add an app at a mount path with DevLink component sharing and Webflow CMS access. Vercel is better when you need full Node.js API compatibility, ISR, Vercel-specific features (Workflows, AI SDK, image optimization), or when there is no existing Webflow site and no need for DevLink. Both deploy Next.js; the decision comes down to which integrations and runtime capabilities your specific app requires.

What Are the Limits of the V8 Isolate Runtime?

V8 isolates have CPU time budgets per request, no persistent TCP connections (so traditional database connections do not work), no full Node.js API support (fs, native binaries, certain crypto APIs), and bundle size limits. Apps with heavy computation, large dependency trees, or Node.js-specific dependencies need auditing before deployment. For workloads that exceed these constraints, Vercel's Node.js runtime is the more flexible option.