Websites serve a lot of purposes and in many scenarios, web developers need to place special files at special URLs on their site.
Unfortunately Webflow has strict limits on the type of files you can upload, and all uploaded files are stored on a separate CDN at URLs that are unrelated to your website domain.
Sygnal Hyperflow solves this by providing a full routing layer that enables you to place special files on your site in special places;
Integrate external code & assets
Embed an entire Github repo, Netlify folder, or Amazon S3 bucket directly in your Webflow-hosted site as a folder to make it accessible and SEO-friendly.
For SEO experts, this is important for asset SEO.
For developers, this can be essential for samesite security considerations.
Compliance & configuration files
Create the files you need and serve them under the compliance-required paths directly. For example-
- ads.txt: This file is used for advertising transparency. It stands for Authorized Digital Sellers and is part of the Interactive Advertising Bureau’s (IAB) initiative to combat fraud in the programmatic advertising ecosystem. It lists all the companies that are authorized to sell a website’s digital advertising inventory.
- .well-known/security.txt: A proposed standard for websites' security information, used to describe the security policies of a web service.
- .well-known/apple-app-site-association: Used for deep linking in iOS apps. This is now supported natively in Webflow.
- .well-known/apple-developer-merchantid-domain-association, used for Apple Pay verification.
- .well-known/assetlinks.json: Used for deep linking Android apps.
- .well-known/browserid: Used for Mozilla’s BrowserID implementation.
- crossdomain.xml: Used by Adobe Flash Player and Microsoft Silverlight to permit cross-domain requests. It’s a security file that controls the ability of external domains to access your content.
- Industry-specific compliance files
- ... and many, many more.
Technical configuration files
Some of these files are already used by Webflow, but we can expand them without affecting Webflow's current needed data availability, e.g.;
- manifest.json: For Progressive Web Apps (PWAs), this file is used to define the application's metadata, appearance, and behavior when installed on a user's device.
- sitemap.xml: Can be auto-generated and then modified programmatically.
How Hyperflow Works
Sygnal's Hyperflow framework is a reverse proxy solution, built on Cloudflare's high-performance edge-serving infrastructure.
Once setup requests that come to your website come to Hyperflow first, and can be cached, enhanced, or modified in various ways depending on the Hyperflow setup you choose and the features you want.
To do this;
- We build our custom Hyperflow reverse proxy, specifically for your needs
- We help you migrate your DNS to Cloudflare, and configure it for the setup you want
What you will need;
- You'll need access to your DNS, to export a "zonefile." This is a text file list of your DNS records that we use to duplicate your DNS in Cloudflare for you.
- You'll need access to your domain registrar, so that you can change your nameservers to point to your new Cloudflare-optimized DNS
- You'll need to disable DNSSEC during the change so that your new DNS is recognized and works properly
If you are already using Cloudflare for your DNS, you're all set, and we can build your reverse proxy directly in your existing Cloudflare account.
