Freelance developers manage credentials for 3–8 clients at once. LitePassword keeps each client isolated and makes offboarding a single click.
That's exactly the size LitePassword is shaped around. Same zero-knowledge encryption, same three roles, but priced for freelance developers and solo founders — not enterprise. The Personal or Family plan covers you, and you can start on Free today.
Try free →That's exactly the size LitePassword is shaped around. Same zero-knowledge encryption, same three roles, but priced for freelance developers and solo founders — not enterprise. The Personal or Family plan covers you, and you can start on Free today.
Try free →If you freelance, your credential graph looks different from a startup or agency:
The clean pattern: one vault for your own infrastructure, one vault per active client, archive client vaults at end of engagement.
Each client vault gets its own encryption key. A subcontractor invited to “Client — Acme” cannot see “Client — Lemon.io” — not because of UI hiding, but because their account does not have the wrapped key for the other vault. This is enforced by cryptography, not by access-control rules.
You’re on a call with Client A. You open your password manager to grab a credential. Client A sees the names of every other vault you have. If those vault names include “Client B” — Client B’s competitor — that’s an awkward moment.
In LitePassword you can hide all vaults except the one you’re actively using. The other client names don’t render until you go back to the vault list. (This is also why naming vaults “Client — Name” is better than just “Name” — easier to spot if you accidentally show the list.)
Step 3 is the part most people miss. Revoking access in LitePassword stops them from decrypting future ciphertext. It does not rotate the underlying credential. If the subcontractor knew the literal Stripe key, they still know it after you revoke — you need to regenerate the key on Stripe’s side. See How to revoke shared password access when someone leaves for the full pattern.
A common freelance complaint is “every client uses a different password manager.” That’s reality. You don’t need to consolidate clients into LitePassword — use whatever they hand you for their credentials. Use LitePassword for credentials you own (your infrastructure, subcontractor invites, staging environments). That boundary is what keeps offboarding clean on both sides.
No credit card. Free for one user. Upgrade only when you bump into the limits.
Probably not. The Personal plan ($1.50/mo) gives you 10 vaults and 50 secrets — enough for ~8 active clients. Bump to Family ($5/mo, up to 5 users) the day you bring on a subcontractor.
One shared vault per client. Inside, group by tool. When you finish the engagement, archive the vault (we keep it; no one new can be invited) and hand the client their access list. Per-client isolation also means the client cannot accidentally see another client's credentials if you ever screen-share.
Yes. Use the client tool for credentials they own (their AWS, their Stripe). Use LitePassword for credentials you own (your own dev infrastructure, the staging environments you spin up, your subcontractor invites). Mixing both into the client's tool creates revocation problems on both sides.
Invite them as View only on Family plan. Grant per-vault access to the one client they will work on. They sign up, set a master password, get a recovery key. After 4 weeks, revoke their account. Vault keys rotate automatically.
Hand them a list of every credential they shared with you and ask them to rotate each one. The client revoking your access on their side does not rotate keys on third-party tools — they need to do that explicitly (rotate Stripe key, regenerate GitHub PAT, etc.). LitePassword cannot do that for them.
No formal discount — Personal at $1.50/mo and Family at $5/mo are already priced for freelance and small-team budgets. If you have an unusual situation, write to support.
Create your account in under a minute. Pick a master password. We'll generate your recovery key for you.