Sink

A mail trap you own

Sink is a self-hosted mail trap for applications that should never send real email from staging or CI. It gives your non-production environments a dedicated place to capture outbound mail on infrastructure you control, instead of routing test messages through a third-party SaaS.

It is capture-only by design. A sink Laravel mail transport posts your app's outbound mail to an HTTP /ingest endpoint instead of delivering it, so nothing leaves your environment and no customer ever receives a message from a test run.

Built for Laravel Cloud ownership

Sink follows the same fork-and-own-it model as the rest of Built for Cloud. You fork the application, connect it to Laravel Cloud, and run your own Sink deployment on compute you control.

Pointing your app's mail at your Sink deployment is the only wiring step. Your staging and CI environments use the sink transport, the messages land in your deployment, and your production mail configuration stays untouched.

What Sink captures

Sink captures the outbound mail your app would have sent — subject, recipients, headers, metadata, and body — and presents it in a human inbox UI you can read. Your team opens the inbox to confirm what a flow actually sent without a real message ever leaving the environment.

Body-blind through MCP

Sink also exposes a Model Context Protocol server so an AI agent can assert on captured mail — that a message was sent, to the right recipients, with the expected subject, headers, and metadata. The MCP server is body-blind: it never exposes private message bodies to the agent, so automated checks stay useful without reading the contents of every email.