Webflow Enterprise is the only Webflow plan with a 99.99% hosting uptime commitment, single sign-on and SCIM, according to Webflow's pricing page in November 2026. The plan one step below it, Team, launched on 13 May 2026 at $2,500 a month on an annual contract and commits to 99.00% hosting uptime. That gap, about 53 minutes of allowed downtime a year against about 88 hours, is the clearest single reason a company moves to Webflow Enterprise.
This guide compares Enterprise with the Premium and Team plans line by line, sets out what public data says about the price (Webflow does not publish one), and ends with a short test for whether you need it. Figures come from Webflow's own pages unless stated, and we label vendor claims as such.
The Webflow plan ladder after May 2026
Before May 2026, the usual question was Business or Enterprise. Business no longer exists. Webflow folded the CMS and Business Site plans into a single Premium plan and moved existing customers onto it as their sites renewed. Former Business customers kept most limits, with one drop: included bandwidth fell from 100 GB to 50 GB, with add-ons available.
The comparison that matters now has three rungs. Premium is the self-serve plan most marketing sites run on. Team is what Webflow calls an all-in-one offering for teams that have outgrown self-serve "but aren't ready for Enterprise". Enterprise is the quoted plan above both.
| Item | Premium | Team | Enterprise |
|---|---|---|---|
| Price | $25 a month yearly, $39 monthly | $2,500 a month, annual contract | Quoted |
| CMS items | 20,000 | 20,000, more for a fee | Custom |
| CMS Collections | 40 | 100 | Custom |
| Static pages | 300 | 500 | Custom |
| Seats included | Bought on the Workspace plan | 5 full, 5 limited | Custom |
| CMS API requests a minute | 120 | 600 | Custom |
| Bandwidth | Up to 2.5 TB a month | Up to 30 TB a year | Custom |
| Hosting uptime commitment | Standard agreement | 99.00% | 99.99% |
Source: Webflow pricing page and Site and Platform plan comparison tables, read 2026-11-04; Webflow blog, Simplified plans and updated pricing, May 2026
Two details are easy to miss. Premium is priced per site, while Team and Enterprise are platform plans that bundle the site with seats, Localize and AI credits. And the limits on Team are published, while almost every Enterprise limit reads "Custom", which means it is set in the contract.
Our guide to Webflow CMS limits covers the item, Collection and reference field caps in detail, including the rollout dates for sites in Agency Workspaces.
What Webflow Enterprise adds over Team
Team already brings much of what used to be Enterprise-only. Webflow's launch post lists publishing workflows, page branching, single-page publishing, the site activity log, custom SSL certificates and custom security headers, all on Team. So the honest comparison is Team against Enterprise, not Premium against Enterprise.
| Area | Feature | Team | Enterprise |
|---|---|---|---|
| Identity | Single sign-on | No | Yes |
| Identity | Just-in-time provisioning and SCIM | No | Yes |
| Governance | Custom roles | No | Yes |
| Governance | Granular access, down to pages and Collections | No | Yes |
| Governance | Design approvals | No | Yes |
| Governance | Audit logs API | No | Yes |
| Staging | Private staging and a custom staging domain | No | Yes |
| Platform | Site and Workspace management APIs | No | Yes |
| Support | Customer success manager, solutions architect, phone | No | With Premium SLA |
| Contract | Agreement type | Terms of Service | Master Services Agreement |
Source: Webflow pricing page, Team and Enterprise comparison table, read 2026-11-04
Identity is the usual trigger. If your IT team requires every SaaS tool to sit behind the company's identity provider, with accounts created and removed automatically, only Enterprise offers SSO and SCIM. Webflow's hosting page says the same: SSO is included for Enterprise.
Governance is the second. Team has publishing workflows and page branching, so drafts can be reviewed before they go live. What it lacks is control over who can touch what. Custom roles and page-level or Collection-level permissions let a regional team edit its own pages and nothing else.
The support row has a condition. A dedicated customer success manager, a solutions architect and phone support are marked "Available with Premium SLA" on Enterprise. Read that as a further tier inside the Enterprise contract, not a default. Ask for it by name if you need it.
The contract changes form. Team runs on Webflow's Terms of Service. Enterprise runs on a Master Services Agreement, which is what procurement teams usually want to redline.
Uptime and support commitments, in hours
Percentages hide how much downtime a commitment allows. The table converts Webflow's published figures into hours a year, using 8,760 hours.
| Commitment | Team | Enterprise |
|---|---|---|
| Hosting uptime | 99.00% | 99.99% |
| Allowed hosting downtime a year | About 87.6 hours | About 53 minutes |
| Designer and platform uptime | 99.90% | 99.90% |
| Response to a major incident | 12 hours | 1 hour |
| Response to a minor incident | 24 hours | 4 hours |
Source: Webflow pricing page, SLAs section, read 2026-11-04; downtime hours are our arithmetic
The editor uptime is the same 99.90% on both. A team that worries about the Designer being unavailable during a launch gets no stronger commitment by upgrading.
Security and compliance: what is already on every plan
A lot of security review questions are answered before you reach Enterprise. Webflow's security page lists SOC 2 Type II, ISO 27001, ISO 27017, ISO 27018 and PCI-DSS, and its hosting page adds CCPA and GDPR. These certifications cover the platform, so a Premium site sits on the same audited infrastructure as an Enterprise one.
What Enterprise adds for a security review is access and paperwork. The Enterprise page mentions access to Webflow's Enterprise Whistic profile, a defined incident response SLA and an escalation path. The pricing page also lists help with custom security questionnaires.
One limit applies on every plan. Webflow's security page says it is not HIPAA compliant by default and is not designed to store or process protected health information. A healthcare company that needs patient data on its site needs a separate compliant backend whatever plan it buys.
What Webflow Enterprise costs
Webflow does not publish an Enterprise price, and we will not invent one. Three public signals help you set a budget before the sales call.
| Signal | Figure | What it covers | Caveat |
|---|---|---|---|
| Team list price | $30,000 a year | One site, 10 seats, published limits | The floor below Enterprise, not Enterprise |
| Vendr purchase data | Median $37,125 a year; $10,000 to $81,743 | 134 Webflow purchases through Vendr | All plans, before the May 2026 change |
| Forrester TEI composite | About $470,000 licence cost over 3 years | A $2 billion company running several sites | Commissioned by Webflow; present value |
Source: Webflow pricing page, read 2026-11-04; Vendr, Webflow pricing, updated February 2026; Forrester Consulting, The Total Economic Impact of Webflow, September 2024
Read Team as the floor. Webflow positions Team for companies not yet ready for Enterprise, so a buyer who needs Enterprise features should expect a quote above $30,000 a year. That is inference from the positioning, not a published figure.
Vendr is a proxy. Its sample is buyers who used Vendr's procurement service, so it skews to larger companies, and it mixes all Webflow plans. Its page says Enterprise pricing "depends on seat count, site volume, support tier, and contract length", and that multi-year commitments and prepayment often bring further discounts at the Enterprise level. Parts of the same page still describe Workspace plans retired in May 2026, so treat the detail with care.
The Forrester figure is vendor-commissioned. Webflow paid Forrester Consulting to model a composite organisation built from five customer interviews. The headline, a 332% return over three years, comes from that model, and Forrester notes other organisations may see different results. Its cost side is more useful: licences of about $470,000 over three years, plus $143,000 for an outside agency and $22,000 for training, all risk-adjusted present values.
Add-ons move the number. On Team, Optimize and Analyze are optional add-ons, extra locales and seats cost more, and more CMS items are sold separately. On Enterprise these lines read "Custom". Price the add-ons you will actually use, not the full list.
Who actually needs Webflow Enterprise
Most marketing sites do not. Our Webflow statistics roundup shows Webflow runs 0.8% of all websites but 2.3% of the top 10,000, so its customer base runs from small sites to large brands. The question is which requirement forces the move, and whether Team already meets it.
| Requirement | First plan to check |
|---|---|
| One marketing site, a small team, under 20,000 items | Premium |
| More than 40 Collections or more than 10 reference fields | Team |
| Reviewed publishing and page branching for a growing team | Team |
| Faster API writes for a large migration | Team, at 600 a minute |
| SSO and SCIM required by IT | Enterprise |
| Editing rights split by region, brand or page | Enterprise |
| An uptime commitment above 99% in the contract | Enterprise |
| An MSA that procurement can negotiate | Enterprise |
Source: Webflow pricing page, read 2026-11-04; our reading of the plan tables
B2B SaaS companies tend to hit Team first. A growing SaaS site adds Collections for integrations, templates, a glossary and customer stories, and passes 40 before it passes 20,000 items. Our piece on Webflow for B2B SaaS shows where that architecture gets bent.
Regulated and global companies hit Enterprise. Fintech, cybersecurity and large healthcare firms usually have an identity policy and a vendor review. Companies with regional marketing teams need permissions that stop one market editing another.
Migrations change the timing. Webflow says Team's API limit is five times the self-serve limit. If you are moving thousands of items, our checklist of what Webflow migration services should include covers the plan, and the API ceiling is part of the schedule.
How to approach the Enterprise sales conversation
Write the requirements before the call. List the identity provider, the number of editors by role, the number of sites and locales, the item count in two years, and the uptime figure procurement will accept. Webflow quotes against those variables.
Ask for the limits in writing. Every "Custom" cell on the pricing page becomes a number in the order form: items, Collections, static pages, API rate, bandwidth, locales and seats. Get each one.
Check what Team cannot do before you pay for Enterprise. If the only gap is 40 Collections or the API rate, Team may cover it at a published price.
Agree how agencies get access. The pricing page lists a guest role that lets agency and freelance partners work without becoming full Workspace members. Our post on the Webflow Agency Workspace plan explains how transfers work when a partner builds for you, and it is worth reading before you add one.
What this means for your Webflow plan decision
Start from the requirement, not the plan name. If the only pressure is CMS size or API speed, Team at a published $30,000 a year probably covers it. If IT requires SSO and SCIM, procurement wants an MSA, or regional teams need their own permissions, Webflow Enterprise is the plan that offers them, and the price will be quoted.
We build marketing sites in Webflow and applications in Next.js, so read this comparison knowing we work inside Webflow every week. Across 20 or more Webflow sites in twelve months, the largest CMS we built held over 1,200 items, well inside Premium's 20,000. We would scope the content model and permissions first, then match the plan, and we quote each build per project. Our Webflow development service page explains how we scope a build on any Webflow plan.
