Connecting Vercel gives Clarion visibility into your deployments and the edge in front of them, and feeds two agents: Vercel Platform for operational and security events, and the Exposure Agent for finding sites that are public when they shouldn’t be.
Estimated time: 3 minutes. You will need permission to install an integration on your Vercel team.
Prerequisites
- A Vercel team where you can install integrations
- The Vercel integration configured for your Clarion instance (contact your administrator if the page says otherwise)
Connect
- In Clarion, open Integrations and find Vercel.
- Click Install — you are taken to Vercel to authorize the integration.
- Choose the team and the projects Clarion may see.
- Return to Clarion; the integration appears as connected.
What Clarion ingests
Events that feed the Vercel Platform agent:
- Deployment failures and their build output
- Runtime errors
- Firewall and attack-challenge activity
- Domain and certificate health
Project discovery into the Brain
Clarion discovers your projects and deployments as assets, along with firewall configuration, log drains, and edge configs. Projects correlate with the repositories that build them and the services that observe them, so a deployment failure resolves to the code and the service behind it.
What agents can do
trigger_redeployment changes production. It is gated by your workspace’s tool policy and asks for approval unless you have explicitly allowed it.
Exposure sweeps
The Exposure Agent uses this integration for its daily sweep: it enumerates hosts and probes each one’s root over read-only HTTPS from the Clarion sandbox, then files an issue per site that is publicly reachable and shouldn’t be. Verdicts are written back to the Brain, so a site you confirm as intentionally public stops re-reporting.
Because the probe runs from the sandbox, that sweep requires the Bash tool category at Protected or above.
Disconnect
Click Disconnect in Clarion, then remove the Clarion integration from your Vercel team. 
