Proton Pass for Business homepage

Your SSH keys deserve the same security as your passwords

Store, share, and rotate developer credentials centrally — with CLI access, SSH agent support, secure sharing, and audit trails built in.

Trusted by over 100,000 businesses and 100 million people worldwide

Enterprise password management from the same team that built Proton Mail — the world’s largest end-to-end encrypted email service. Proton Pass protects the credentials of organizations in healthcare, finance, legal, and government.

The developer credential problem most engineering teams ignore

SSH keys spread across every machine

Managing SSH keys across multiple machines is a persistent security risk. Each engineer stores keys in ~/.ssh on their laptop, home machine, work VM, and every server they’ve provisioned. No central inventory. No revocation process. When an engineer leaves, their SSH keys may persist on systems they configured — with no way to audit which ones.

Credentials hardcoded in source code

API keys embedded in source code — including in repositories that were later made public, or pushed to a remote before anyone caught it. This is the most common vector for credential exposure in engineering teams, and it is almost always invisible until the damage is done.

Secrets shared over Slack and never rotated

Database passwords sent over Slack, stored in someone’s local notes, forwarded to a contractor. No record of who has the key. No rotation schedule. No revocation process.

No offboarding process for developer credentials

When an engineer leaves, which SSH keys do they still have? Which PATs are tied to their GitHub account? Which service credentials did they set up? Without a central inventory, these questions get answered after a security incident — not before.

The CISO’s problem: non-human credentials — SSH keys, PATs, API keys, service passwords — are not in the password manager, not in the HR system, and not in any auditable location. Their blast radius in a breach is unknown.

SSH agent: one vault, every machine

Proton Pass includes a built-in SSH agent. SSH keys stored in your vault are accessible from any device — terminal, scripts, CI/CD pipelines — without copying key files between machines manually.

Centrally stored, available everywhere

Store SSH keys in an encrypted vault. Access them from any machine via the Pass SSH agent — the same key, available everywhere, without insecure file copying between machines or servers.

Revoke in one action

Remove an SSH key from the vault and access is revoked across all machines and contexts simultaneously. No hunting down which servers have a copy. No residual access after offboarding.

No plaintext key files in ~/.ssh

SSH keys in Proton Pass are encrypted at rest. They are not stored as plaintext files that can be read, copied, or exfiltrated from a compromised machine.

CLI access for terminal and automation workflows

What the Proton Pass CLI does

The CLI gives engineers secure, terminal-based access to the vault. Full capabilities:

  • Enables scripting for personal workflows and enterprise user management
  • Secure credential access directly in the terminal
  • Create, read, update, and delete vaults and items
  • Supports: passwords, secure notes, credit cards, identities, WiFi credentials, custom items, and stored SSH keys
  • Vault member management: add, remove, and modify access programmatically
  • Works in CI/CD pipelines, servers, containers, and headless environments via app-password authentication
  • Enables scripted workflows and task automation without hardcoded credentials

End-to-end encrypted in the terminal — independently audited

The CLI uses the same end-to-end encryption as every other Proton Pass client. Credentials are decrypted locally — not on a server that could be logged or intercepted. The CLI was independently audited by Recurity Labs (January–April 2026) as part of their full Pass security review. Finding: no exploits or encryption bypasses identified.

Only the right engineers reach the right credentials

Production stays locked down

Production credentials live in a separate vault from staging and development. Engineers with staging access cannot read production secrets. The access boundary is enforced at the vault level — not by a policy document that depends on human compliance.

PATs, SSH keys, and passwords — all under one policy

Manage Personal Access Tokens for GitHub, GitLab, and CI/CD tools alongside SSH keys and service passwords — all in the same governed environment, with the same vault permissions, the same audit trail, and the same instant revocation on offboarding.

When someone leaves, access ends completely

One admin action removes an engineer’s access to every vault, SSH key, PAT, and service credential simultaneously. No checklist. No missed entry point. No follow-up ticket three weeks later.

Credential health and posture reporting

The admin dashboard provides a full inventory of stored credentials with last-accessed metadata. Pass Monitor flags credentials that appear in known breach data. Identify credentials that have not been rotated, keys shared across multiple engineers that should be individualised, and orphaned credentials from departed team members.

Built for engineering teams at SMBs and mid-market

Proton Pass is not a replacement for HashiCorp Vault or AWS Secrets Manager at enterprise infrastructure scale. It is the right solution for SMBs and mid-market engineering teams that need developer credential governance without a six-month implementation and a dedicated infrastructure team to maintain it.

If your team currently manages SSH keys in ~/.ssh, API keys in Slack, and PATs in a spreadsheet — Proton Pass closes that gap in the time it takes to configure an admin account.

Connects to your existing SSO provider, SCIM directory, and CLI toolchain.

Proton Pass

Bring your developer credentials under control