Proton currently limits the number of email aliases, even when users connect and manage their own domains. This restriction feels unnecessary for custom domains because the user already owns and controls the domain.

Please allow unlimited - or substantially more - aliases for custom domains connected to Proton. Ideally, aliases should not count toward the standard Proton address limit.

Custom-domain integration should also extend across Proton Mail, Proton Pass, and SimpleLogin.

Users should be able to:
Create unlimited Hide-my-email aliases using their own domain or subdomain.
Share a connected domain across Proton Mail, Proton Pass, and SimpleLogin without configuring it separately in each service.
Choose whether a domain is available to one user or shared with an organization or family.
Manage domains, aliases, routing, and permissions from one central location.
Use separate subdomains for regular mail addresses and Hide-my-email aliases.

Currently, domains added to Proton Mail are not integrated with Proton Pass or SimpleLogin.
Building a unified custom-domain system would make Proton’s email and alias services feel like one cohesive ecosystem while giving users greater flexibility and control.