What is your process for hosting client websites outside of Webflow to increase revenue and make your agency more profitable, especially for non-CMS websites? Can you please provide information on where you host it, the disadvantages of doing this, and any other considerations to keep in mind? Additionally, if you recommend using another CMS for external hosting, what CMS would you suggest for someone who has only worked with Webflow?

Hosting Webflow-exported sites externally can help agencies increase revenue and maintain client control, particularly for non-CMS projects. Below are the key steps, recommended hosting providers, disadvantages, and CMS alternatives.

1. Exporting a Webflow Site for External Hosting

• Go to Webflow Designer → Click the Export Code button (top right)
• Download the ZIP file containing HTML, CSS, JS, and assets.
• Extract files and review them to ensure there are no Webflow dependencies (e.g., forms requiring external processing).

2. Choosing a Hosting Provider

For static websites (no CMS/dynamic content), recommend:

• Vercel – Fast, free tier, built-in CI/CD (great for developers).
• Netlify – Easy deployment, automatic HTTPS, free tier.
• Cloudflare Pages – Highly optimized, security features.
• Surge.sh – Simplest deployment (one command).

For server-based hosting (clients need backend or forms):

• DigitalOcean / Linode / Vultr – VPS hosting for full control.
• Cloudways (via DigitalOcean/AWS/Google Cloud) – Managed hosting.
• Hostinger / SiteGround – Affordable shared hosting with good support.

3. Disadvantages of Hosting Webflow Sites Externally

• No Webflow CMS – Dynamic content needs another CMS or manual updates.
• No Webflow form processing – Forms require third-party tools (Formspree, Basin, Postmark, etc.).
• No Webflow Editor – Clients can’t easily edit content unless a CMS is added.
• Code becomes static – Future design changes require exporting files again.

4. Alternative CMS Options for External Hosting

For users transitioning from Webflow, these low-code CMS options work well:

• WordPress (Best for customization, plugins, and easy client editing).
• Ghost (Minimalist, fast, great for blogs/magazines).
• Statamic (Flat-file CMS, great for developers and agencies).
• Sanity / Strapi (Headless CMS options with structured content editing).

If keeping static hosting, consider:

• Plasmic – Drag-and-drop Webflow alternative for React projects.
• Eleventy (11ty) – Static site generator for optimized performance.

5. Key Considerations Before Offering External Hosting

• Recurring Revenue Model – Price your hosting & maintenance as a monthly retainer.
• Client Expectations – Ensure clients understand the limitations (e.g., no Webflow Editor).
• Monitoring & Security – Use UptimeRobot, Cloudflare, and backups to prevent downtime.
• Custom Forms & CMS Needs – Choose third-party APIs wisely (e.g., Airtable, Zapier, Formium).

Summary

Exporting Webflow sites and hosting them externally can increase agency profitability but removes Webflow-specific features like CMS, form handling, and the Webflow Editor. Choose a hosting provider based on technical needs (e.g., Vercel for static sites, Cloudways for managed hosting). If a CMS is required, WordPress is the easiest for Webflow users, while Ghost or Statamic are good lightweight options.