AliasVault v1.0 roadmap

[lanedirt]

Important

Note: The following list is not yet 100% definitive and might be refined further; however, all items listed will be addressed or explored while working towards the upcoming 1.0 release. Last update: 2026-03-01.

This issue provides an overview of key milestones planned for the AliasVault 1.0 release.

The short-term priority is to position AliasVault as a fully viable alternative to traditional password managers like 1Password, Bitwarden, and KeePass. This involves ensuring robust usability for everyday tasks, including comprehensive autofill capabilities across all platforms.

🚧 Prereleases (0.X)

The following issues will be actively worked on, with incremental releases published every 2-3 weeks. This approach allows us to test new features extensively in real-world usage and collect valuable user feedback.

Any breaking changes to the data model will always include automatic data migrations. Throughout these prereleases, AliasVault is fully usable and your credentials remain secure. Fixing bugs will always be prioritized and you can trust that data integrity will always be maintained.

Data Model and Usability Improvements

• Add custom imports for existing (popular) password managers
• Add passkey storage support
• Expand core data model and separate credentials into two types:
  • Random aliases (already implemented)
  • Fixed reusable identities (your own identity to be used for official purposes such as government, online banking etc., your real email)
    • Main identity
    • Shipping / billing address
    • Creditcard details
• Allow credentials to be grouped for better overview and management (folder structure)
  • Improve importers so credentials can be optionally imported to a specific folder
• Allow to add multiple service URLs (optionally) for improved autofill
  • [Feature Request] Add multiple Service URLs for one Alias #753
• Implement password history
• Investigate possibility for user-defined custom fields
• Research team and organization features:
  • Being able to share credentials with other users while maintaining proper E2E encryption handling
  • LDAP/LDAPS/OAuth support (with/without Windows AD domain) for group/business authentication
    • [Feature Request] SSO / OIDC / OAuth login for users on domain #751
    • [Feature Request] LDAP / LDAPS Support #642

Platform Support

• Browser Extensions
  • Chrome (and other Chromium browsers)
  • Firefox
  • Edge
  • Safari
• Mobile Apps
  • iOS app
    • Investigate possibility for Apple Watch companion app for favorite credentials and 2FA TOTP
  • Android app
• Enable AliasVault to be a passkey provider
• Add multi-language support to all AliasVault clients and enable crowd-sourced translation contributions
  • [Feature Request] Add multilingual support #820
• Authentication & Security Enhancements
  • Implement mobile app (phone) based unlock in web app and browser extension instead of master password
  • Add explicit PIN unlock mode to mobile app in addition to biometric (default).
  • Add explicit PIN unlock to browser extension in addition to password (default).
  • Add hardware key as 2FA method (as optional method next to existing TOTP)
  • Support FIDO2, WebAuthn or hardware key as primary vault password
  • Develop duress mode for web app and native apps (for travel or forced situations).
  • Add recovery code / emergency contact / fallback access to vault while still guaranteeing full E2EE (as optional feature)
• Evaluate potential for native desktop / CLI clients (macOS, Linux, Windows)
  • [Feature Request] Desktop apps #1283
  • [Feature Request] Windows Native passkey support #1351
  • [Feature Request] CLI tool #1800
  • MacOS native apps can leverage "Native autofill" capabilities: https://www.theverge.com/2022/5/3/23055212/1password-8-mac-password-manager-security
  • Native apps can act as a local SSH agent for autofilling credentials in Linux/MacOS terminal

Documentation & Setup Improvements

• Improve documentation for VM installations (Docker, clean setups)
• Standardize AliasVault deployments with single-docker image package for NAS/self-hosting convenience

Browser Extensions & Mobile Apps

• Support adding manual user/password entry via the create screen
• Allow credential mutations directly via browser extension
• Add advanced credential create screen with customization options for password strength
• Develop full client capabilities for mobile app
  • Support vault upgrades
  • Change identity generator settings
  • Change password generator settings
  • Built-in account and vault creation

Premium Cloud Features

These features will be offered as an optional subscription to cover the costs of running the cloud version and help the future development of AliasVault.

• Enable users to connect their custom domain(s) to the cloud hosted AliasVault version
  • Investigate being able to import custom email aliases from existing service combinations such as Proton Pass + SimpleLogin. Note: Bitwarden supports multiple external parties. 1Password integrates with Fastmail for masked email.
• Allow more email storage for premium users
• Allow larger attachment storage for premium users
  • Separate attachments from actual vault blob to reduce overhead in loading the actual vault
• Add reply-to-message feature integrated within AliasVault aliases
• Investigate integration of disposable phone number service for SMS verifications
• Add Have I Been Pwned integration (and/or similar platforms) for automatic checks if credentials have been part of a data breach on the internet, in order to advise the user to change those credentials.

Additional Research Required

• Research SMTP relay host support for reply capabilities
• Investigate integration with external cloud email services (Office365, IMAP) for catch-all and reply capabilities.
• Explore UI customization (logo, app name) for self-hosted and premium cloud versions

Feedback and suggestions are welcomed to further refine this roadmap as we progress towards the AliasVault 1.0 release.

🎬 Release Candidates (v1.0.0-rcX)

Once the above milestones are completed, we will release candidate versions focused on bug fixes, stability, and performance improvements. At this stage, the core feature set and data model will be finalized, with no further breaking changes.

🚨 Security audit

With the API stabilized, we aim to have AliasVault undergo a thorough security audit this stage. We have already initiated conversations with renowned cyber security companies who have taken interest in taking this on.

👑 1.0: Stable Release

Once all known bugs have been fixed in RC releases and optimal performance is achieved, AliasVault 1.0 will be officially released.

After this stable release, work will continue on additional 1.x minor releases which can contain additional features and improvements. However the AliasVault API and datamodel from this point onwards will stay backwards compatible within the 1.x branch.

[SchBenedikt]

I would appreciate an IMAP feature so that you can access the aliases with another email program and maybe even send emails using the aliases.

Great application! 👍

[nexthop0]

I would apprecaite the email stuff being removed entirely and made into a companion app. Password manager should never have an email server bundled.

[lanedirt]

@nexthop0, thanks for your feedback. Using email aliases in AliasVault is entirely optional, however we have no plans to separate this functionality into a companion app, as email aliases are a core part of our vision for AliasVault. You can read more about AliasVault's vision and mission here. We may however add additional UI customization options in the future, so users who do not use aliases can hide related from the menu (for example).

If you have other suggestions or ideas for improvements, please feel free to open a separate issue for it so users can upvote it to show their support.

[nexthop0]

@nexthop0, thanks for your feedback. Using email aliases in AliasVault is entirely optional, however we have no plans to separate this functionality into a companion app, as email aliases are a core part of our vision for AliasVault. You can read more about AliasVault's vision and mission here. We may however add additional UI customization options in the future, so users who do not use aliases can hide related from the menu (for example).

If you have other suggestions or ideas for improvements, please feel free to open a separate issue for it so users can upvote it to show their support.

Nothing about that vision and mission precludes the SMTP from being a companion app. I don't want such a technology bundled with a password manager. I want to strip SMTP from the container completely and have it be a module for those who want to risk using that trash so tightly integrated into their password manager. I'm just one user, but as AliasVault gets more popular you will see more requests to remove that functionality completely because SMTP is not synonymous with privacy. Last I'll say on the matter. Best of luck to you.

[vincegre]

I don't want such a technology bundled with a password manager. I want to strip SMTP from the container completely and have it be a module for those who want to risk using that trash so tightly integrated into their password manager.

@nexthop0 Just don't open the ports for smtp on your host where you are running AliasVault and you're all good ! I use Aliasvault since few months now and I'm also not interested by the email alias as it is so I just blocked the corresponding ports in my fw and that's it ;)

[proop]

Perhaps decoupling the alias, password and email features into separate components/containers would be great to give users options.
E.g. email could be forwarded instead of using the mailserver.