One interceptor, many packs

Payment-page script integrity

Inventory every script on checkout and payment pages, add integrity hashes and per-response nonces, and enforce an allowlist, all in the HTML stream. The aim is evidence that helps with PCI DSS 4.0 requirements 6.4.3 and 11.6.1.

Third-party freeze and front-end SBOM

The pack would pin every external script to a reviewed copy served from your own domain, hold upstream changes until someone approves them, and export a CycloneDX bill of materials of the front end.

Consent enforcement at the origin

The pack would keep third-party tags inert until the consent cookie grants them, and set Consent Mode defaults at the origin before page scripts run. Its inventory would list the third parties that actually fire.

How origin-side enforcement differs

Edge SEO at the origin

Canonicals, hreflang, titles and structured data set at serve time, with no CMS change and no CDN. The pack applies the rules you write to the HTML stream in the interceptor, so once enforced a fix reaches every page the rule matches.

What it fixes and who it is for

Rule packs reference

Response firewall for legacy sites

Mask leaked stack traces and personal data, strip version tells and add missing security headers in the response. For sites on software that no longer gets updates, the response is the layer you can still change.

Write your own

A pack is a declarative JSON file: you can write your own edge-SEO rules in the same format and run them in report mode first. The server can check a pack's signature against keys you trust. Tell us if you would write custom filters.