2016–2017 Bitwarden debuted in August 2016 with an initial release of mobile applications for
iOS and
Android, browser extensions for
Chrome and
Opera, and a Web-based "vault" (encrypted database). The browser extension for
Firefox was later launched in February 2017. The same month, the
Brave web browser began including the Bitwarden extension as an optional replacement password manager. In September 2017, Bitwarden launched a
bug bounty program at
HackerOne. In February, Bitwarden debuted as a stand-alone desktop application for
macOS,
Linux, and
Windows. It was built as a
web app variant of the browser extension, built with the
Electron framework. The Windows app was released alongside the Bitwarden extension for
Microsoft Edge in the
Microsoft Store a month later. In May, Bitwarden released a
command-line application enabling users to write scripted applications using data from their Bitwarden vaults. In June 2018, following a review, Bitwarden was made available as an optional password manager in the
Cliqz browser (discontinued in 2020).
2022 In September 2022, the company announced $100M
series B financing; the lead investor was PSG, with the existing investor
Battery Ventures participating. The investment would be used to accelerate
product development and company growth to support its users and customers worldwide. Passwordless.dev provided an open-source solution allowing developers to easily implement
passwordless authentication based on the standards
WebAuthn and
FIDO2. Bitwarden also launched a
beta software service allowing third-party developers the use of biometric sign-in technologies – including Apple's
Touch ID and
Face ID, and Microsoft's
Windows Hello – in their apps. In October of that year, Bitwarden introduced changes to the dependencies of its desktop application to include a restricted-use
SDK that may prevent some members of the public from
compiling the application from
source code, provoking concerns that Bitwarden is moving away from open-source principles. Bitwarden
CTO Kyle Spearrin stated in response that it is an issue they plan to resolve, and is "merely a bug". == Security ==