Purley compares what your CMS says should exist against what your host actually built, and gives you a few tools for the gap between the two. Every feature lives on a tab inside a project.
Everything sits inside an organisation. Every account gets one on signup, on the Free plan; upgrading it to Pro unlocks every tool, scheduled checks and team members. Inside an organisation you create projects, and each project is one Prismic repository paired with one Vercel project.
Opening a project shows a row of tabs. The SETTINGS button in the top right of the same page opens the project configuration panel, which is where credentials, routes and languages live. If a project has no Vercel token saved yet, that panel opens automatically and a banner points you at it.
| Tab | What it does |
|---|---|
| url_audit | Lists URLs that exist in Prismic but were never built by Vercel. |
| broken_links | Scans every document for links that point nowhere, internal or external. |
| link_finder | Finds every document that references a given UID. |
| sitemap | Builds a sitemap.xml from the pages in your latest Vercel build. |
| redirects | Edits and publishes your Vercel redirect list without touching config files. |
| webhooks | Batches rapid publish events into a single deploy. |
| builds | Shows recent deployments and, for failures, the errors behind them. |
| datadog | Runs your Datadog Synthetic tests against each successful production deploy. |
Not every tab needs the full configuration. This is the minimum for each one to work:
| Tab | Requires |
|---|---|
| url_audit | Prismic repository, Vercel project ID and token, at least one route |
| broken_links | Prismic repository |
| link_finder | Prismic repository |
| sitemap | Vercel project ID and token |
| redirects | Vercel project ID and token |
| webhooks | Nothing - it only needs a deploy hook URL to call |
| builds | Vercel project ID and token |
| datadog | Vercel project ID and token, plus Datadog API and application keys |
The url_audit and broken_links scans page through every document in your repository and pull the full build log of your most recent deployment. Both ask for confirmation before running, because on a large repository they use a noticeable amount of Prismic and Vercel API quota. Scheduled checks have the same cost on every run, so pick the longest interval you can live with.