Join our Newsletter — 33% off our NHI Course
Home› FAQ› Architecture & Implementation› What is the difference between a cloud password…
Architecture & Implementation

What is the difference between a cloud password manager and a self-hosted password vault?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 5, 2026 Domain: Architecture & Implementation

A cloud password manager runs on the vendor’s infrastructure, so the vendor patches, hosts, and operates the service. A self-hosted vault runs on infrastructure the organisation owns or directly controls. That means the organisation gains custody and policy control, but also takes on patching, backups, uptime, and access management for the server itself.

What changes in practice between cloud and self-hosted password storage?

The difference is less about the password list itself and more about who operates the control plane around it. A cloud password manager shifts hosting, patching, and availability to the vendor, while a self-hosted vault makes the organisation responsible for the server, its hardening, backups, access rules, and recovery. That ownership changes the operational burden and the blast radius if something goes wrong.

A self-hosted vault can fit organisations that want tighter data custody, custom network placement, or specific policy controls. It can also be the better fit when the business wants to evaluate enterprise password managers against internal requirements such as auditability, encryption scope, and integration constraints. The trade-off is that the organisation must keep the service healthy enough to remain trusted in day-to-day use.

Cloud services reduce local operational overhead, but they also make the vendor a dependency for uptime, support, and change management. Self-hosting reduces that external dependency, but it increases the need for disciplined administration, especially where a password vault becomes part of broader privileged access management and may hold highly sensitive shared or administrative credentials. In other words, the security question is not only where the vault lives, but who can reliably govern it.

Where the security and resilience trade-offs differ

The biggest practical difference is not feature parity, it is operational responsibility. A cloud service usually centralises patching, scaling, monitoring, and incident handling under the vendor; a self-hosted vault pushes those duties into the organisation's own change, backup, and recovery processes. That means the self-hosted option can fail more often through neglect, while the cloud option can fail more broadly through vendor outage, vendor misconfiguration, or account compromise.

Another key distinction is blast radius. If a cloud password manager is breached, the vendor's infrastructure and the customer tenancy model shape the exposure. If a self-hosted vault is misconfigured or not patched, the organisation may expose the entire vault service directly. For readers assessing attack paths, it is worth pairing this comparison with the common ways credentials are stolen from password stores, because the storage model changes how attackers reach the secret, not whether the secret is valuable.

Self-hosted deployments also create a sharper recovery problem. Backups must be tested, restore procedures must be real, and admin access must be tightly controlled because the vault itself becomes a critical security service. Where organisations use the vault to store high-value secrets, they should also be conscious of secret rotation and audit design, since the operational model needs to support the speed of rotation the business expects.

How to choose the right model for your environment

The decision should start with governance, not branding. If the organisation lacks staff to patch, monitor, back up, and restore a security-critical service, self-hosting may create more risk than it removes. If the organisation needs strong custody, bespoke controls, or a very specific trust boundary, self-hosting may be justified, but only if the server is treated as a production security platform rather than a utility app.

Cloud password managers are usually easier to roll out quickly and more likely to stay maintained by default. Self-hosted vaults are usually chosen when data location, integration flexibility, or control over the runtime matter more than outsourcing operational work. The right answer often depends on whether the organisation can sustain the extra admin load without weakening the very access discipline the vault is supposed to improve. A useful comparison point is how different secrets managers are evaluated, because the same questions about access control, rotation, and audit often apply.

For many teams, the real dividing line is not cloud versus self-hosted, it is whether the platform can be operated with consistent ownership. If no one owns upgrades, backups, recovery testing, and emergency access, the self-hosted option becomes a hidden liability. If those duties are mature and well-run, self-hosting can deliver stronger custody without sacrificing control.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementPassword vaults directly affect credential lifecycle, rotation, and storage control.
AC-2 — Account ManagementBoth deployment models require disciplined ownership of admin and shared access.
CP-9 — System BackupSelf-hosted vaults depend on tested backups and recovery to remain trustworthy.
Recommendation — Manage stored credentials with defined issuance, rotation, revocation, and backup procedures. Centralise account ownership and review access to the vault service regularly. Test backups and restore procedures for the vault as part of operational security.
CIS Controls v8CIS-5 — Account ManagementThe choice changes who manages privileged access and service accounts.
CIS-11 — Data RecoverySelf-hosted vaults create a direct need for verified backup and recovery capability.
Recommendation — Control privileged access to the vault platform and review it on a schedule. Validate that vault backups can be restored quickly and completely.

Practitioner Guidance

What to verify: Before choosing self-hosted, confirm who owns patching, backup testing, restore drills, and privileged access to the vault server itself. If those responsibilities are unclear, the deployment model is already weaker than it appears.

Decision rule: If the vault will hold production credentials or shared administrative secrets, treat platform availability and recovery as part of the security requirement, not just IT operations. If the team cannot sustain that ownership, a managed service is usually the safer operating model.

Common mistake: Teams often focus on where the passwords are stored and ignore the operational burden of running the service that protects them. That usually leads to weak patch hygiene, incomplete backups, or neglected access reviews.

Practitioner takeaway: The storage location matters less than the reliability of the control environment around it, because a secure vault that cannot be maintained, recovered, or governed is not actually a secure vault.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org