How to self host using reverse proxy
Reverse proxy hosting is a modern way to integrate an existing hosting provider or infrastructure with your Framer site for full control over headers, authentication or delivery. Every modern hosting platform like Vercel, Netlify, CloudFlare or AWS supports it.
How it works
You can really think of this as “automatic uploading”. Instead of downloading and uploading a new version after every update, your server can just ask the Framer site directly for the requested page and save it so it can be served from your host (and optionally modified).
Technically, you tell your hosting platform to simply forward the request from a client to your Framer site under the hood, optionally modify it (like setting headers and adding authentication) send it back and cache it locally so the next request gets served directly from your host (skipping typical manual upload steps).
We typically see customers use proxy hosting if they:
Want to integrate different websites under a single domain. Proxy rewrites allow you to point different paths to different origins. So /hello could point to one Framer site, /signup to another, all while the main index could be another site built in Next or React directly. This approach is very popular and sometimes called micro frontends.
• Want to add authentication, analytics or cookies to the requests before they send them.
• Want to add an additional layer or server side analytics or optimizations.
• Want to add an additional layer of caching for reliability and performance.
• Make sure traffic gets served from “vetted” enterprise infrastructure in larger companies.
How to set it up
We have articles for the most common hosting platforms, but any one supporting reverse proxy setups works.
• How to host with Google App Engine
• How to integrate with your current site
• How to host with nginx / apache / varnish
• How to host with Netlify
• How to host with Vercel