Cyberia SecretOps
14 / Deployment
Runtime Injection
Wrap any build or start command and the right secrets arrive in the process environment.
In this feature
- cybsecrets run -- npm run build
- Secrets injected in-process, never written to disk
- Works with Netlify, Vercel, GitHub Actions and any runner
- Count of injected secrets logged, values never printed
- Rotation-aware: latest value fetched at run time
- Same command locally and in production
// In the console
What it looks like
cybsecrets run -- <command> resolves the configured scope, injects the environment's secrets into the host environment for that process only, and executes your build or server. Production values never touch the repository, the image or a CI settings screen.
Runtime Injection
Runtime Injection — detail
Deploy
One line in the build command
Prefix the existing build or start command. The platform's own environment screen stays empty apart from a single scoped SecretOps token.
Rotation
Always the current value
Because resolution happens at execution time, a rotated credential is picked up by the next deploy or restart without editing a pipeline.
Hygiene
Nothing to leak
Values exist only in the child process environment. Logs record how many secrets were injected, never what they were.
Included out of the box
cybsecrets run -- npm run build
Secrets injected in-process, never written to disk
Works with Netlify, Vercel, GitHub Actions and any runner
Count of injected secrets logged, values never printed
Rotation-aware: latest value fetched at run time
Same command locally and in production