Skip to content
BBlueSend
Multi-tenant email, done right

Compliant email for all your clients, from one API.

BlueSend lets each of your clients send from their own verified domain through one secure server — with templates, environments, granular permissions, automatic suppression, and a complete audit log. No contact database to manage or leak.

Get started See the API
  • Own-domain sending
  • SPF · DKIM · DMARC
  • Powered by Amazon SES
  • Audit-log only
  • One-click unsubscribe
What BlueSend is

One platform. Two audiences.

BlueSend is one server for sending email on behalf of many clients — each from their own verified domain, with deliverability, compliance and a full audit trail handled for you.

For your business

Manage email for every client from a single dashboard. Each client sends from their own branded domain, deliverability and compliance are handled for you, and you can see exactly what went out — without ever holding a marketing list of their customers.

  • One dashboard for all client sending
  • Their brand on every message
  • Compliance and suppression on autopilot

For your developers

A clean REST API with per-environment keys. Send a raw message or a saved template with variables in one POST, attach files as base64, and get back a status you can log. No SDK lock-in, no environment ids to juggle — the key picks the environment.

  • POST /v1/emails — raw or templated
  • Per-environment keys (test / live)
  • 202 Accepted with a durable send id
Capabilities

Everything a sending platform should do

Deliverability

Every client sends from their own domain

BlueSend verifies each tenant's sending domain and wires up SPF, DKIM and DMARC for them — powered by Amazon SES with per-tenant reputation isolation, so one client's sending never drags down another's.

  • Guided domain verification with copy-paste DNS records
  • SPF · DKIM · DMARC configured per sending identity
  • Per-tenant reputation isolation on Amazon SES
Privacy by design

No stored contact lists — recipients live only in the audit log

BlueSend is not a CRM. It never builds a marketing database of your recipients: addresses are used to send and then recorded in an immutable, per-send audit log. There's no contact table to leak, export, or subpoena.

  • No persistent contact/audience store
  • Every send logged with recipients, status and attachments
  • Suppression and access lists enforced at send time
Environments

Dev, staging and production — with one-way promotion

Give every project as many environments as it needs. Build and test templates and rules in development, then promote them downstream along a defined order — promotion only ever flows one way, so production can't be clobbered by accident.

  • Per-environment API keys (bsnd_test_… / bsnd_live_…)
  • Promote templates and config along a fixed order
  • One-way flow — no accidental writes back to prod
Content

Reusable templates with variables and attachments

Design HTML templates once, version them per environment, and send them by key with substitution variables. Attach files inline as base64 — receipts, invoices, PDFs — with a clear combined size limit.

  • Send by templateKey with typed variables
  • Base64 attachments up to 10 MB combined
  • Templates versioned and promotable per environment
Compliance

Unsubscribe and suppression, handled for you

Marketing sends carry one-click List-Unsubscribe headers, and bounces and complaints feed an automatic suppression list so you stop mailing addresses that shouldn't be mailed. CAN-SPAM, GDPR and CASL expectations are met by default.

  • RFC 8058 one-click List-Unsubscribe on marketing mail
  • Automatic suppression on bounces and complaints
  • Whitelists / blacklists honored at send time
How it works

From zero to your first send in four steps

  1. 1

    Create a project & environments

    Spin up a project for each client and give it development, staging and production environments.

  2. 2

    Verify a sending domain

    Add the client's domain and drop in the generated SPF, DKIM and DMARC records. BlueSend confirms verification.

  3. 3

    Grab an API key

    Mint a per-environment key — bsnd_test_… for dev, bsnd_live_… for prod. The environment is derived from the key.

  4. 4

    POST /v1/emails

    Send a raw message or a saved template with variables. Every send is authenticated, checked and logged.

For developers

Send your first email with one request

Authenticate with a per-environment bearer token, POST to /v1/emails, and you're sending. Provide a raw subject and HTML body, or reference a saved template by key and pass variables — BlueSend renders it server-side.

  • Bearer keys prefixed bsnd_test_… or bsnd_live_… — the key selects the environment
  • Up to 50 recipients per message; 10 MB of attachments combined
  • 202 Accepted returns { id, status }; suppressed recipients return 422
Full API reference in your dashboard
send.sh
curl -X POST https://api.bluesend.app/v1/emails \
  -H "Authorization: Bearer bsnd_live_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["customer@acme.com"],
    "subject": "Welcome to Acme",
    "htmlBody": "<h1>Hi there</h1><p>Thanks for signing up.</p>"
  }'

# → 202 Accepted
# { "id": "3f9a1c60-4b2e-4d8a-9e11-7c5b2a0f6d84", "status": "Sent" }

…or send a saved template

body.json
{
  "to": ["customer@acme.com"],
  "templateKey": "welcome",
  "variables": { "name": "Dana", "plan": "Pro" }
}
Trust & compliance

Built to be trusted with your clients' sending

The compliance work is done for you — authentication, unsubscribe, suppression and an audit trail are on by default, not a checklist you maintain.

Authenticated at the domain level

Every tenant sends from a domain they verify, with the full authentication triad configured for them via Amazon SES.

  • SPF
  • DKIM
  • DMARC
  • Per-tenant reputation

Respectful of every recipient

Marketing mail carries a one-click unsubscribe, and bounces and complaints feed suppression automatically — so bad addresses stop getting mailed.

  • RFC 8058 one-click
  • Bounce suppression
  • Complaint suppression
  • Access lists

Accountable by default

Every send is written to an immutable, per-send audit log — recipients, status and attachments — with no marketing contact database to leak, export or subpoena.

  • Immutable audit log
  • Per-send records
  • No contact store

Aligned with the rules

The defaults are built to meet the expectations of the major sending regulations, with a Data Processing Addendum available for review.

  • CAN-SPAM
  • GDPR
  • CASL
  • DPA available

Regulatory references describe the controls BlueSend provides; they are not legal advice. See the Privacy Policy and DPA for details.

Pricing

Simple tiers that grow with you

Starter, Pro and Enterprise. Final pricing is being finalized — start free and talk to us about volume.

Starter

For a first client or a side project

TBD

Pro

Popular

For agencies running many domains

TBD

Enterprise

For volume, SLAs and SSO

TBD

Compare plans

Ready to send from your clients' domains?

Open the dashboard, verify a domain, and post your first email in minutes.

Get started Talk to us