[Feature Request] Alias Organization (Tags/Folders): Moving from Discussion #398 to Implementation

Problem description

SimpleLogin is excellent for privacy, but as a long-term user’s library grows (often exceeding 200+ aliases), the dashboard becomes a "flat list" that is increasingly difficult to navigate. Currently, there is no way to group aliases by use case (e.g., "Finance," "Social," "Shopping," "Work").

This request has lived in Discussion #398 for nearly five years. It is one of the most upvoted and commented-on topics in the repository, signaling a high level of user demand and potential churn for power users who feel overwhelmed by the lack of structure.

The technical context: The SPA migration

In previous updates (most notably in 2022 and late 2023), the maintainers mentioned that implementing a tagging/folder system requires a transition from a "classic" web app to a Single Page Application (SPA).

Since we are now in 2026, we wanted to check in on the status of this architectural shift:

Q: Has the SPA rewrite reached a state where UI-heavy features like tagging can now be integrated?

Q: If the migration is still ongoing, are there "middle-ground" solutions (like simple database-backed labels) that could be exposed via the API in the interim?

Proposed solutions

Based on the consensus in #398, the community is looking for:

• Tagging System: A way to assign one or more labels to an alias.
• Filtered Views: A sidebar or dropdown to filter the alias list by these tags.
• Visual Mocks: Excellent UI suggestions were provided by @gitmaker032 in the original discussion, which could serve as a starting point to minimize design overhead.

Why this matters now

Many of us have moved our entire digital lives to SimpleLogin. Without a way to organize, the cognitive load of managing "alias sprawl" is reaching a breaking point. Formalizing this as an Issue ensures it stays on the development radar and allows the community to track progress toward a specific milestone.

Call to action

We recognize the massive effort involved in a backend/frontend rewrite.

Could the team provide:

1. A status update on the SPA migration?
2. A definitive "Yes/No/Later" on whether tagging is part of the 2026 Roadmap?

Reference Link: #398