1) The problem → I want to use Webflow to host my content, but I want it to be fully secure.

2) Why is this important → My clients understand Webflow and our stack is built around it. I don't want to use another CMS. Also, my content needs to be more secure than just basic front-end redirects.

3) What's your plan B → Hope people don't get access to my content. Wait for Webflow memberships.

4) Possible solutions we could build for you → A way to secretly tell Memberstack which pages are which and have Memberstack serve the content dynamically. i.e use fake links on the site which Memberstack maps back to the real page hosted in Webflow.