head to head · open source

Aegis Authenticator vs PearPass

Aegis Authenticator has 13,448 GitHub stars, 614 forks, 120 open issues and last shipped 2 months ago. PearPass has 542 stars, 72 forks, 32 open issues and last shipped 3 months ago. Aegis Authenticator leads on adoption by 2,381% (13,448 vs 542 stars). Aegis Authenticator is written in Java under GPL-3.0; PearPass is written in TypeScript under a custom or non-standard licence. Aegis Authenticator has attracted 5% as many forks as stars, PearPass 13%. Aegis Authenticator was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Aegis Authenticator ★ 13K PearPass ★ 542 category Productivity & Utilities

← all 20902 open source comparisons

Side by side

Aegis Authenticator PearPass
GitHub stars ★ 13K ★ 542
License GPL-3.0 Custom / other
Written in Java TypeScript
Last push 2026-09-06 2026-08-14
Forks ⑂ 614 ⑂ 72
Self-hosting Yes Yes
Data ownership Your server Your server

pick Aegis Authenticator if

  • You weight community size — 13K stars and counting
  • You want the GPL-3.0 license terms
  • Your stack matches Java
  • You value the larger contributor base for long-term maintenance

full Aegis Authenticator profile →

pick PearPass if

  • You want the PearPass feature set and don't need the biggest community
  • You prefer the Custom / other license terms
  • Your stack matches TypeScript
  • You evaluated both and PearPass fits your workflow better

full PearPass profile →

About Aegis Authenticator

Aegis Authenticator Aegis Authenticator is a free, secure and open source 2FA app for Android. It aims to provide a secure authenticator for your online services, while also including some features missing in existing authenticator apps, like proper encryption and backups. Aegis supports HOTP and TOTP, making it compatible with thousands of services. For a list of frequently asked questions, please check out the FAQ. The security design of the app and the vault format is described in detail in this document. Features Free and open source Secure The vault is encrypted (AES 256 GCM), and can be unlocked with…

read the full Aegis Authenticator overview →

About PearPass

[!WARNING] 🍐 PearPass is currently paused from active development, so please use at your own caution until further notice. PearPass Desktop The desktop app for PearPass, an open source, end to end encrypted password and identity manager built on Pear Runtime. Table of Contents Introduction Features Installation Usage Examples Logging Testing Staging to Dev Workspace Dependencies Dependencies Related Projects Contributing License Introduction PearPass is an open source, privacy first password and identity manager that gives you full control over your sensitive information. It makes storing and managing your…

read the full PearPass overview →

More in Productivity & Utilities

Related comparisons

More Password & Secret Management projects

Compare either of these against the rest of the Password & Secret Management field.

Frequently asked questions

Is Aegis Authenticator or PearPass more popular?

Aegis Authenticator has 13,448 GitHub stars and PearPass has 542. Aegis Authenticator has the larger community by that measure.

Are Aegis Authenticator and PearPass free?

Both are open source. Aegis Authenticator is licensed under GPL-3.0, and PearPass has no licence declared in this registry. Both are free to self-host.

What is the difference between Aegis Authenticator and PearPass?

Aegis Authenticator is written in Java and PearPass in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, Aegis Authenticator or PearPass?

Choose Aegis Authenticator if you want the larger community (13,448 stars) or its GPL-3.0 licence terms. Choose PearPass if its feature set, stack or Custom / other licence fits better. Both are self-hostable.