However, "managed" doesn't mean "one size fits all." Webflow's site plans, workspace tiers, and enterprise options each solve different problems, and picking the wrong combination can cost you money or box you into unexpected technical limits.
This guide breaks down exactly how Webflow hosting works under the hood, what each tier includes, where the real limitations are, and how to design a hosting strategy built for a scaling B2B SaaS organization.
Key Takeaways
- Runs on Amazon Web Services (AWS) for origin compute and serves static assets via a global CDN (Fastly and CloudFront) across 250+ edge locations. Paid site plans include SSL, automatic compression, HTTP/2, and global caching.
- Webflow is ideal for marketing sites, blogs, resource hubs, and landing pages. It is not an application backend stack—there is no custom server code execution, native server-side rendering (SSR), or dynamic app database hosting.
- Site plans host individual websites on custom domains. Workspace plans manage team seats, collaboration permissions, and unhosted staging environments. You need both, but they scale independently.
- Most B2B SaaS companies host their marketing site on Webflow while keeping their core product on a dedicated app stack.
How Webflow Hosting Works Under the Hood
If you’re a marketing ops lead or web manager used to handling server infrastructure, Webflow shifts your responsibility away from capacity planning and server maintenance. Understanding the underlying plumbing helps evaluate reliability, latency, and security compliance.
Webflow processes over 2 million requests per second globally. Static assets—HTML, CSS, JavaScript, and images—are stored on AWS origin servers and cached at edge locations closest to your visitors. CMS endpoints and form submissions are handled directly by Webflow’s managed application layer.
Every paid site plan includes:
- Automatic SSL/TLS Provisioning: Certificates are automatically generated and renewed.
- Performance Tuning: Brotli/Gzip compression, HTTP/2 delivery, and responsive image generation run natively without plugins.
- Backups & Recovery: Automatic site snapshots are created on major updates, allowing instant point-in-time restores from the dashboard.
Webflow Cloud and modern App integrations support dynamic capabilities on the front end, but the standard hosting stack remains focused on high-performance static delivery and managed CMS endpoints.
Site Plans vs. Workspaces: What Are You Actually Buying?
The most common point of confusion on Webflow’s pricing page is the difference between Site Plans and Workspace Plans. Mixing these up leads to overpaying or blocking team workflows.
Site Plans
Webflow site plans attach directly to an individual project, so each website gets its own site plan for hosting and publishing on a custom domain.
- Starter (Free): The free plan tied to a webflow account for learning, prototyping, and testing on a webflow.iosubdomain before moving to a paid plan. Limited to 2 static pages, 50 CMS items, 1 GB bandwidth, and a Webflow badge.
- Basic ($15/mo billed annually or $25/mo monthly): This basic site plan is the Basic Plan and often the right plan for simple, static landing pages or microsites that do not need cms functionality. Supports up to 300 static pages and 10 GB bandwidth, but includes no CMS collections.
- Premium ($25/mo billed annually or $39/mo monthly): As Webflow's unified hosting tier for content-driven marketing sites, the Premium plan combines dynamic content capabilities with high-capacity limits. It’s built to host your site with support for dynamic blog posts, up to 20,000 CMS items, 40 collections, form file uploads, site search, and 50 GB base bandwidth.
- Enterprise (Custom): For high-traffic marketing operations that require custom SLAs, SAML/SSO, advanced security controls, and high-volume custom bandwidth limits.
Each project needs its own site plan, and site plan based billing applies per website rather than by workspace.
On the Premium tier, bandwidth add-ons apply if your traffic exceeds 50 GB/month. Additional bandwidth can be added in tiered blocks (starting at 50 GB up to 2.5 TB total) to handle spikes without forcing a site migration.
Workspace Plans & Per-Seat Charges
Workspaces govern your team's internal editing environment, seat management, and staging access:
- Starter (Free): 1 Full seat included for solo building with up to 2 unhosted staging projects.
- Core (~$19/mo base billed annually): Unlocks code export, up to 10 unhosted staging sites, and capacity for basic team collaboration.
- Growth (~$49/mo base billed annually): Unlocks unlimited staging sites, site-level roles, site password protection, custom 301 redirects, and granular publishing controls.
- Enterprise Workspace: Adds Single Sign-On (SSO/SAML), SCIM provisioning, central audit logs, and custom seat pools.
Understanding Seat Billing
In addition to the base Workspace fee, extra team members are billed on a per-seat basis depending on their role:
- Full Seat (~$39/mo per seat): Unlocks complete Designer access, global site settings, and full administrative capabilities.
- Limited Seat (~$15/mo per seat): Built for marketers and copywriters who need to manage content, edit text, and build pages from pre-made components without altering global design systems.
- Reviewer / Commenter Seat ($0/mo): Free read/comment-only access for internal stakeholders.
Connecting Custom Domains and DNS Architecture
For B2B SaaS companies, domain architecture typically splits marketing and product environments across subdomains.
Setup Steps
- Add Domains: Enter both your root (yourSaaS.com) and subdomains ([www.yourSaaS.com](https://www.yourSaaS.com)) into Webflow Project Settings.
- Configure DNS Records: Point root A Records to Webflow's redundant IP addresses, and point the wwwCNAME to Webflow's proxy endpoint.
- Set Primary Domain: Define either the www or root domain as primary to ensure clean 301 redirects and canonical SEO tags.
- SSL Provisioning: Webflow verifies DNS alignment and automatically provisions TLS certificates within minutes.
Security, Compliance, and Enterprise Controls
If your SaaS company undergoes SOC 2, ISO 27001, or GDPR audits, your InfoSec team will evaluate Webflow’s security posture.
Standard Security Features (All Paid Plans)
- Secure hosting on all paid plans with TLS 1.2+ encryption in transit
- DDoS mitigation and bot protection at the CDN edge
- Platform-level SOC 2 Type II compliance
- Automatic security patches and dependency updates
Enterprise Security Controls
Non-Enterprise plans operate on shared security configurations. If your security policy requires granular header-level control, Webflow Enterprise unlocks:
- Custom Security Headers: Configure Content-Security-Policy, X-Frame-Options, HSTS, and Referrer-Policy directly.
- Single Sign-On (SSO): Enforce SAML/SSO via Okta, Azure AD, or Google Workspace for team access.
- Custom SLAs: Standard uptime guarantees (up to 99.99%) paired with dedicated support SLAs.
Performance & Core Web Vitals Optimization
Out of the box, Webflow produces clean HTML/CSS and manages frontend assets effectively. However, performance marketing scripts can quickly degrade these advantages if not managed carefully.
Built-in Optimization Mechanisms
- Responsive Image Srcsets: Images uploaded to the Designer are automatically resized and converted into modern formats (WebP/AVIF).
- Native Lazy Loading: Images and inline frames below the fold defer loading until scrolled into view.
- Asset Minification: CSS and JS bundles are minified automatically upon publishing.
While Webflow's base infrastructure routinely delivers sub-100ms server response times, third-party marketing tags (e.g., Google Tag Manager, chat widgets, heatmaps, AB testing scripts) execute client-side. Load these scripts asynchronously or via server-side tagging to protect your Core Web Vitals (LCP, CLS, INP).
Technical Constraints: What Webflow Hosting Cannot Do
Webflow is built for marketing performance, not full-stack application logic. Understanding its boundaries prevents architectural mistakes.
Webflow vs. WordPress vs. Jamstack
Cost Modeling for B2B SaaS Marketing Stacks
When budgeting for Webflow, evaluate the total cost of ownership (TCO). In addition to base fees, factor in seat assignments and traffic profile needs (bandwidth add-ons) to get an accurate monthly run-rate.
Designing a Webflow Hosting Strategy That Scales
Webflow hosting eliminates the traditional trade-off between design autonomy and infrastructure reliability. By bundling AWS-backed compute, global CDN edge caching, automatic security, and managed CMS pipelines into a single visual environment, Webflow gives SaaS marketing teams full control over site updates without managing infrastructure or pulling core engineering resources away from product development.
Success on Webflow comes down to getting your architecture right from day one:
- Choose the right Webflow plan for your public content demands (use Basic for non-CMS landing pages, Premium for CMS collections/blogs) and budget for bandwidth add-ons if traffic routinely tops 50 GB/month.
- Avoid buying full Designer seats ($39/mo) for non-technical team members.Assign Limited seats ($15/mo) to marketers and content managers to control costs and prevent accidental breaks in your design system.
- Host acquisition channels ([www.yourSaaS.com](https://www.yourSaaS.com)) on Webflow’s managed infrastructure while routing application logic (app.yourSaaS.com) to your dedicated product stack.
- Protect Webflow’s sub-100ms native capabilities by auditing client-side marketing scripts and managing third-party tags closely.
When configured correctly, Webflow isn't just a design tool—it becomes a resilient, low-maintenance foundation for your entire growth engine. Whether you're launching your first MVP or scaling a multi-region enterprise site, choosing the right Webflow plan ensures your web presence remains fast, secure, and ready to scale alongside your business.
Frequently Asked Questions
Can I export my Webflow site and host it elsewhere?
Yes, but with significant trade-offs. Static code (HTML, CSS, JS, images) can be exported on eligible workspace plans (Core and above). However, exported sites lose Webflow CMS, forms processing, native ecommerce, and all dynamic behavior powered by Webflow's managed infrastructure.
If you export and host on Netlify, Vercel, or S3, you become fully responsible for SSL, CDN configuration, forms, and any dynamic functionality. The essential features that make Webflow hosting convenient - automatic scaling, managed SSL, CDN edge caching - no longer apply.
Flowout occasionally supports hybrid setups where core marketing pages stay site hosted on Webflow while certain static microsites or landing pages are exported and deployed elsewhere for specific technical or compliance reasons.
Does Webflow hosting support staging environments?
Yes. Webflow provides staging via webflow.io subdomains, and you can password-protect them for internal reviews. This is how most SaaS teams QA changes before pushing to the live site.
Higher workspace tiers (Core, Growth, Agency) offer more staging sites and branching capabilities with enhanced staging capabilities. The Growth plan and above provide unlimited staging sites. But regardless of tier, you still publish from the same Webflow hosting infrastructure - staging is just an unpublished preview environment.
A typical SaaS workflow: design changes in a branch, review on a password-protected staging link, get stakeholder approval, then merge and publish to the production domain with a single click.
Can I use Webflow hosting for my SaaS app login area?
No. Webflow hosting is not intended for authenticated web apps or dashboards. You cannot run your auth backend, user sessions, or app logic on Webflow servers. There's no server-side code execution or database access beyond Webflow's CMS.
The common pattern: marketing site on Webflow hosting (www.yourSaaS.com), and the product on a separate stack at app.yourSaaS.com, with SSO or redirected sign-in links from Webflow pages. This keeps your marketing site fast and editable by non-developers while your product stack handles everything behind the login.
Flowout designs signup funnels and marketing flows in Webflow while coordinating with product teams on app URLs, tracking continuity, and consistent UX across the marketing-to-product handoff.
How reliable is Webflow hosting during big launches or traffic spikes?
Webflow's hosting infrastructure handles millions of page views daily across its customer base. Webflow automatically scales to handle traffic spikes using AWS auto-scaling and global CDN edge caching. For typical B2B SaaS launch surges - press coverage, Product Hunt features, large ad campaigns - Webflow hosting is generally more than sufficient if the page itself is well-optimized.
Enterprise customers can obtain formal SLAs (e.g., 99.99% uptime) with guaranteed support response times. Flowout routinely prepares for client launches by load-testing marketing pages, deferring non-critical scripts, compressing assets, and ensuring the site loads cleanly under traffic pressure.
Can I add custom security headers if I'm not on Enterprise?
Full custom security headers configuration (Content-Security-Policy, X-Frame-Options, custom HSTS parameters, Referrer-Policy) is an Enterprise hosting feature. Non-Enterprise plans do benefit from automatic HSTS and SSL, but cannot enable full header-level customization.
Workarounds exist: some companies configure certain headers at a reverse-proxy or CDN layer placed in front of Webflow. This adds complexity and requires careful testing to avoid breaking site behavior. It's a viable approach but not a simple one.
