LastPass vs Keeper
Two long-standing business password managers with different strengths: LastPass on policies and directory integration, Keeper on compliance and outside sharing.
The short answer
- Choose LastPass for its policy depth (100+ on Business), broad directory integrations, and familiarity.
- Choose Keeper for a lower price, extensive certifications (FedRAMP High, FIPS 140-3), privileged-access options, and One-Time Share for people outside.
- For logged, repeatable or two-way handoffs, add CredenShare to either.
Who this page is for: businesses comparing LastPass and Keeper.
LastPass vs Keeper at a glance
| LastPass | Keeper | |
|---|---|---|
| Business price | Teams $4.25 (up to 50); Business $7; Business Max $9 per user/month | Business Starter $2 (5–10 users); Business $3.75; Enterprise $5 per user/month |
| Encryption | AES-256; PBKDF2-SHA256 (600,000) | AES-256-GCM; PBKDF2 (1,000,000) |
| Certifications | ISO 27001 (Schellman); SOC 2 Type II; SOC 3 | SOC 2 Type 2; ISO 27001/27017/27018; FedRAMP High; FIPS 140-3; PCI DSS Level 1 |
| SSO | None on Teams; 3 apps on Business; unlimited on Business Max | SAML 2.0 |
| Provisioning | Directory integrations (Business and above); SCIM via Okta and Entra ID | SCIM and AD/LDAP (Enterprise) |
| Sharing with non-users | Between LastPass accounts; its help says recipients must create an account | One-Time Share, up to 180 days, device-locked; can collect fields |
Checked on October 23, 2026. Both pricing pages showed placeholders, so prices are from each vendor's own blog (LastPass, May 2026; Keeper, January 2026), billed annually. See the sources below.
Which is cheaper, LastPass or Keeper?
Keeper. For 10 people billed annually: Keeper Business is $37.50 a month, against $42.50 for LastPass Teams and $70 for LastPass Business.
Which is more secure?
Both encrypt locally with AES-256. Keeper uses AES-256-GCM with 1,000,000 PBKDF2 iterations; LastPass uses 600,000. Keeper lists a longer certification set, including FedRAMP High and FIPS 140-3.
How do they share with people outside?
- LastPass shares between LastPass accounts. Its Sharing Center article says the recipient "must create a LastPass account".
- Keeper One-Time Share works without a Keeper account, for up to 180 days, locked to the first device. It can let the recipient edit fields and upload files.
Which should you pick? Scenarios
| Your situation | Better fit | Why |
|---|---|---|
| Many granular policies | LastPass Business | 100+ policies. |
| Government or regulated buyers | Keeper | FedRAMP High, FIPS 140-3. |
| Sharing with contractors who won't install anything | Keeper | One-Time Share needs no account. |
| The lowest per-user price | Keeper | From $2 per user. |
| Unlimited SSO apps | LastPass Business Max, or Keeper | Keeper includes SAML SSO. |
What neither LastPass nor Keeper does
Both are built around your vault. How each reaches people outside it:
- LastPass: shares between LastPass accounts; no expiring links found.
- Keeper: One-Time Share, up to 180 days, locked to the first device.
At the edge of the vault, three needs keep coming up that neither covers on its own pages:
- Collecting a credential from someone outside. A client's hosting login or a vendor's API key: there's no request form, so it usually arrives by email or chat.
- Proof that an outside handoff arrived. Their logs track your organization; a per-link record of who opened a share, when and from where, isn't described.
- Handoffs on the recipient's schedule. Links that last longer, or start counting at the first open.
CredenShare is built for that edge, and works with either:
- Secure Requests (Business and Enterprise): send a form with the fields you need; each answer is encrypted in the sender's browser.
- Access logs for every share: views, times and IP addresses, kept 3 to 180 days by plan.
- Expiry from 1 hour to 3 months, optionally from the first open, plus passcodes and view limits.
- Slack, a browser extension, a REST API, SDKs and an MCP server for AI agents.
Shares made in the web app, API and SDKs are encrypted in your browser or client; Slack-created shares are encrypted on our servers. Only the people who create shares and requests need a CredenShare seat.
Before you share a credential: a checklist
These apply whichever tool you use.
- Send the link and the passcode through different channels. For example, the link by email and the passcode by text message.
- Watch out for link scanners. Some email security filters and chat apps open links automatically, which can use up a one-view link. Send the link as plain text through a channel that doesn't pre-open links, or allow a second view with a short expiry.
- Don't open the link to test it. On a one-view link, your test is the view.
- Pick the shortest expiry that works. If you don't know when the recipient will act, a link that starts counting at the first open is safer than a long fixed window.
- Rotate after the handoff when you can. The link expires, but the credential is still valid.
- Keep the original in your password manager. A sharing link is a delivery method, not storage.
Verdict: LastPass or Keeper?
- Pick LastPass for policy depth and directory integration.
- Pick Keeper for price, compliance and One-Time Share.
Whichever you choose, cover the outside handoffs neither is built for.
Related: 1Password vs LastPass · 1Password vs Keeper · CredenShare vs Keeper
Sources (checked October 23, 2026):
- LastPass: blog (business prices), blog (personal prices), business plans, zero-knowledge security, Sharing Center
- Keeper: blog (prices), encryption model, security, One-Time Share, enterprise
LastPass, Keeper are trademarks of their respective owners. CredenShare is not affiliated with any of them.
Frequently asked questions
Add a record to every outside handoff
Share and collect credentials with access logs. Start on the Free plan.