A focused mailbox experience with explicit account, protocol, usage, and billing state. The simple surface is supported by details you can inspect.
Every important state has a visible place in the interface.
Address, quota, aliases, protocol capability, and provisioning state stay together so configuration never feels like guesswork.
Password, passkey, authenticator, recovery, and active sessions are distinct controls.
Mailbox usage is shown only when synchronized measurements are available.
Plan definitions come from the database. Stripe is the payment source of truth, while mailbox entitlement and provisioning stay independently visible.
Each connection method has a specific role. Availability is represented as applied, pending, failed, or unsupported instead of being implied.
Synchronizes folders and messages in compatible desktop and mobile clients.
Incoming mailbox accessSubmits outgoing messages through authenticated transport.
Outgoing message submissionOptional retrieval for clients and workflows that still require it.
Capability dependentA modern API option when the configured mail service supports it.
Capability dependentThe interface follows the real work instead of hiding it behind a spinner.
Validated identity and verified recovery details establish the account boundary.
identityAvailability, limits, and current database pricing are checked on the server.
validationCheckout depends on a verified Stripe test Price mapping during development.
billingThe result remains pending until the mail service reports an applied state.
mailboxClear boundaries are more useful than a single encryption badge.