Framer

Proxy traffic from your Ploy-hosted domain to an existing Framer site during your migration.

← Back to Fallback Origins

Find a stable Framer origin URL

  1. Go to your Framer project's Settings, then Domains.
  2. Find either:
    • the free Framer subdomain (under Custom > Get a free Framer subdomain), or
    • the default issued Base URL (a *.framer.app link, shown at the top under Base).

Either one works as a Ploy fallback origin URL — both stay stable regardless of what custom domain is attached to the project.

Framer Site Settings Domains panel showing the Base URL (a .framer.app link) and the free .framer.website subdomain option, either of which works as a Ploy fallback origin URL

Framer as Default fallback proxy

Use the default fallback proxy when you want to start slow on Ploy — building out a few pages at a time (e.g. Ploy serves /blog) and deferring to Framer for everything else during your transition. You can also keep this hybrid setup permanently if you don't need to migrate every page over. Enable Default fallback proxy and point it at the same URL.

Ploy Default fallback proxy setting enabled and pointed at a Framer *.framer.website origin URL, with Preserve Host header off and Enable analytics off

Point select Ploy routes at Framer origin

For any Ploy Routing Rules that need to proxy pages to your pre-existing Framer site, paste that URL into the routing rules editor's Origin URL field. Use the fully-schemed Framer URL without a trailing slash, for example https://ploy-fallback-origin.framer.website.

Ploy routing rules showing Rule 1 (regex ^/$ routed to the Ploy site) and Rule 2 (path prefix /at/framer proxied to a Framer *.framer.website origin URL, with Host set to Preserve and Analytics off)

Ploy Apply Routing Rule Changes confirmation dialog showing a JSON diff that adds a new pathPrefix /at/framer rule with a proxy action to a Framer origin URL and preserveHostHeader true

In this example, any route that matches the prefix /at/framer will serve from Framer. In the example page below, the page is served by Ploy but the content is proxied through to Framer, so it renders as if it came straight from your Framer site:

Incognito browser at https://ploy.computer/at/framer/one showing a Framer page served through a Ploy path-prefix proxy rule to a Framer origin

Troubleshooting

  • The Preserve Host header setting appears to have no effect on Framer's ability to return content to the proxied pages. This may change over time depending on Framer's configuration, so toggle it if your page isn't proxying as expected.