Can you self-host Keeper? The answer is more complicated than you think

Keeper released Self-Managed Keeper in late 2024

It's a big deal for enterprises. For most teams, it's a distraction.

Self-Managed Keeper (SMK) is Keeper's Privileged Access Management (PAM) platform running on your own infrastructure. On-premises. Air-gapped. Zero cloud dependencies. This is built for organizations with critical infrastructure: federal agencies, defense contractors, power grids, hospitals. Teams that cannot afford a cloud breach.

What you need to run it

SMK runs in Docker containers on a 64-bit Linux VM. You manage the reverse proxy. You manage the database. You manage backups. You manage security patches. You control the update schedule. No automatic updates. No managed infrastructure.

Zero-Knowledge encryption works the same way: encryption and decryption happen on the user's device. Keeper never sees your passwords unencrypted. But the operational weight is entirely yours.

The licensing model

SMK pricing is custom and enterprise-only. Keeper doesn't publish pricing. It's a 'request a demo' product. Expect licensing fees per seat plus dedicated support costs.

The minimum operational overhead is substantial. You need Linux systems administration, Docker knowledge, and database administrator skills. This is not a weekend project.

For most teams: Keeper Cloud is simpler

If you just need password sharing and team vaults, Keeper Cloud at USD 2.00 per user per month is often cheaper than running SMK infrastructure yourself. You avoid the ops burden entirely.