Overall Satisfaction with KeePass
We use KeePass to store passwords to servers, services, bank card details, etc.
We also use KeePass to store passwords to our client's servers/services.
KeePass is used on two levels:
1) Personal accesses, that should not be shared with other people. For this case, we use private file with private master password.
2) Passwords/usernames to shared accounts that should be shared inside company. For this case, we use shared file that encrypted using password+keyfile, and that is shared automatically via google diive.
We also use KeePass to store passwords to our client's servers/services.
KeePass is used on two levels:
1) Personal accesses, that should not be shared with other people. For this case, we use private file with private master password.
2) Passwords/usernames to shared accounts that should be shared inside company. For this case, we use shared file that encrypted using password+keyfile, and that is shared automatically via google diive.
- Easy to use
- Password's storage with hierarchy
- Price to benefits ratio
- Time-based one-time passwords would be nice addition
- Automatic timeout for inactive - database should lock automatically
- Automatic updates - would be nice that keepass could update on background.
- KeePass is free, so it saves money
- KeePass is local, so it not possible to hack it in a similar way as LastPass
Why KeePass:
- no recurring fees.
- easier to use for small company
- local, so nobody has access to your passwords except you
- more secure than cloud based solutions
- no recurring fees.
- easier to use for small company
- local, so nobody has access to your passwords except you
- more secure than cloud based solutions
Do you think KeePass delivers good value for the price?
Yes
Are you happy with KeePass's feature set?
Yes
Did KeePass live up to sales and marketing promises?
Yes
Did implementation of KeePass go as expected?
Yes
Would you buy KeePass again?
Yes