Platform
Vercel
Collected. Compares a Vercel project’s environment variables, with one project-scoped token per service.
The job receives one JSON token map keyed by repo and service. Each child gets only its own token, as VERCEL_ACCESS_TOKEN; the map itself never reaches a child.
Pre-flight pins the project and the Vercel targets to the allow record. A malformed token map fails with a fixed message that never quotes a value.
Vercel collection runs as its own platform slice, in its own job.
More platforms
All platforms →- 01
CapRover
Collected. Compares a CapRover app’s environment with its 1Password source, pinned to one captain domain and app name.
- 02
Render
Known to env-sync, but has no platform rule here, so pre-flight drops any service with a Render target.
- 03
AWS SSM Parameter Store
Known to env-sync, but has no platform rule here. AWS variables are deliberately kept from every child.