Bring verification
closer to the request.

EdgeD connects browser-action protection with supported edge infrastructure. Installation and behavior depend on the provider you use.

Read the quickstart How Verify works

REQUEST PATHIllustrative

Provider-specific integration

Browser request
Provider integration
Verification
Protected application

Browser evidence. Application authority.

01 — PROVIDERS

Two providers.Two different integrations.

EdgeD Connect places browser collection and verification in a supported request path. What that means depends on the provider.

I — Cloudflare

Worker in your zone

A Worker runs in a customer zone, in front of the protected route.

Explicit route coverage
A way to roll the integration back
Historical staging evidence; current lifecycle changes need fresh validation

Browser→Worker · your zone→Origin

II — Vercel

Middleware you install

Customer-installed middleware plus browser collection in your project.

Observe-only
No automatic page injection or enforcement
Has not completed live provider validation

Browser→Middleware · your project→App

02 — BEFORE YOU RELY ON IT

A configuration is not protection. Creating a provider configuration is one step. Check the real request path before treating an integration as active.

Check the domain

Confirm the configured domain is the one serving the protected route.

Check the deployed version

Make sure the Worker or middleware you reviewed is the version that is live.

Check collector reachability

Browser collection has to load for the action to carry proof.

Managed ingress is planned

EdgeD Managed is a separate planned MANDATE-operated offering. It is not implemented or customer-available.