I'm leaning towards self-hosting on this occasion, but Webflow does this funny thing where it doesn't let you self-host collections (like Blog posts).

Oh that's weird -- that's on the CMS side correct? So it would be more like trying to get data exported from the CMS?

A bit more context too. Webflow just makes it easy to update marketing content.

We have stuff on domain.etc/xxxxxxxxxx which is part of our application, everything else goes to the Webflow site which is our homepage.

Webflow forces you to use their hosting solution if you want to manage things like collections. There's sadly no way for us to just self-host the static content which would be preferred.

Thanks for the context, am I understanding right that Webflow isn't letting you route that subpath without paying the obscene amount of money, so you put a proxy in front (Cloudflare) instead.

I know this is a pretty silly suggestion and an attrocious hack, but with webflow already at the root, would a full page iframe on /xxxxxxx work?

And clearly going to just `app.domain.etc` was a non-starter?