Webflow Setup

Webflow does not natively support folder on main domain routing to external origins. To serve Flint pages in a folder on your main Webflow domain (e.g. acme.com/lp/), you need an external reverse proxy. The recommended approach is Cloudflare Workers (free tier works).

• •Your Webflow site continues to serve your main website.
• •Cloudflare sits in front of your domain and routes traffic.
• •A Cloudflare Worker intercepts requests to your Flint folder on main domain and proxies them to your Flint-hosted subdomain.
• •All other traffic passes through to Webflow normally.

Since Webflow itself now runs on Cloudflare infrastructure, this is called an Orange-to-Orange (O2O) setup.

• •A Cloudflare account (free tier is sufficient)
• •Your domain DNS must be managed through Cloudflare (DNS records set to Proxied/orange cloud)
• •Your Flint subdomain (contact the Flint team if you do not know this value)
• •A paid Webflow account with a custom domain connected

For full instructions on setting up the Cloudflare Worker rewrite, see the Cloudflare setup guide.

If you cannot use Cloudflare, AWS CloudFront can also serve as a reverse proxy.

• •Webflow does not configure or support third-party reverse proxies. The Cloudflare Worker approach is self-managed.
• •Webflow offers a managed reverse proxy service for Enterprise plan customers, but the Cloudflare approach gives you more control and works on any Webflow plan.
• •For general Cloudflare setup details beyond Webflow, see the Technical Setup guide.