# AliasVault: Open-Source E2EE Password & (Email) Alias Manager

**URL:** https://discuss.privacyguides.net/t/aliasvault-open-source-e2ee-password-email-alias-manager/24436
**Category:** Project Showcase
**Created:** 2025-01-28T09:53:48Z
**Posts:** 242
**Showing post:** 73 of 242

## Post 73 by @anonymous261 — 2025-06-06T00:30:43Z

Quick question: would there be anything that would prevent AliasVault from theoretically using the AGPLv3 in a quasi-proprietary way, as stated below?

> [@Introducing SoftwareCompare: Objective data to find software that fits your needs!](https://discuss.privacyguides.net/t/introducing-softwarecompare-objective-data-to-find-software-that-fits-your-needs/21520/22):
>
> (I’m not a lawyer and this is not legal advice) could be interpreted by some as committed to protect a free philosophy in their product. That would be a misinterpretation. Copyleft and permissive licenses are both foss and both permit users the same freedoms required under FOSS definitions. slight_smile Also, the AGPLv3 in particular, while still FOSS, can be used in a quasi-proprietary way in practice. [https://keygen.sh/blog/weaponized-open-source/](https://keygen.sh/blog/weaponized-open-source/) But I feel that a copyleft license co…

---

_[View the full topic](https://discuss.privacyguides.net/t/aliasvault-open-source-e2ee-password-email-alias-manager/24436)._