Sesame

Sesame is a simulated Amazon SES for staging load runs. Your staging app sends through its normal SES v2 path with the endpoint pointed at Sesame. Sesame draws a seeded outcome for every recipient (delivery, bounce, complaint, delay or reject) and posts SNS notifications back to your webhook. The notifications are signed in the format the AWS SNS message validator accepts once it is bound to Sesame's certificate host. Sesame keeps the ground truth for each message, so after a run you can check that every event changed the right state, not only that the run was fast. It never delivers mail.

Sesame is a proof of concept. Growth CRM is its first intended consumer, but the end-to-end loop has so far been closed only against a local CRM-compatible harness that lives in Sesame's own repository. The Scalpels entry is Experimental: a work in progress, not ready for production use. It is public, and Scalpels will start an install, but that install path has not been tested on Laravel Cloud, and deploying during a test can lose sends from that test. The source is at artisan-build/sesame.

In these docs

• Getting started explains what the proof of concept demonstrated and what an install from the Experimental listing does and does not provide.
• Requirements records what an install provisions, how Sesame keeps data, and what is still open.

The proof-of-concept report in the Sesame repository, docs/poc-report.md, has the full evidence: the commands run, the numbers, and the benchmark conditions.