| Authoring and AIHow do visual production, AI changes, and direct file work fit together? | Webflow combines its visual Designer, reusable classes, variables, components, interactions, CMS templates, and role-aware page building with current AI site, section, CMS-item, and code-component capabilities. | Describe the site, refine it through AI, edit visually, or work with project files. AI building and visual editing are both part of the workflow. | [3] [1] [12] [13] [20] |
|---|
| CMS and contentDoes the site need a structured editorial model and generated content pages? | Collections define shared field schemas, items, template pages, and dynamic lists. Current Premium documentation lists 20,000 CMS items and 40 Collections. | A team can build database-backed content and a custom editing workflow on Playcode Cloud. This is an application-specific CMS, not claimed feature parity with Webflow CMS. | [4] [2] [21] [22] |
|---|
| Plan stackWhich plan layers and add-ons can affect the total? | Current new-site annual pricing shows Basic at $15 per month and Premium at $25. Workspace Core is $19 and Growth $49 when billed yearly. Seats, AI credits, bandwidth, add-ons, ecommerce, Cloud, and existing-account transitions can change the total. | Pro currently starts at $25 monthly or $250 yearly with 100 monthly AI credits, unlimited static websites, and three Cloud apps. Current plan and resource limits still apply. | [1] [2] [12] [19] |
|---|
| Production meterWhat grows after launch? | The selected Site and Workspace can meter pages, CMS items and Collections, bandwidth, seats, AI credits, add-ons, ecommerce, and Cloud usage. Legacy-account timing can also affect the available plan. | AI work uses credits. Static websites and full-stack Cloud apps have different plan limits, and Cloud capacity remains a production constraint. | [1] [2] [12] [15] [19] [22] |
|---|
| Hosting and publishingWhat does the managed website path include? | A paid Site plan connects a custom domain to managed hosting and SSL. Role and plan controls can separate staging, review, and publishing responsibilities. | Paid plans include website hosting, custom domains, and HTTPS. Full-stack projects can run on Playcode Cloud under current app and resource limits. | [5] [6] [16] [19] [22] |
|---|
| Application runtimeDoes the website need to become a framework application? | Webflow Cloud documents GitHub-connected framework app hosting with separate requests, CPU, storage, bandwidth, database, and plan meters. Its separate App Gen path can generate apps for Cloud, but Webflow says App Gen development is paused and deprecation will begin; existing apps currently continue to run. | Playcode Cloud runs full-stack apps with backend, database, files, jobs, WebSockets, previews, and recovery on its supported runtime. | [15] [14] [21] [22] |
|---|
| Code and content exportWhat remains runnable after export? | A paid Workspace can export HTML, CSS, JavaScript, and assets. CMS records export separately as CSV. CMS behavior, accounts, ecommerce, forms, search, localization, password protection, and code components do not become a complete external site automatically. | Paid plans include project export. Runtime records, files, identities, secrets, domains, and provider-owned data remain separate exit items. | [7] [8] [19] |
|---|
| Team rolesCan design, content, review, publishing, and site administration be separated? | Workspace and site roles are distinct. Site roles include Site manager, Designer, Marketer, Content editor, and Reviewer, with controls depending on Workspace and enterprise access. | Workspace collaboration is plan-bound. Application roles and record authorization still need to be designed and tested inside the project. | [16] [1] [19] |
|---|
| Ownership and transferWho owns the working site after an agency or client handoff? | The containing Workspace is the default site owner. Client payments can move billing without immediately transferring ownership; an official transfer has separate plan, app, font, comment, locale, and post-transfer access boundaries. | Record the long-term workspace, domain, provider, data, and billing owners before launch. Collaboration access alone is not a complete handoff plan. | [17] [18] [11] [19] |
|---|
| Recovery and exitIs a platform backup the same as an independent live copy? | Webflow documents automatic and manual restore points with plan, permission, and restore-side-effect boundaries. A platform backup and a static export are different controls, and neither alone is a full external disaster-recovery site. | Cloud snapshots restore code, files, and database together to a saved point on the supported path. Git and project export remain separate controls. | [10] [7] [22] |
|---|