Managed beta
Use the complete triage, drafting, routing, follow-up, provider, client, MCP, and API workflow while Mailtwine operates the application and supporting services.
Open-source email triage · AGPLv3 after beta
Open-source email triage.
Start free beta
Open-source email triage.
Self-hosted after beta.
Mailtwine is hosted while we stabilize the complete email triage workflow with early teams. When beta ends, the application code will be published under AGPLv3 with a documented, supported path to self-hosting.
Public when beta ends.
The complete Mailtwine application repository will be published under AGPLv3 with supported self-hosting. There is no public production repository during beta.
// HOSTED BETA → PUBLIC SOURCE → SUPPORTED SELF-HOSTING
The status today
Hosted now. Public source after beta.
The managed beta is the supported way to use Mailtwine today. One operating path lets us stabilize mailbox synchronization, email actions, AI rules, clients, upgrades, and security boundaries before asking teams to run production email infrastructure themselves.
AGPLv3 source and self-hosting
Inspect and modify the complete application, deploy it on infrastructure your team controls, and follow documented installation, upgrade, backup, and recovery procedures.
Why AGPLv3
Your email workflow should not become a permanent cloud-only trap.
Mail history, routing policy, approvals, drafts, provider state, and automation rules become operating data. Public source gives teams a practical route to inspect that system and keep it close to their own infrastructure.
Inspect the workflow
Review how mailbox access, tenant boundaries, AI decisions, approvals, and outbound actions are implemented before trusting the system with important email.
Own the deployment
Run Mailtwine on infrastructure you control when data location, internal networking, compliance, provider policy, or operational requirements demand it.
Share modifications
AGPLv3 is intended to keep network-served modifications available under the same license. Review the published source and license when the release arrives.
What the release is meant to include
The application, mail engines, clients, APIs, and operations package.
The planned release covers the connected Mailtwine system rather than presenting one client or integration as if it were the whole product.
Email command center
The web application, account and project boundaries, triage queues, AI rules, drafts, approvals, follow-ups, audit state, search, REST API, and MCP server.
Providers and workers
Google Workspace, Microsoft, Fastmail, Helpmonks, and standard IMAP or SMTP paths, plus the background processing and realtime services that keep state synchronized.
Ways to work and deploy
Desktop, mobile, browser, CLI, and TUI clients together with versioned production configuration, installation, upgrades, backups, recovery, and security guidance.
Before the public release
Use the beta to prove the workflow.
A source license does not rescue an email tool that does not reduce the work. Validate the product first, then help shape the self-hosting contract.
Connect one mailbox
Choose a real inbox where triage, ownership, replies, or follow-ups are currently being lost.
Run one full workflow
Let Mailtwine triage, summarize, draft, route, and return the thread for review. Confirm the result before expanding access.
Tell us what self-hosting must prove
Send infrastructure, data-location, provider, security, upgrade, and recovery requirements to hi@mailtwine.com.
FREE DURING BETA
UNLIMITED ACCESS
Available now
Prove Mailtwine on a real inbox
Use every Mailtwine feature with no plan limits during beta. Supported self-hosting follows when beta ends.