FOR LARAVEL DEVELOPERS

One HTTP call from the app you already have.

Your Mailables are fine. Your queues are fine. What is missing is the answer to the support message that starts “I never got the email” — and the only place that answer could live is a log nobody built. One POST from your app, and the record exists.

Start free — no card requiredSee the plans →
Keep your Mailables, your queues and your mail server.Built in Laravel, by people who got tired of tailing logs to answer one question.
WHERE WE SIT

Your mail goes out the way it does today. We write down what happened.

1Your appyoursSends one request: who it goes to, which template to use, and the values to fill in.
2Spoolwaythis is usWe fill in your template, hand it to your server, and write down every step.
3Your mail serveryoursAmazon SES, Mailgun, Postmark, or your own server. We never send as if the mail were ours.
4Your customeryoursGets the email, the same as they do today. Your address, your reputation.
and every step above is written down
THE RECORDsearchable later — and kept for exactly as long as you decide
Did that email actually go out?Your mail server’s own reply, word for word, with the time it was accepted.
What exactly did it say?The message itself, stored encrypted, for as long as your retention policy says — or never stored at all.
Who else can send as us?Every key is named and belongs to a person. Revoke one without breaking the rest.
WHAT CHANGES FOR YOU

Four things, in plain words.

A few lines, not a refactorSend through the API and keep your own mail server exactly as it is. Nothing about your Mailables, queues or deliverability changes.
One template set across every appIf you run more than one Laravel app, they stop each having their own copy of the password-reset blade. Write it once, version it in git.
Which app sent itTag each application once. "Which of our apps emailed this customer?" becomes a filter instead of grepping five deployments.
Or use the API directlyOne POST with a template name and variables, if you would rather not render mail in your app at all.
THE INTEGRATION

The whole integration

// config/services.php — one HTTP call, from any Mailable
Http::withToken(config('services.spoolway.key'))
    ->post('https://spoolway.com/api/v1/messages', [
        'template'    => 'auth/password-reset',
        'application' => 'auth-prod',
        'to'          => $user->email,
        'variables'   => ['reset_url' => $url],
    ]);
Free tier: 10,000 messages a month, 3 Applications, 7-day message bodies — no card required.
WHAT WE DO NOT DO

We never send mail as if it were ours, and we never show a delivery we cannot prove.

There is no plan where we become your sender. Your server keeps your reputation. Where a mail server cannot report back, the record stops at the handoff and says so — no green tick standing in for a fact nobody has.

what we hold, and what we do not have yet →
ALSO WRITTEN FOR
Amazon SESMailgunPostmarkYour own mail serverAgenciesSaaS foundersSupport teamsCompliance and procurementDevelopers

Your transport. Your record.
Running in five minutes.

connect your mail server → name the product → send a test
Start free — no card requiredFree forever tier · caps pause, never auto-upgrade