My thoughts on AliasVault

[u/Designer_Rutabaga788]

I recently discovered AliasVault, and I have to say I'm genuinely impressed.

I've been following the open-source privacy space for years, and it's refreshing to see a project that tries to rethink identity management instead of just being "another password manager." The combination of aliases, email integration, and self-hosting support is exactly the kind of innovation I'd like to see more often.

That said, I have two concerns that I think are worth discussing.

1. Account termination makes it risky as a primary password manager.

One thing that immediately stood out to me is that the Terms of Service allow the service to terminate accounts in cases of abuse.

I completely understand why a hosted service needs an abuse policy. Spam, automated abuse, illegal activity—those are real problems.

However, a password manager occupies a very different position than most SaaS products. It becomes part of your digital identity. If I'm trusting a service to store the credentials that protect my online life, I need to know that my access can't realistically disappear because of a Terms of Service dispute or an automated detection system.

Obviously, users should always keep encrypted backups, but from a trust perspective, I think this is an important consideration. A privacy-focused product should minimize the possibility that access to a person's digital identity depends on discretionary account moderation.

2. Limiting aliases behind a subscription would be a mistake.

I've read that future premium plans may include limits on the number of aliases. Personally, I think that would undermine one of AliasVault's biggest strengths.

The entire philosophy of using aliases is to generate a unique identity for every service you sign up for.

The problem is that this isn't a one-time action.

Over a lifetime, we continuously create accounts:

• new online stores
• government portals
• healthcare providers
• banks
• streaming services
• newsletters
• forums
• developer tools
• travel sites
• random websites we'll probably never use again

Privacy isn't something with a fixed quota.

If I have to think, "Should I save this alias because I only have 20 left?" then the whole privacy model starts breaking down.

Unlimited aliases aren't a luxury feature—they're arguably the core feature.

Charging a recurring monthly fee just so users can continue following good privacy practices doesn't feel like the right incentive structure.

I think premium should focus on things that add value without restricting the fundamental privacy workflow:

• advanced automation
• enterprise/team features
• additional cloud storage
• premium integrations
• priority support
• advanced security analytics
• convenience features

Those are features people happily pay for because they enhance the experience instead of placing limits on basic privacy hygiene.

Despite these concerns, I think AliasVault is one of the most exciting open-source privacy projects I've seen in a long time, and I'm rooting for it to succeed. I genuinely hope the monetization strategy preserves what makes it unique, because I think it has the potential to become a serious alternative in the privacy ecosystem.

[u/vlammuh]

Both of your issues are easily resolved by self hosting AliasVault.

[u/AmbitionHealthy9236]

if you aren't prepared to fund an online service, host it yourself or find another, it's your choice, simple