CloudySend

Email for products

Transactional email and broadcasts in one place.

CloudySend sends the mail your product already needs: a Resend-compatible API, ordinary SMTP mailboxes, your own domain, templates, webhooks, and a delivery log.

Overview
Sent1,284
Delivered1,241
Bounced11
Quota12%
hello@acme.testdelivered
alerts@lab.testqueued

Who it's for

Teams that send mail from a product, not from a personal inbox.

Products and SaaS

Sign-up confirmations, password resets, receipts, and the notifications your app already sends.

Self-hosted tools

GitLab, WordPress, monitoring, forums, and anything that only knows host, port, and a password.

Product marketing

Segments, templates, and broadcasts to the audience you already have.

Developers

The SDK you already use, signed webhooks, and an HTTP log for every API call.

What you can do

Sending, domains, and the record of what happened — without a second tool.

An API your code already speaks

Keep the official Resend SDK. Point it at CloudySend and send with the same call. Domains, keys, templates, contacts, and broadcasts stay next to it.

SMTP for everything else

Host, port, username, password. Mail from other apps joins the same pipeline as the API.

A domain you control

SPF, DKIM, and return-path, with the DNS records listed on one page. Open and click tracking turn on per domain.

A log for every message

Greylist retries, bounces, complaints, suppressions, opens, and clicks — visible per email.

Volume you can plan for

Workspace limits keep a month of sending inside the number you expect.

A workspace for the team

Shared keys, mailboxes, and history. Owner, developer, and member roles.

Why teams use it

How it works

  1. 1
    Open a workspace

    Create an account. A workspace is ready for your domain, keys, and mail.

  2. 2
    Connect a domain

    Publish the DNS records and wait for verification.

  3. 3
    Send the first message

    From your code, from an SMTP mailbox, or with the button in the dashboard.

Send from the app you already wrote

Keep the SDK. Change the base URL and the API key from the dashboard. Idempotency, batch send, templates, and webhooks stay on the same path.

POST /emails
curl -X POST $API/emails \
  -H "Authorization: Bearer cs_…" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Acme <hello@acme.com>",
    "to": ["ada@example.com"],
    "subject": "Welcome",
    "html": "<p>It works.</p>"
  }'
SMTP
Hostmail.example.com
Port587
EncryptionSTARTTLS
Usernamealerts@acme.com
Passwordcsmtp_••••••••

A mailbox for apps without an API

Create a mailbox on a verified domain and paste host, port, username, and password into the other tool. Messages show up next to API traffic.

Start sending from your domain

Connect a domain, create a key or an SMTP mailbox, and send the first message from the dashboard or from your code.

CloudySend — email infrastructure for products and teams.