03 / Communications infrastructure

Email capability for products that need to communicate.

MailCore gives applications a tenant-aware boundary for email delivery and inbound message workflows, alongside a hosted workspace for people. It is designed to keep provider plumbing behind a consistent service interface instead of scattering it through every product that sends or receives mail.

Private betaTenant-aware serviceProvider-backed workflows

The idea

Separate the mail engine from the product using it.

Email can be a core part of a product without becoming a tangle of provider-specific code, credentials, message state, and webhook handling. MailCore centralizes those workflows behind tenant-scoped APIs and normalized message contracts, while the hosting application keeps its own product-specific experience and policies.

The service and its mailbox experience are in private beta. Resend is the current implemented delivery and inbound provider adapter; provider-neutral contracts are an integration boundary, not a claim that every mail provider is already supported.

Inside the platform

One service. Two connected ways to work.

MailCore connects application integrations with an evolving hosted workspace, without hiding its current limits.

01 / Integration

A consistent API boundary

Applications can submit outbound messages and work with inbound messages through tenant-authenticated APIs. The embeddable Python library keeps message and provider contracts separate from database and web-framework choices.

02 / Tenant scope

Keep customer data in its lane

Tenants own their mailboxes, messages, attachments, and delivery context. Service-to-service API keys and verified user access resolve to explicit tenant permissions rather than relying on a process-wide default.

03 / Delivery lifecycle

Follow messages beyond submission

Durable workers handle provider-backed delivery. Signed provider events update message state, while signed tenant callbacks can carry delivery changes back to the integrating application. Inbound attachments are bounded by configured size, count, type, and host policies.

04 / Staff workspace

Bring everyday work into view

The hosted Staff Mail experience brings inbox workflows together with calendar and task views for signed-in tenant users. MailCore also includes organization membership and mailbox controls; available onboarding paths remain limited in the private beta.

Screen preview

A shared workspace for mail and follow-through.

The preview reflects the current Staff Mail navigation and inbox layout. Message text and account details are synthetic.

MAILCORE
ILLUSTRATIVE ACCOUNT · NOT LIVE

Inbox

Project updateNotes for the team workspace
Delivery summaryYour weekly message activity
Calendar follow-upItems to review this week

Project update

Hello team,

This sample message illustrates the reading pane. In the product, mailbox actions and tenant access depend on the signed-in account.

Thanks,
A sample sender

Illustrative interface preview with synthetic messages. This is not a live mailbox or a promise of general availability.

Availability

Private beta. Limited access and integrations.

MailCore is actively evolving. Provider support is currently centered on the implemented Resend adapter, and domain onboarding and hosted mailbox workflows are not yet a general-purpose production offering. Existing mail systems should not be cut over without an approved migration plan.