Many of our enterprise customers have complex tech stacks that require them to connect multiple Webflow projects on a single domain via reverse proxy. While setting up a reverse proxy is a great option for customers to have flexibility during implementation, this approach still requires help from (already stretched) engineering teams. This typically involves maintaining a proxy server and complicated configuration code through yet another third-party tool in the tech stack. The initial setup and any future updates will likely be subject to sprints and tickets, which may take weeks or months to complete.
And so, to make it easier for Enterprise customers to configure reverse proxy rules, we’ve added this as an option to our service level agreements. This service empowers designers and marketers to create seamless experiences for their site visitors, without relying on engineering teams to maintain a proxy server or an additional tool. Configuration, launch, and updates can be completed in a quick and seamless manner with the help of a Webflow Technical Architect.
To learn more about how we can help you configure reverse proxy rules for your Webflow projects, reach out to your Customer Success Manager or get in touch with our sales team.
What is a reverse proxy? Explained simply, setting up a reverse proxy allows customers to direct their site visitors to one or more Webflow projects, all while making them appear as though they’re on the same domain. This allows for flexibility when setting up Webflow alongside existing sites or apps, and/or when integrating multiple Webflow projects under a single domain.
To make it easier for enterprise customers to connect multiple Webflow projects together on a single domain, we’ve added reverse proxy setup as a service to our Enterprise packages.