Integrations

LPM works alongside the tools your team already uses. There are three main integration patterns:

  1. Install LPM packages in CI/CD or production builds — via LPM_TOKEN or OIDC token exchange.
  2. Decrypt the project's env vault inside CI — OIDC-based, no long-lived secret needed (Pro/Org).
  3. Push env values to a deployment platform — Vercel, Netlify, Railway, Fly, GitHub Actions secrets, AWS SSM, AWS Secrets Manager, Coolify, or a generic webhook (Pro/Org).

Quick setup patterns

CI installs with OIDC (no secrets):

lpm setup --oidc          # exchanges CI OIDC for a 30-min read-only token
npm install

CI installs with a static token:

export LPM_TOKEN=<your-token>
lpm setup
npm install

CI decrypts the project env vault:

lpm env pull --oidc --env=production --output=.env

Push env values to Vercel:

lpm env connect vercel --project=<id>
lpm env push --to vercel --env=production

Guides

  • CI/CD — GitHub Actions, GitLab CI, Bitbucket Pipelines; OIDC installs and publishes
  • OIDC for CI env decrypt — let CI decrypt your env vault without a long-lived token
  • Platform integrations for env — push the env vault to Vercel, Netlify, Railway, Fly, AWS, GitHub Actions secrets
  • Deployment — Vercel, Netlify, Docker build images