Queenside Castle (O-O-O)

Protect your Webflow-hosted assets with Sygnal's "long castle" manouvre.

Sygnal's Queenside Castle manouvre is an extension of our Kingside Castle manouvre. See those docs as well to fully understand the solution.

Goals;

• Disconnect "leeches" who are hosting your Webflow assets directly in their own site

• Replace Webflow's asset hosting with your own, and control all asset hosting 100%

  • Ability to replace and update files like PDFs or videos directly

  • Full access control to assets

  • Ability to directly delete assets

  • Full stats on who is access your assets and from where

• Downstream compatibility with Webflow's designer and ongoing publishing processes

  • i.e. changes in Webflow, new assets added, etc will be automatically picked up and cloned to your private asset store

Approach

Setup Hyperspeed, and perform the Kingside Castle.

Then;

• Setup a personal S3 bucket.

Hyperspeed is custom extended for your setup to include;

• On an asset request;

  • Hyperspeed checks your private asset store first

  • If no match found, it then checks Webflow's store

    • If the asset is found, it clones the asset to your bucket

    • If not found, records an internal 404 block for 1 day to prevent multiple requests

Results

• All of the Kingside Castle benefits
• Full control over your assets, including access control, deletion and replacement

• Full monitoring statistics and WAF control

• Downstream compatibility with Webflow publishing

  • New assets added to the designer or CMS and published will be picked up and cloned

  • Assets added/changes to your private asset store will not be known to WF, but will be utilized in your public site.

​