Skip to main content
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

  1. In Clarion, open Integrations and find Vercel.
  2. Click Install — you are taken to Vercel to authorize the integration.
  3. Choose the team and the projects Clarion may see.
  4. 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, save_firewall_rule and remove_firewall_rule change production. They are gated by your workspace’s tool policy and ask for approval unless you have explicitly allowed them.

Firewall access

The Vercel connection Clarion installs can’t be granted firewall access, so get_firewall_config, list_firewall_events, save_firewall_rule, remove_firewall_rule and the firewall details on project assets need a token you create for each project.
  1. In Vercel, open Account Settings → Tokens and create a token. For Scope, pick the team, then the project.
  2. In Clarion, open the Vercel integration, find Firewall access, pick the project and paste the token.
Clarion refuses a token that can see any other project. On a team with a single project it can’t tell a team-wide token from a project token, so check the scope when you create it.
Vercel has no firewall-only token. A project token can also deploy the project and read its environment variables. Clarion stores it encrypted and uses it only for firewall calls. Revoke the token in Vercel when you remove it from Clarion.
Firewall rules Clarion creates are named Clarion: <title>, are scoped to one exact hostname, and go live without a draft. Clarion only updates or removes rules carrying that prefix, never the rules your team wrote.

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.