Buttercup

An honest look at what Buttercup was, why it mattered, and whether you should still use it.

TL;DR

• What it is: A free, open-source, cross-platform password manager that stored encrypted vaults locally or via cloud sync (Dropbox, Google Drive, WebDAV). Built on Electron + Node.js. [README]
• Critical flag: The project is officially closed. Repositories are transitioning to public archives. No new issues or pull requests are being accepted. [README]
• Who it was for: Privacy-conscious users who wanted a self-contained password vault without paying SaaS subscription fees or trusting a third-party server.
• License: GPL-3.0 [merged profile]
• GitHub: 4,413 stars [merged profile]
• Key strength: Simple, clean UI; AES-256 encryption; flexible storage backends (local, Dropbox, Google Drive, WebDAV) [README][4]
• Key weakness: The project is dead. No maintenance, no security patches, no feature development. Using abandoned security-critical software is a genuine risk, not just a theoretical one.

---

What is Buttercup

Buttercup was a free, open-source password manager built on NodeJS and TypeScript, targeting users who wanted desktop and mobile password management without a recurring subscription or a vendor holding their data. The desktop application runs on Electron, the mobile app on React Native, and the whole thing encrypted your credentials in .bcup vault files using AES-256 with over 200,000 PBKDF2 iterations [4].

The core concept was straightforward: your vault lives in a file you control, encrypted with a primary password you choose. That file can sit on your local filesystem, or you can sync it to Dropbox, Google Drive, or any WebDAV-enabled service — which in practice meant ownCloud or Nextcloud installations [README]. No proprietary sync server, no subscription, no vendor lock-in.

It shipped on macOS, Windows 10/11, and most Linux x64 distributions. Mobile apps existed for iOS 12+ and Android 8.0+. A browser extension for Google Chrome handled autofill [4]. The whole stack was a coherent, multi-platform solution that genuinely competed with commercial options.

Then, in late 2024, the founder posted a closure notice in the repository:

“⚠️ Project Closure ⚠️ The Buttercup project has come to an end, and these repositories are in transition to becoming public archives. No public-facing resources will be removed, wherever possible. Please do not create issues or PRs — they will unfortunately be ignored.” [README]

The explanation was posted separately (perry-mitchell’s gist linked in the README). The project did not merge into another tool, did not find a maintainer, and did not fork into an active successor. It simply stopped.

That closure is the most important fact in this review, and everything else should be read in that context.

---

Why People Chose It

Before the closure, Buttercup had a clear value proposition that attracted a specific kind of user.

The self-hosted angle. Every mainstream password manager — 1Password, LastPass, Dashlane — requires you to trust a central server with your encrypted vault. LastPass had multiple high-profile breach incidents where vault data was exfiltrated. Buttercup inverted this: the vault file lived on your own storage. Even if you synced via Dropbox, the file itself was encrypted before upload, and Dropbox saw only ciphertext [README][4]. This mattered to users who had watched the LastPass incident unfold and decided cloud sync for password managers was a bad idea.

No per-seat, no subscription. Bitwarden’s free tier and 1Password’s family plan both require accounts with the vendor. Buttercup had no account, no server, no billing relationship. You downloaded software and ran it [4].

Multi-platform parity. Desktop on macOS, Windows, Linux. Mobile on iOS and Android. Browser extension for Chrome. For users needing all four, Buttercup covered the bases without forcing platform lock-in [4].

Honest encryption. The medevel.com review specifically calls out AES-256 with 200k+ PBKDF2 iterations — a genuinely solid cryptographic posture for password manager vault files at the time [4]. The README includes a direct acknowledgment that security is only as strong as your primary password, with practical guidance on choosing one [README].

The community formed a real following — 4,413 GitHub stars and a multi-year development history — but the project never reached the institutional adoption level that would have sustained a full-time team past the founder’s decision to wind it down [merged profile].

---

Features

What Buttercup actually shipped before closure, based on the README and the medevel.com coverage:

Core vault functionality:

• AES-256 encryption with 200k+ PBKDF2 iterations [4]
• Vault files in .bcup format — a documented, open format [README]
• Entry organization into groups and collections [4]
• Custom fields per entry (ports, URLs, PINs, notes, anything you want) [4]
• Built-in trash for deleted entries [4]
• Rich search across hundreds of entries [4]
• Auto-lock after inactivity [4]

Storage backends:

• Local filesystem [README]
• Dropbox [README]
• Google Drive [README]
• Any WebDAV-enabled service (ownCloud, Nextcloud, etc.) [README]

Desktop-specific:

• Portable Windows executable — run from USB without installing [README]
• macOS, Linux, Windows 10/11 support [README]
• Homebrew cask for macOS (brew install --cask buttercup) [4]
• AppImage for Linux [4]

Mobile-specific:

• iOS 12+ and Android 8.0+ [4]
• On-device encryption/decryption [4]
• Auto-hide screen when backgrounded (like banking apps) [4]
• Offline vault access in read-only mode [4]
• Safari autofill on iOS [4]
• Native code (Objective-C/Java) for performance-critical crypto operations [4]

Browser extension:

• Google Chrome extension for autofill [4]

What it did not have: a web vault interface, browser extensions for Firefox or Safari as first-class products, TOTP/2FA code generation built-in, or an admin panel for team management. It was always a personal password manager, not an enterprise one.

---

Pricing: SaaS vs Self-Hosted Math

This section is simple: there was no SaaS pricing. Buttercup was always free, fully open-source, GPL-3.0 licensed, with no paid tier, no enterprise plan, and no hosted offering [README][merged profile].

The comparison that mattered was Buttercup (free, self-managed vault) versus services like:

• 1Password: ~$3/mo individual, ~$5/mo family (billed annually)
• Bitwarden: free tier exists, premium is $10/year; self-hosted option available
• LastPass: free tier reduced to one device type in 2021; premium at ~$3/mo
• Dashlane: ~$4.99/mo

Buttercup’s cost was $0 indefinitely. The tradeoff was your own time for setup and maintenance, and responsibility for your own backup and sync strategy. For a single user comfortable with file management, this was a favorable trade. For someone who wanted sync “just to work” across five devices without configuration, it was not.

Note: since the project has closed, even the $0 cost calculation now includes the hidden cost of eventual migration. Security software without ongoing maintenance is a liability, not an asset.

---

Deployment Reality Check

Installation was never the hard part with Buttercup. On macOS, brew install --cask buttercup worked. On Windows, there was a standard installer and a portable .exe for USB deployment. On Linux, AppImage or Snap packages were available [README][4].

The friction came from the vault storage model. If you wanted sync across devices, you had to either:

1. Use Dropbox or Google Drive — accounts with a third party, which somewhat undercuts the privacy argument
2. Run your own WebDAV service — meaning a Nextcloud or ownCloud instance, which is its own setup project
3. Manually copy the vault file — technically free but practically annoying

For the target user (privacy-conscious, self-hosting-inclined), option 2 was the clean solution. But it added a dependency: if your Nextcloud is down, your vault sync is down. For someone who had never self-hosted anything, this was a real barrier.

The Arch Linux AUR community maintained their own package, and a small number of Arch users reported occasional segfaults — a known issue with a documented workaround in the GitHub issues [README]. This suggests the project had real-world users filing real bugs, and the codebase was reasonably mature.

What you cannot deploy now: the project is archived. If you hit a bug on a new OS version, you own the problem. If a security vulnerability is found in the encryption implementation, no patch is coming. Building from source remains possible (GPL-3.0), but realistically most users won’t do this.

---

Pros and Cons

Pros

• Genuinely free, no subscription. GPL-3.0, no commercial tier, no account required. While it was active, this was a clean deal [README].
• Strong encryption on paper. AES-256 with 200k+ PBKDF2 iterations is a solid baseline for password manager vault files [4].
• Flexible sync backends. Local filesystem, Dropbox, Google Drive, WebDAV — unusual range for a free tool [README].
• True cross-platform parity. Desktop (macOS/Windows/Linux), mobile (iOS/Android), browser extension (Chrome) all shipped [4][README].
• No server-side attack surface. With local storage, there’s no central vault database to breach. Your exposure is limited to your own devices [README].
• Portable Windows mode. Useful for users on managed machines who can’t install software [README].
• Clean UX for a personal password manager. The medevel.com review describes it as simple and user-friendly — nothing about a steep learning curve [4].

Cons

• Project is dead. This is not a “mostly unmaintained” situation. The README explicitly says the project has ended and repositories are becoming archives. No patches, no updates [README].
• Security software needs maintenance. Encryption libraries have CVEs. OS APIs change. Electron has had critical vulnerabilities over the years. An abandoned Electron app is a specific attack surface concern.
• No TOTP/2FA generation. A modern password manager should ideally handle TOTP codes. Buttercup didn’t. You’d need a separate app for that [4].
• No browser extensions beyond Chrome. Firefox and Safari users had no official autofill option [4].
• No team features. Zero — no shared vaults, no access management, no admin controls. Personal use only [README].
• WebDAV sync requires extra infrastructure. The privacy-preserving sync option required running your own Nextcloud/ownCloud, which is its own project [README].
• Apple Silicon desktop builds were never released. The README explicitly notes “no builds yet” for Apple Silicon Mac [README]. On M-series Macs, you’d run the x64 build under Rosetta.
• Website returned 503 at review time — resources are already starting to disappear [website scrape].

---

Who Should Use This / Who Shouldn’t

Do not start using Buttercup today. This is the honest answer for anyone evaluating it fresh. Security-critical software that is no longer maintained is a liability. Bitwarden covers the same use case (free, open-source, self-hostable, cross-platform) with an active development team, a disclosed security audit, and a clear long-term roadmap. Starting on a dead project in 2026 makes no sense when live alternatives exist.

If you’re already using Buttercup: migrate. The vault format is documented and uses a .bcup extension — exporting your credentials and importing to Bitwarden or KeePass is a one-time afternoon task that eliminates ongoing risk.

If you’re a researcher or curious about the codebase: the GPL-3.0 source is still there, the architecture (Electron desktop, React Native mobile, shared TypeScript core) is worth studying as a real-world multi-platform app design. Just don’t build on it.

If you’re deciding between self-hosted password managers generally: the relevant comparison is now Bitwarden (self-hosted via Vaultwarden) versus KeePass-family tools. Buttercup has exited this competition.

---

Alternatives Worth Considering

Bitwarden / Vaultwarden — The direct replacement recommendation. Bitwarden is open-source (AGPL for the server, various client licenses), actively maintained, has completed third-party security audits, and offers a self-hosted option via Vaultwarden (an unofficial Rust reimplementation of the server that runs on a $5 VPS). Free individual tier, $10/year premium for TOTP generation and additional features. This is where Buttercup users should migrate.

KeePassXC — The old-guard open-source password manager. Desktop-only with no official sync, but extremely mature, audited, and has zero dependencies on any cloud service. Vault files in .kdbx format are supported by dozens of third-party mobile apps (KeePassium on iOS, KeePassDX on Android). Ugly by modern standards, functionally solid.

KeePass 2 — The original, Windows-only, plugin-heavy variant. Longer history, more community plugins, but the UI hasn’t aged gracefully.

Proton Pass — If you’re in the Proton ecosystem (ProtonMail, ProtonVPN), their password manager is free, end-to-end encrypted, and actively maintained. Not self-hostable, but zero-knowledge architecture.

1Password — The commercial benchmark. Expensive ($3–5/mo), not open-source, but polished across every platform including CLI and SSH key management. Relevant if budget isn’t the constraint.

The clean recommendation for non-technical founders escaping commercial password managers: Bitwarden self-hosted via Vaultwarden, or Bitwarden cloud free tier if self-hosting is too much friction. Both are what Buttercup tried to be, and both are actively maintained.

---

Bottom Line

Buttercup was a reasonable password manager for its time: free, encrypted, cross-platform, and built on flexible sync backends that didn’t require trusting a third-party server. For users who wanted to escape 1Password fees or LastPass breach anxiety, it offered a credible alternative. The 4,413 GitHub stars represent real users who found it useful [merged profile].

But the project is closed. The README says so in plain language, and the website returning 503 confirms that resources are already evaporating [README][website scrape]. For a password manager — software where a missed CVE can expose every credential you own — “actively maintained” is a non-negotiable requirement. Buttercup no longer meets it. Recommending it to anyone starting fresh in 2026 would be irresponsible. If you’re currently using it, export your vault and move to Bitwarden before you encounter a problem that has no patch coming.

---

Sources

1. medevel.com — “Buttercup: a simple user-friendly Password manager for all platforms” — https://medevel.com/buttercup/
2. Buttercup Desktop README — Project closure notice, feature documentation, platform support — https://github.com/buttercup/buttercup-desktop
3. perry-mitchell (GitHub Gist) — Project closure explanation — linked from https://github.com/buttercup/buttercup-desktop/discussions/1395

Primary sources:

• GitHub repository: https://github.com/buttercup/buttercup-desktop (4,413 stars, GPL-3.0, archived)
• Official website: https://buttercup.pw (returning HTTP 503 as of March 2026)