Vercel
Deploy your product to Vercel. Your factory’s deployment engineer handles the release; you approve it.
What it enables: shipping a product to a Vercel project, either by generating the CI workflow in your own repository or by having Sapient deploy directly.
Connect
Section titled “Connect”Settings → Connectors → Vercel.
| Field | Where to get it |
|---|---|
| API token | Vercel → Account Settings → Tokens → Create |
| Project | The Vercel project name or id that this product deploys to |
| Team / scope | Optional — your team slug, if the project lives under a team rather than your personal account |
The token is encrypted before it’s stored; it never appears in a log, an agent prompt, or an audit entry. Rotate it in Vercel and paste the new one here whenever you like.
GitOps or managed — pick per product
Section titled “GitOps or managed — pick per product”GitOps (recommended). Sapient writes a Vercel deploy workflow into your repository. Vercel deploys the way it always has, from your own CI, and you can read exactly what will run. The factory’s role is authoring and maintaining the workflow.
Managed. Sapient calls the Vercel API directly to create the deployment. Fewer moving parts, but the deploy happens outside your repo’s history.
Choose per product in the product’s deployment settings. GitOps is the better default: the pipeline stays legible and reviewable, and nothing deploys that isn’t in your repository.
Approvals
Section titled “Approvals”Deploying is an approval-gated action. The factory prepares the release and waits; you approve in
the control room, the iOS app, or sapient approvals approve <id>. Nothing reaches production
because an agent thought it was ready.
After the deploy
Section titled “After the deploy”The deployment engineer records the deployment URL and watches the release. If you’ve connected an observability provider, post-deploy health is checked against it and a bad release is surfaced rather than left to be discovered.
Troubleshooting
Section titled “Troubleshooting”“Project not found.” The project name/id doesn’t exist under the scope you gave. If the project belongs to a team, fill in the team slug.
401 from Vercel. The token was revoked or expired. Create a new one and re-paste.
Deploy succeeds but the site 404s. Usually a build-output or framework-preset mismatch on the Vercel side. The factory reports what Vercel returned rather than guessing — check the Vercel build log it links to.
Removing
Section titled “Removing”Remove the connection under Settings → Connectors. Products configured to deploy here stop being deployable until you connect another target; nothing already deployed is touched.