Five projects, five domains, five email setups — and why I built Sixuse
Running five projects meant managing five domains, separate business addresses, and five inboxes. In practice, important mail would sit unseen in a mailbox I had not opened in two days. Projects needed separate identities, but I wanted one inbox.
The standard ways to run this, and why each one breaks
The closest workaround is Cloudflare Email Routing pointed at Gmail. It can be useful, but each domain still needs its own DNS configuration and routing rules, and replying from the project address depends on Gmail features that are changing.
Google says that starting in January 2027, Gmail will remove “Send as” for third-party email accounts. Gmailify and web-based POP fetching for third-party accounts are also being removed. Automatic forwarding into Gmail remains available, but the Gmail-based reply workflow is not a durable long-term foundation.
Sources: Google's third-party account changes and Gmailify and POP changes.
Shared inboxes, elaborate filters, one personal address, or separate inboxes each solve part of the problem. None of them gives every project a clear identity without adding more daily maintenance.
What I actually wanted
Give each project a real domain and purpose-built addresses like billing@ and support@, while having every message land in one place I already check. When I reply, I want to reply from the right address automatically.
That's Sixuse. Create a project, give it the identities it needs, and route messages to your inbox. Sixuse handles sending through its own SMTP infrastructure, so replies from a project address do not depend on Gmail's third-party “Send as” feature.
One founder. Multiple projects. One inbox.
Sixuse is live at sixuse.com in beta. If you are a solo founder running more than one project, Try Sixuse in beta