Vercel deployments
Proofline reads the deployments of each connected Vercel project: their target, readiness, and creation time, and the commit and branch Vercel recorded for each.
Proofline treats that commit as provenance that Vercel reported, which does not prove what code runs. It does not read build logs, environment variables, or project settings.
Cloudflare Workers deployments and routes
For each Worker script you list, Proofline reads recent deployments and how traffic splits between versions. It also reads the Worker routes in the zones you select.
Build records from Workers Builds are optional. When you turn them on, Proofline records the commit each build reports. See how to connect Cloudflare Workers.
A route that another Worker already serves
As an illustration, a pull request adds the route api.example.com/v2/* to a Worker's configuration.
The zone's live routes show that pattern bound to a different Worker. After the deploy, requests might not reach the new code.
A finding cites the configuration in the diff and the existing route, and suggests moving or removing the old route first.
Questions
What token does Proofline need for Vercel or Cloudflare?
Proofline needs an API token that you create. For Vercel, scope it to the project or team. For Cloudflare, limit it to the read permissions the form lists. Proofline encrypts the token at rest, and it stays valid until you roll or delete it.
Does Proofline track gradual deployments in Cloudflare Workers?
Yes. Proofline records each deployment's version split, including the percentage of traffic each version serves.
Does Proofline change my Vercel or Cloudflare settings?
No. Proofline only reads deployments, routes, and optional build records.