Webflow switched off its native User Accounts on every site on 29 January 2026, according to its developer changelog. Since then, a client who asks for logins or account dashboards has needed either a third-party add-on or code. That is when an agency that sells Webflow sites usually finds itself quoting a Next.js build it has no one to write.
This guide covers which requests actually need code, what a white-label Next.js partner should own, and how the handover differs from a Webflow site transfer. The platform facts come from the Next.js, Vercel, GitHub and Webflow documentation, read in October 2026.
Which client requests need code, and which do not
Most requests that sound like "we need a developer" can still live in Webflow. The useful test is narrower: does a page need to know who is logged in, which account they belong to, or what a cookie says? If not, Webflow serves it. Our post When a Marketing Site Genuinely Needs Next.js, which goes live shortly, runs that test in full; this is the short form for an agency sorting incoming briefs.
| Client request | Stays in Webflow | Needs a code component or Webflow Cloud | Needs a Next.js build |
|---|---|---|---|
| New landing pages, blog, case studies | Yes | No | No |
| Pricing calculator or product configurator | No | Yes, as a code component | Only if it saves quotes to a database |
| Gated resources behind an email form | Yes, with a form tool | No | No |
| Customer logins and account dashboards | No, native User Accounts are gone | Possible with an add-on or a Cloud app | Usually, if the data is the client's own |
| Content past 20,000 CMS items or 40 collections | No, Premium caps there | No | Yes, or a higher Webflow plan |
| Pages personalised per logged-in account | No | Partly | Yes |
| Server-side integrations with secret API keys | No | Yes, in a Cloud app | Yes |
Source: Webflow pricing and code component documentation; Next.js static exports guide, read 2026-10-28
The server list. The Next.js static exports guide lists 13 features that need a server, among them cookies, redirects, headers, incremental static regeneration, draft mode, Server Actions and route handlers that read the request. A brief that uses none of them can ship as static HTML, which is what Webflow already serves, and the client keeps an editor their marketing team can use.
The CMS ceiling. Webflow's Premium site plan caps a site at 20,000 CMS items and 40 collections, according to its pricing page. Programmatic page sets, large directories and catalogues hit that ceiling. Above it, the choice is a Webflow platform plan or a code build with a headless CMS. Our comparison of Webflow and Next.js for a marketing site puts numbers on both routes over two years.
The middle options before a full rebuild
Two Webflow features now cover much of what used to force a rebuild. A white-label partner should offer them first, because both keep the client inside one tool.
Code components. Webflow's documentation describes each code component as its own React app in a separate Shadow DOM container, rendered on the server by default and hydrated in the browser. Components do not share React context, React Server Components are not supported, `.env` files are not supported, and data fetching runs in the browser against public APIs. A mortgage calculator fits. Anything that needs a secret key does not.
Webflow Cloud. Webflow Cloud hosts a Next.js, Astro or Vite app under a path of a Webflow site's domain. Premium includes 2 million requests and 30 CPU minutes a month, then $2 per extra million requests (Webflow pricing). Read the limits page before promising anything: requests time out at 20 seconds, the worker bundle is capped at 10 MB, and every response's `Cache-Control` header is replaced with `private, no-cache`. That suits a logged-in tool on a few paths, not a high-traffic content page.
When the logged-in area is the product itself, it usually belongs on its own subdomain as a separate Next.js app, with the Webflow marketing site left alone.
What changes when a white-label partner builds in code
The principle stays the same: the partner builds and the agency owns the client. Our guide to white label Webflow development sets out that split for Webflow. On a code build, three lines move.
| Area | Webflow build | Next.js build |
|---|---|---|
| Where the work lives | One Webflow site in a Workspace | A Git repository, a hosting project, a CMS project and third-party services |
| Who can edit after launch | The client's marketing team, in the Designer or Editor | Editors in the CMS; layout changes need a developer |
| What the partner hands over | The site, the CMS model, the page kit | The repository, deployment setup, environment variables, CMS schema, runbook |
| Security patching | Webflow's job | The partner's or the agency's job, under a written clause |
| Recurring tooling cost | One site plan | Hosting seats, CMS plan, monitoring, sometimes auth and database |
Source: Vercel, GitHub and Webflow documentation, read 2026-10-28
Editing. Clients feel this first. A Webflow client changes a layout and publishes. A Next.js client edits content in a headless CMS, and a new section type is a developer ticket. Say so in the proposal.
Confidentiality. Git history carries names. Commit authors and email addresses identify whoever wrote the code, so a partner working under the agency's name should commit with agency-provided identities or squash history before the repository moves. Our article on Webflow white-label agency agreements covers the confidentiality and IP clauses; for a code build, add the repository and its history to the assets assigned to the client.
Who holds the keys. A code build has API keys for the CMS, analytics, email and sometimes payments or a database. Each should be created in an account the client or the agency owns, never in the partner's.
The handover: five accounts instead of one Workspace
Webflow hands a site to a client in one transfer between Workspaces. A Next.js handover is a set of separate moves, each with its own rules.
The repository. GitHub's documentation says a transfer keeps issues, pull requests, webhooks, secrets and deploy keys, and redirects links from the old location. The new owner must accept within one day when the target is a personal account, the target cannot already hold a repository with the same name, and creating a new repository at the old location deletes the redirect permanently.
The hosting project. Vercel transfers projects between teams with zero downtime, according to its documentation. The person moving it must own the source team and be a member of the target team, so the client invites the partner or the agency first. A transfer takes between 10 seconds and 10 minutes.
| Moves with the project | Must be redone after the transfer |
|---|---|
| Deployments and builds | Integrations, added again on the new team |
| Environment variables set in project settings | Variables defined in `vercel.json` |
| Domains and aliases, delegated or moved | Log drains and runtime and build logs |
| Git repository link | Monitoring data |
| Cron jobs, Web Analytics, Speed Insights | Blob storage, through its own transfer |
Source: Vercel documentation, Transferring a project, updated 2026-09-08
The team itself. If the client will own the whole Vercel team, Vercel's knowledge base says there is no transfer button: an owner promotes the client to Owner, then the client removes or demotes the original owner. Owner changes are blocked during a Pro trial.
Everything else. The CMS project, the domain registrar, analytics, email and any database each have their own invite flow. List them in the handover document with the account owner, the billing card and the date each moved, and add a runbook: local setup, deployment, what each environment variable does and who to call when a build fails.
The maintenance clause Webflow never needed
On Webflow, the platform patches the platform. On Next.js, someone has to upgrade the framework, and the contract should say who.
The support window. Next.js keeps a major version in Active LTS until the next major ships, then in Maintenance LTS for two years from its first release. Version 16, released 21 October 2025, is in Active LTS. Version 15 is in Maintenance LTS, with its original end date of 21 October 2026 extended. A site launched today will need at least one major upgrade in its normal life.
Advisories. In March 2025, a middleware authorisation bypass rated CVSS 9.1 affected Next.js from 11.1.4 until the fixes in 12.3.5, 13.5.9, 14.2.25 and 15.2.3; the advisory says deployments hosted on Vercel were automatically protected. In December 2025, a remote code execution flaw in React Server Components, rated CVSS 10.0, hit App Router sites on Next.js 15 and 16. The Next.js team wrote that there was no workaround: upgrade, then rotate secrets if the site was online and unpatched on 4 December.
What to put in the contract. We would write three lines into a white-label code agreement: who watches advisories, how fast a critical patch ships after disclosure, and whether that work sits inside the retainer or is billed.
Pricing and margin on code work
We quote per project for Webflow and Next.js alike, so we do not publish rates. The structure of the cost still changes the agency's margin maths.
A code build includes work a Webflow build does not: rendering decisions, hosting setup, CMS schema, a deployment pipeline and a runbook. Running costs differ too. Webflow's Premium site plan is $25 a month billed yearly. Vercel's Hobby plan is for personal, non-commercial use, so a client site needs Pro at $20 per developer seat a month, plus the CMS, auth and database. Decide early whether the client pays these directly or the agency rebills them.
The retainer changes most. On Webflow it pays for new pages and edits; on Next.js it also pays for upgrades, dependency updates and incident response, which is easier to justify to the client. Our comparison of white label web design against subcontracting and hiring runs the cost side for a 10-person agency.
What this means for agencies selling code they do not write
Sort the request first. Most briefs that mention "custom" or "app" are still Webflow work, sometimes with a code component or a small Cloud app. When a page genuinely needs to know who the visitor is, or the content outgrows Webflow's caps, a Next.js build is the honest answer.
When you sell one, change three things. Write the handover as a list of accounts, each with an owner and a billing card. Put patching in the contract with a response time. Tell the client, before signing, that layout changes now go through a developer.
At Octo we build marketing sites in Webflow and applications in Next.js, which is why we sort briefs this way before quoting. Our white-label service page explains how we scope it.
