↗ MailGuyOpen workspace
WEBMAIL BETA · SERVICE SCOPE

Know your mailbox.

Domain email in your browser. Invitation only, with no payment collected during the current beta.

Your domainAddresses you own
Your inboxRead in the browser
Your replyFrom your domain

Read the setup guide ↗

What the beta includes
  • Inbox: received mail for addresses connected to your workspace, with a plain-text reading view.
  • Compose, Reply and Reply all: send plain-text mail with an owned domain identity. Reply recipients and identity are prepared from the stored original; review them before sending.
  • Sent: messages with a confirmed provider acceptance receipt. Acceptance does not prove recipient delivery.
  • Outbox: pending, unknown and failed requests. Check the original request without sending another copy.
  • Downloads: received attachments and the complete original received message as .eml, available after signing in.

The reader uses plain text, including a text representation of HTML mail. It does not render mail HTML or load remote images. Shortened message views are labeled; download the original when you need the complete content.

Outgoing attachments, IMAP access and Gmail mailbox synchronization are not available. Webmail's Sent folder is separate from Gmail Sent. This is a beta, with no production availability or delivery guarantee.

What it takes to connect

You need an invitation and a domain whose DNS you can manage. Add its ownership TXT record, verify it in the workspace, then create an address. The service owner manages receiving, storage and the sending provider.

TXT verification proves ownership only. It does not configure MX, sender authentication or an incoming mail route. The service owner must complete the real connection, and you must confirm receiving and sending with a test inbox before relying on it.

Managed Webmail does not require your own provider account or a Chrome extension. Domain registration remains your responsibility. Existing users choosing the old Gmail flow still manage their own provider account, quotas and costs: Advanced · Legacy Gmail setup.

Capacity and sending limits
  • 2 MiB per received message: the whole original email, including headers and encoded attachments. Up to 20 received attachments.
  • 5,000 messages or 512 MiB per workspace: whichever comes first. Original mail, stored message data and pending or failed records count toward capacity.
  • 100 send attempts per rolling 24 hours: per workspace, subject to additional provider limits.
  • 10 domains and 50 exact addresses: per workspace. Wildcard and catch-all addresses are not supported.

Mail that exceeds message or storage limits is rejected; existing mail is not silently removed to make room. Self-service message deletion and storage cleanup are not available in this beta. Ask through your invitation channel if you reach capacity.

Payment and support

No payment is collected during the current beta. An invitation is not a purchase.

Paid plans have not launched. Stripe is a candidate for future hosted checkout; pricing, commercial terms and the purchase-to-cancellation flow still require verification before a paid release. A payment return page alone would not confirm an active subscription or a working mail connection.

Verified operator and contact details, published privacy and service terms, and refund and support processes remain release requirements. This page describes the beta scope; it is not a completed commercial service agreement. For beta help, use the channel that supplied your invitation. No support response time is guaranteed.

Your data and leaving the beta

The service stores received messages, their original files and attachment data, outgoing content, account configuration and request or receipt records for your workspace. It processes addresses, subjects and content to receive and send mail. This is a server-stored mailbox, not an end-to-end encrypted mailbox.

The current browser tab also saves unresolved message content and its request key. Ordinary unsent drafts are not synchronized. Clearing the local recovery copy does not erase the server's saved outgoing record or cancel delivery.

  1. Use your invitation channel to request account closure or data removal. Self-service account and mailbox deletion are not available yet.
  2. Arrange a replacement mail route before changing your domain's existing mail records. Disabling a workspace does not update those records or recall sent mail.
  3. If you used the legacy extension, revoke its token, remove it and clear its local data. Manage any legacy provider subscription and forwarding separately.
Confirm the first real round trip
  1. Send a unique test message from another inbox you control to your connected address. Confirm it appears in Webmail Inbox.
  2. Reply once from Webmail after reviewing From and the recipient. Test Reply all only with addresses you control.
  3. Check the external inbox for the response, its sender authentication and reply headers. A Sent entry alone does not complete this check.
  4. If sending is uncertain, review the original request in Outbox and ask the service owner to check provider activity before making a new copy.

Round-trip steps ↗ · Review an unconfirmed send ↗