Start free

Amazon SES · your region

Deliverability engineering, not a rented IP

sendlz runs your sending on Amazon SES in your chosen AWS region, with authentication, IP warm-up, suppression and inbox-placement monitoring handled for you. The campaign builder and the transactional API share one template library and one audience.

Connect your domain →Email pricing
✓ DKIM · SPF · DMARC98.9% inbox placement

Why email still needs engineering

Sending is easy. Arriving is the job.

A rented IP has someone else’s history

Shared sending infrastructure means someone else’s complaint rate is now your deliverability problem too.

DMARC without enforcement is a suggestion

A policy of p=none tells spoofers nothing changes. Enforcement is what actually protects the domain.

An inbox you never check

“Sent” isn’t “delivered”, and “delivered” isn’t “in the inbox”. Placement has to be monitored, not assumed.

How it works

From domain to inbox, handled end to end

  1. 1

    Connect your domain

    An SES identity in your chosen AWS region, with the DNS records generated for you.

  2. 2

    Authenticate

    DKIM, SPF, DMARC and BIMI verified automatically, then watched for drift.

  3. 3

    Warm up

    A 30-day sending curve with automatic throttling if complaints spike.

  4. 4

    Send and monitor

    API or campaign builder, with inbox placement tracked by provider.

Deliverability

Every signal a mailbox provider checks, monitored

Authentication and reputation are not a one-time setup. sendlz generates and watches your DKIM, SPF, DMARC and BIMI records for drift, runs new sending infrastructure through a managed warm-up curve, and tracks inbox placement by provider rather than trusting a “sent” status.

  • DKIM at 2048-bit, kept rotated
  • SPF alignment and a DMARC policy enforced at p=reject
  • BIMI with a Verified Mark Certificate, live on supporting inboxes
See the deliverability guide →

One workflow, three channels

No open in 24 hours? Escalate to WhatsApp — automatically

Email, WhatsApp and SMS share one audience and one consent ledger, so a journey can list them in order: send the email first, and escalate to a WhatsApp utility message (or SMS) only if it goes unopened past your window. The customer gets one message that reaches them, not three that pile up.

  • One journey, channels listed in order — email first, WhatsApp or SMS next
  • Escalates only on no-open or no-click, never a duplicate send
  • One consent ledger and one suppression list across every channel
Explore omnichannel messaging →

win_back_v2

  1. 1Email sent — dynamic template
  2. 2No open in 24h: WhatsApp utility template
  3. 3No delivery: SMS sent
  4. 4Open or reply stops the rest
Visual drag-and-drop canvas — Coming soon

Use cases

Where email earns its place in the stack

Transactional email

Receipts, password resets and OTP backup with idempotency keys and per-key limits.

Marketing campaigns

Newsletters and promotions on the same audience and segments as WhatsApp.

Verification and domain trust

DKIM, SPF, DMARC and BIMI configured and monitored, not a one-time setup.

Lifecycle and re-engagement

Abandoned carts and win-back sequences that escalate to WhatsApp when email goes unopened.

What the email side gives you

Everything deliverability needs, none of it bolted on

Sending

Your SES, your region

SES configured in your AWS account or ours — ap-south-1, eu-west-1, us-east-1

Auth

Authentication done for you

DKIM, SPF, DMARC and BIMI records generated and monitored for drift

Reputation

Managed IP warm-up

A 30-day warm-up curve with automatic throttling on complaint spikes

Campaigns

Campaign builder

Same audience and segments as WhatsApp, with A/B subject testing

Transactional

Single-call send API

Templated transactional email with idempotency keys and per-key limits

Hygiene

Suppression and bounces

Hard bounces, complaints and unsubscribes suppressed across both channels

Monitoring

Inbox placement

Seed-list placement by provider, plus Google Postmaster and Yahoo signals

Journeys

Cross-channel fallback

No open in 24 hours? Escalate to a WhatsApp utility message automatically

Compliance

Consent and preferences

Hosted preference centre, list-unsubscribe headers and a consent audit trail

For developers

One API for every channel

Sending an email is the same call as WhatsApp or SMS — only the channel changes.

  • POST /v1/messages
  • GET /v1/templates
  • POST /v1/webhooks
Read the API docs →
Send a receipt by email
curl -X POST https://api.sendlz.com/v1/messages \
  -H "Authorization: Bearer $SENDLZ_KEY" \
  -H "Idempotency-Key: receipt_48120" \
  -d channel=email \
  -d to=ananya@example.com \
  -d template=order_receipt_v3 \
  -d vars[order_id]=48120 \
  -d vars[total]=899

{ "id": "msg_01JQ...", "status": "queued",
  "channel": "email", "region": "ap-south-1" }

Economics

Klaviyo-style journeys, SES-style economics

Contact-based suites bill you for every address you store, so the invoice grows even in a month you send less. sendlz charges for what you send — and because WhatsApp, SMS and email share one journey builder, an unopened email can escalate to a WhatsApp utility message instead of a second email.

Klaviyo alternative comparison →

Why sendlz

Email without a second stack

Your own SES, your region

ap-south-1, eu-west-1 or us-east-1 — in your AWS account or ours. No vendor lock-in on sending infrastructure.

Managed warm-up

A 30-day curve with automatic throttling on complaint spikes, watched for you.

Shared suppression

One suppression list and one consent ledger across WhatsApp, SMS and email — not three.

Built for developers

The same REST API, signed webhooks and idempotency keys as every other channel.

Email API questions, answered

Do I need my own AWS account for SES?

No. You can connect your own AWS account and region, or let sendlz run it for you in ap-south-1, eu-west-1 or us-east-1 — either way you keep your own sending identity.

What authentication do you set up?

DKIM at 2048-bit, SPF alignment, a DMARC policy enforced at p=reject, and BIMI with a Verified Mark Certificate — generated for your domain and monitored for drift.

How does IP warm-up work?

New sending infrastructure follows a 30-day volume curve so mailbox providers build trust gradually, with automatic throttling if complaints spike during the ramp.

Can an unopened email escalate to WhatsApp?

Yes — that part is live today. List email first and WhatsApp or SMS next on a journey, and sendlz escalates only if the email goes unopened past your window. A visual drag-and-drop canvas for building these flows is on the roadmap; today it’s built through the API.

How is email billed?

Per send, at the Amazon SES rate, plus the flat sendlz platform fee — not per contact stored. A quiet list costs nothing extra.

Ready to send on your own infrastructure?

Connect your domain and send your first email today. No credit card required.

Connect your domain →See the deliverability guide