litemx addresses create
Custom-domain email. Your inbox.
Create support@yourdomain.com from the CLI, receive it in the inbox you already use, and reply normally. Your recipient sees support@yourdomain.com—not your private address.
one address · one commandverified destinationGmail · Thunderbird · Fastmailas support@ · destination hiddenthread intact · delivery tracked$litemx addresses create support@project.dev --forward-to owner@example.comOne address. Your inbox. Agents when you need them.
Set up the address from the terminal, handle conversations in the email app you already know, and add scoped agent access only when it helps.
litemx addresses create
Create the address in one command.
Connect support@project.dev to a verified destination. LiteMX creates the address and returns the DNS records to add wherever your domain is already managed.
pnpm dlx litemx@latest loginlitemx addresses create support@project.dev --forward-to owner@example.com✓ address created · destination addedlitemx domains dns-plan project.devlitemx domains verify project.devlitemx mailboxes forwarding
Keep using the inbox you already know.
Incoming mail lands in Gmail, Thunderbird, Fastmail, or another existing inbox. Click Reply there; LiteMX sends it from support@project.dev and keeps your private destination hidden.
litemx forwarding-destinations listowner@example.com · verifiedlitemx mailboxes forwarding support@project.dev✓ forwarding enabled · destination verifiedReply in your usual inboxrecipient sees support@project.devlitemx mcp test
Let agents act inside a boundary.
External agents can search, read, draft, and send through MCP or the API. Each token is limited by mailbox and action, so you decide exactly what an agent can do.
litemx mcp test✓ initialized · tools availablelitemx tokens create support-agent --mailbox support@project.devscopes: messages:read · messages:search · drafts:writelist_mailboxes · list_threads · read_messagesend_draft — requires email:sendCustom addresses without another inbox subscription.
Google Workspace and Proton Mail are great when someone needs a complete new mailbox. LiteMX is for projects that need support@, hello@, billing@, and admin@ in an inbox you already use.
One LiteMX plan can cover many experimental domains. No extra mailbox UI, mailbox password, or nameserver move—just forwarding, normal replies, and optional CLI, API, and MCP access.
| Capability | Google Workspace | Proton Mail | LiteMX |
|---|---|---|---|
| Billing model | Per user | Per user / plan | Flat pool — many domains |
| Where humans read mail | Gmail | Proton Mail | Your existing inbox |
| Another mailbox login | Yes | Yes | No |
| 20 custom domains | Depends on setup | Not a personal-plan fit | Included |
| Many domains, one account | No | Limited | Yes |
| Unlimited aliases | Capped | Capped | Yes |
| First-class CLI | No | No | Yes |
| Scoped REST + MCP access | Separate APIs | No | Yes |
| Agent access | No | No | Yes |
| Designed for | Human teams | Private human inboxes | Project addresses + agents |
Competitor notes are September 2026 snapshots from Google Workspace pricing and Proton Mail plans. Exact cost depends on seats, domains, aliases, and tier. LiteMX is not a full webmail or office-suite replacement.
One plan for many project domains.
Pay once for a pool of domains, addresses, retention, and outbound volume—not one inbox at a time.
| Plan | Domains | Addresses | Sends / mo | Retention | Price |
|---|---|---|---|---|---|
| free | 1 | 1 | 500 | 30d | $0 |
| starter ← recommended | 20 | 50 | 3,000 | 60d | $8/mo |
| scale | 50 | 150 | 15,000 | 1y | $18/mo |
Questions, answered plainly.
LiteMX connects your custom-domain addresses to an inbox you already use. The CLI handles setup; scoped MCP or API access is there when you want automation.
What is LiteMX?
LiteMX gives founders custom-domain addresses without another inbox subscription. Create support@, hello@, or billing@ from the CLI, then receive and reply from an inbox you already use.
Do I need another mailbox or password?
No. LiteMX forwards mail to a verified inbox you already have and does not issue mailbox passwords. Your existing provider and email app keep handling your personal inbox.
Why not just use Google Workspace or Proton Mail?
Use them when a person needs a complete new mailbox and office suite. Use LiteMX when a project needs a custom address that can share the inbox you already pay for.
How much does custom-domain email cost with LiteMX?
LiteMX starts free for one domain, one mailbox, and capped low-volume sending. Paid plans are $8/month for Starter and $18/month for Scale, billed annually. Aliases are included on every plan.
Can I use LiteMX for newsletters or cold outbound?
No. LiteMX is for human-scale mailbox email, replies, support conversations, and operational messages. It is not a bulk sender, newsletter platform, marketing automation tool, or cold outbound product.
Who is LiteMX for?
LiteMX is for founders, indie hackers, agencies, and automation builders who keep creating new domains and do not want another paid inbox for every experiment.
Does LiteMX replace Gmail?
No. Gmail, Thunderbird, Fastmail, or your current email app remains the place where you read and reply. LiteMX connects your custom-domain address to that existing inbox.
How do agents use LiteMX?
External agents connect through MCP or the REST API using LiteMX tokens. Tokens can be limited to one mailbox and specific actions, so an agent can read and draft without being allowed to send.
What email infrastructure does LiteMX use?
LiteMX is DNS-provider-agnostic for inbound mail. The initial production provider is AWS SES Email Receiving, with Cloudflare Workers, D1, Durable Objects, R2, Queues, and Cron Triggers as the application runtime and storage layer.
Start with one domain.
Request access, connect support@ to your existing inbox, receive a test message, and reply from the email app you already use. Add an agent later if you want one.