1Password & op CLI

AdoptFactorial rates 1Password as Adopt (2026). 1Password is where all our credentials live, from personal logins to infrastructure secrets.

1Password stores passwords, API keys, certificates and SSH keys in shared vaults with fine-grained access. Beyond the apps, the op CLI reads secrets in scripts and terminals, either directly (op read "op://vault/item/field") or by resolving op:// references in environment variables and config files at runtime (op run, op inject), so no secret has to be written to disk or committed.

For machines there is 1Password Connect, a self-hosted REST server in front of selected vaults, and a Kubernetes operator that turns 1Password items into Kubernetes secrets and restarts deployments when they change.

Updates

Adopt

1Password is where all our credentials live, from personal logins to infrastructure secrets. Repositories, docs and knowledge bases contain only op:// references, never values. Developers use the op CLI to read secrets into scripts and local setups, and our CI pipelines and Phabalicious fetch theirs from our own 1Password Connect server with scoped tokens. On Kubernetes, the 1Password operator syncs items into secrets for our Helm deployments, including Langfuse and our MCP servers.

This matters even more with coding agents: an agent that needs a token runs op read itself, so the secret goes straight into the command and never appears in the chat, the prompt or the repository.