Alternatives to Passbolt logo

Alternatives to Passbolt

LastPass, bitwarden, KeePass, Teampass, and Vault are the most popular alternatives and competitors to Passbolt.
46
196
+ 1
37

What is Passbolt and what are its top alternatives?

Passbolt is an open source password manager for teams. It allows to securely store and share credentials, and is based on OpenPGP.
Passbolt is a tool in the Password Management category of a tech stack.
Passbolt is an open source tool with GitHub stars and GitHub forks. Here’s a link to Passbolt's open source repository on GitHub

Top Alternatives to Passbolt

  • LastPass
    LastPass

    LastPass Enterprise offers your employees and admins a single, unified experience that combines the power of SAML SSO coupled with enterprise-class password vaulting. LastPass is your first line of defense in the battle to protect your digital assets from the significant risks associated with employee password re-use and phishing. ...

  • bitwarden
    bitwarden

    bitwarden is the easiest and safest way to store and sync your passwords across all of your devices. ...

  • KeePass
    KeePass

    It is an open source password manager. Passwords can be stored in highly-encrypted databases, which can be unlocked with one master password or key file. ...

  • Teampass
    Teampass

    It offers a large set of features permitting to manage your passwords and related data in an organized way in respect to the access rights defined for each users. ...

  • Vault
    Vault

    Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log. ...

  • Dashlane
    Dashlane

    Dashlane is a password manager and online security app for everyone who lives, works, and plays on the internet. ...

  • 1Password
    1Password

    Lock credentials and secrets in vaults that sync across systems and seamlessly access within your dev, CI/CD, and production environments. Plus, generate and use SSH keys directly from 1Password, automate infrastructure secrets, and more. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

Passbolt alternatives & related posts

LastPass logo

LastPass

312
312
72
Password manager that works with all browsers & smartphones
312
312
+ 1
72
PROS OF LASTPASS
  • 19
    Synchronised across browsers
  • 16
    Chrome plugin
  • 14
    Passwords stored encrpyted
  • 8
    All devices
  • 8
    Central servers do not have keys
  • 2
    Better then lesspass
  • 2
    The most cost-effective b/t Roboform and 1Password
  • 2
    company wide
  • 1
    Free plan
CONS OF LASTPASS
  • 3
    Slow, unpredictable sync when sharing passwords
  • 3
    UI for admins is an inconsistent mess
  • 2
    Paid
  • 1
    Buggy Chrome add-on
  • 1
    Cannot edit shared password

related LastPass posts

Justin Dorfman
Open Source Program Manager at Reblaze · | 3 upvotes · 302.4K views
Shared insights
on
LastPassLastPass1Password1Password

I use LastPass because it had Android support before 1Password. Also, it's just a great product. It gives me peace of mind with 2-step auth and a YubiKey.

The only thing that drives me nuts is the password generator, sometimes it just doesn't work on certain sites. That is why I wrote/use g20 😎

See more

Firebase Cloud Firestore Cloud Functions for Firebase Google App Engine React React Native React Native Firebase NativeBase Twilio Dwolla.js Yarn fastlane Bitbucket Slack LastPass

See more
bitwarden logo

bitwarden

216
265
107
Free and open source password manager for all of your devices
216
265
+ 1
107
PROS OF BITWARDEN
  • 23
    Open source
  • 16
    All devices
  • 15
    Synchronized across browsers and devices
  • 12
    Passwords stored encrypted
  • 10
    Easy setup
  • 6
    Firefox addon for desktop and mobile
  • 4
    FIDO UTF support
  • 4
    Import & Export
  • 4
    Password Generator
  • 4
    TOTP
  • 4
    Auto-fill
  • 3
    Chrome plugin
  • 2
    Free
CONS OF BITWARDEN
  • 3
    Small Developer Team
  • 1
    Difficult to use

related bitwarden posts

Shared insights
on
bitwardenbitwarden1Password1Password

I’m doing a school project where I have to design a database for a password manager app like 1Password, bitwarden… I’m not sure which database paradigms I should use. Users would have the ability to create vaults and each vault will have many items and can be sorted into favorite, category, tag list… Please help.

See more
KeePass logo

KeePass

69
95
30
A free and open source password manager
69
95
+ 1
30
PROS OF KEEPASS
  • 9
    Free
  • 7
    Password stored encrypted
  • 4
    Password Generator
  • 3
    Plugings
  • 3
    Advanced Search
  • 3
    Import & Export
  • 1
    Biometric unlock
  • 0
    TOTP
CONS OF KEEPASS
  • 1
    Password share is unencrypted
  • 0
    Free

related KeePass posts

Teampass logo

Teampass

8
46
3
A password manager dedicated for managing passwords in a collaborative way
8
46
+ 1
3
PROS OF TEAMPASS
  • 2
    LDAP auth
  • 1
    Open source
CONS OF TEAMPASS
    Be the first to leave a con

    related Teampass posts

    Vault logo

    Vault

    779
    792
    71
    Secure, store, and tightly control access to tokens, passwords, certificates, API keys, and other secrets in modern computing
    779
    792
    + 1
    71
    PROS OF VAULT
    • 17
      Secure
    • 13
      Variety of Secret Backends
    • 11
      Very easy to set up and use
    • 8
      Dynamic secret generation
    • 5
      AuditLog
    • 3
      Privilege Access Management
    • 3
      Leasing and Renewal
    • 2
      Easy to integrate with
    • 2
      Open Source
    • 2
      Consol integration
    • 2
      Handles secret sprawl
    • 2
      Variety of Auth Backends
    • 1
      Multicloud
    CONS OF VAULT
      Be the first to leave a con

      related Vault posts

      Tymoteusz Paul
      Devops guy at X20X Development LTD · | 23 upvotes · 8.3M views

      Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

      It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

      I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

      We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

      If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

      The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

      Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

      See more
      Joseph Irving
      DevOps Engineer at uSwitch · | 8 upvotes · 19.9K views

      At uSwitch we use Vault to generate short lived database credentials for our applications running in Kubernetes. We wanted to move from an environment where we had 100 dbs with a variety of static passwords being shared around to a place where each pod would have credentials that only last for its lifetime.

      We chose vault because:

      • It had built in Kubernetes support so we could use service accounts to permission which pods could access which database.

      • A terraform provider so that we could configure both our RDS instances and their vault configuration in one place.

      • A variety of database providers including MySQL/PostgreSQL (our most common dbs).

      • A good api/Go -sdk so that we could build tooling around it to simplify development worfklow.

      • It had other features we would utilise such as PKI

      See more
      Dashlane logo

      Dashlane

      54
      70
      16
      Dashlane is a password manager and online security app for everyone who lives, works, and plays on the...
      54
      70
      + 1
      16
      PROS OF DASHLANE
      • 4
        Digital wallet
      • 4
        Safe & secure
      • 3
        Best UI
      • 1
        Synchronized across browsers and devices
      • 1
        Passwords stored encrypted
      • 1
        Easy setup
      • 1
        All devices
      • 1
        Firefox addon for desktop and mobile
      CONS OF DASHLANE
      • 3
        Closed Source
      • 2
        No longer has PC app; must be online
      • 1
        Inflexible permissioning

      related Dashlane posts

      1Password logo

      1Password

      433
      281
      20
      Streamline how you manage passwords and development secrets throughout your workflows.
      433
      281
      + 1
      20
      PROS OF 1PASSWORD
      • 8
        Userfriendly UI
      • 3
        Data encryption in transit and at rest
      • 3
        Strong password generator
      • 3
        No third-party tracking in apps
      • 3
        Sync data across devices
      CONS OF 1PASSWORD
      • 4
        Costs
      • 0
        Past Breaches

      related 1Password posts

      Shared insights
      on
      bitwardenbitwarden1Password1Password

      I’m doing a school project where I have to design a database for a password manager app like 1Password, bitwarden… I’m not sure which database paradigms I should use. Users would have the ability to create vaults and each vault will have many items and can be sorted into favorite, category, tag list… Please help.

      See more
      Justin Dorfman
      Open Source Program Manager at Reblaze · | 3 upvotes · 302.4K views
      Shared insights
      on
      LastPassLastPass1Password1Password

      I use LastPass because it had Android support before 1Password. Also, it's just a great product. It gives me peace of mind with 2-step auth and a YubiKey.

      The only thing that drives me nuts is the password generator, sometimes it just doesn't work on certain sites. That is why I wrote/use g20 😎

      See more
      JavaScript logo

      JavaScript

      351.2K
      267.4K
      8.1K
      Lightweight, interpreted, object-oriented language with first-class functions
      351.2K
      267.4K
      + 1
      8.1K
      PROS OF JAVASCRIPT
      • 1.7K
        Can be used on frontend/backend
      • 1.5K
        It's everywhere
      • 1.2K
        Lots of great frameworks
      • 897
        Fast
      • 745
        Light weight
      • 425
        Flexible
      • 392
        You can't get a device today that doesn't run js
      • 286
        Non-blocking i/o
      • 237
        Ubiquitousness
      • 191
        Expressive
      • 55
        Extended functionality to web pages
      • 49
        Relatively easy language
      • 46
        Executed on the client side
      • 30
        Relatively fast to the end user
      • 25
        Pure Javascript
      • 21
        Functional programming
      • 15
        Async
      • 13
        Full-stack
      • 12
        Setup is easy
      • 12
        Future Language of The Web
      • 12
        Its everywhere
      • 11
        Because I love functions
      • 11
        JavaScript is the New PHP
      • 10
        Like it or not, JS is part of the web standard
      • 9
        Expansive community
      • 9
        Everyone use it
      • 9
        Can be used in backend, frontend and DB
      • 9
        Easy
      • 8
        Most Popular Language in the World
      • 8
        Powerful
      • 8
        Can be used both as frontend and backend as well
      • 8
        For the good parts
      • 8
        No need to use PHP
      • 8
        Easy to hire developers
      • 7
        Agile, packages simple to use
      • 7
        Love-hate relationship
      • 7
        Photoshop has 3 JS runtimes built in
      • 7
        Evolution of C
      • 7
        It's fun
      • 7
        Hard not to use
      • 7
        Versitile
      • 7
        Its fun and fast
      • 7
        Nice
      • 7
        Popularized Class-Less Architecture & Lambdas
      • 7
        Supports lambdas and closures
      • 6
        It let's me use Babel & Typescript
      • 6
        Can be used on frontend/backend/Mobile/create PRO Ui
      • 6
        1.6K Can be used on frontend/backend
      • 6
        Client side JS uses the visitors CPU to save Server Res
      • 6
        Easy to make something
      • 5
        Clojurescript
      • 5
        Promise relationship
      • 5
        Stockholm Syndrome
      • 5
        Function expressions are useful for callbacks
      • 5
        Scope manipulation
      • 5
        Everywhere
      • 5
        Client processing
      • 5
        What to add
      • 4
        Because it is so simple and lightweight
      • 4
        Only Programming language on browser
      • 1
        Test
      • 1
        Hard to learn
      • 1
        Test2
      • 1
        Not the best
      • 1
        Easy to understand
      • 1
        Subskill #4
      • 1
        Easy to learn
      • 0
        Hard 彤
      CONS OF JAVASCRIPT
      • 22
        A constant moving target, too much churn
      • 20
        Horribly inconsistent
      • 15
        Javascript is the New PHP
      • 9
        No ability to monitor memory utilitization
      • 8
        Shows Zero output in case of ANY error
      • 7
        Thinks strange results are better than errors
      • 6
        Can be ugly
      • 3
        No GitHub
      • 2
        Slow

      related JavaScript posts

      Zach Holman

      Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

      But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

      But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

      Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

      See more
      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 10.1M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more