Platforms
Platforms and the source
env-sync knows six platforms. The collector collects the two that have a platform rule, CapRover and Vercel, and drops services with any other target in pre-flight.
- 01
CapRover
Collected. Compares a CapRover app’s environment with its 1Password source, pinned to one captain domain and app name.
- 02
Vercel
Collected. Compares a Vercel project’s environment variables, with one project-scoped token per service.
- 03
Render
Known to env-sync, but has no platform rule here, so pre-flight drops any service with a Render target.
- 04
AWS SSM Parameter Store
Known to env-sync, but has no platform rule here. AWS variables are deliberately kept from every child.
- 05
GitHub Actions
Known to env-sync, but has no platform rule here, so pre-flight drops any service with a GitHub Actions target.
- 06
dotenv files
Never allowed. A dotenv target reads an arbitrary file path from the manifest, so it must never get a platform rule.
- 07
1Password (the source)
Every service reads its expected values from a 1Password item. Its credentials are in the base floor that every child receives.
Know which secrets drifted, without seeing them
env-sync-viewer is self-hosted: you run the collector and the viewer in your own infrastructure. Access to the repository is by request.