One place for every email your business sends
Marketing and transactional mail share one sending account, one suppression list and one event feed — so a promo blast and an order confirmation are never fighting each other for your reputation.
Campaign editor
Build the email from blocks, drop in merge fields, show a block only to one segment, and preview it as a real contact on desktop, mobile and in dark mode.
Automations
Welcome, win-back and date-triggered flows that branch on what each contact did. Every contact moves at its own pace, and you can edit a live flow without disturbing the people already in it.
Segments that stay editable
Rules over any field you hold — engagement, tags, source, country, consent proof, your own custom fields and dates — with a live match count as you build them.
Contacts with proof
Every contact carries when, how and from where they consented, plus an activity timeline. Import forces you to say how the list was collected, and double opt-in is one switch.
List cleanup on SES
Amazon SES validates each address without sending to it — syntax, DNS, whether the mailbox exists, role and disposable addresses — and returns a verdict you can segment on.
Statistics, ungated
Opens and clicks by mailbox provider, device and country, a click map on the email itself, and a side-by-side comparison with any other campaign. Apple's machine opens are excluded from the headline rates.
Transactional API & SMTP
Scoped API keys, an SMTP relay for shops that only speak SMTP, signed webhooks retried for 24 hours, and a searchable message log with per-message latency.
Sending domains
Add a subdomain, copy four sets of DNS records, press Verify. We create the SES identity, watch the records and only mark the domain verified when SES itself says DKIM passed.
From nothing to a verified sender, in an afternoon
You never touch an AWS console and you never sign an ESP contract. The only thing we need from you is four DNS records on a subdomain you choose — your existing mail keeps its own reputation, untouched.
Something like mail.yourshop.gr. Marketing and transactional get separate identities, so a promo can never drag your order emails into spam.
1 minuteThree DKIM records, an SPF include, a DMARC policy and a custom MAIL FROM. Copy them from the screen into your DNS provider — we check them for you as they propagate.
10 minutesWe ask SES directly. The domain turns verified only when DKIM actually passes at Amazon — not when a local lookup happens to succeed.
minutes to an hourNew marketing domains ramp over four weeks, capped per mailbox provider per day. Import your list, build the campaign, send a test, then send for real.
same dayReputation is a feature here, not a support ticket
Since February 2024 Gmail and Yahoo have required bulk senders to authenticate properly, offer one-click unsubscribe and stay under a 0.3% spam rate. Sendrill does all three by construction — and steps in before your numbers get you blocked.
Warm-up, on by default
A brand-new domain has no reputation, and the first big send is exactly the one that decides it. Every new marketing domain ramps for four weeks, capped per mailbox provider per day — Gmail, Microsoft, Yahoo and the rest each get their own budget. Anything over the cap waits for tomorrow instead of being burned.
Per mailbox provider, per day. From day 29 the cap comes off. Seed mailboxes measure where your mail actually lands while the ramp runs.
Guardrails you don't have to watch
- Hard bounces and complaints suppress themselves. The address never gets another send, from any campaign or any API call.
- Your sending pauses before Amazon pauses it. Cross the thresholds and we stop you, tell you why, and wait for you to fix the list — rather than letting SES suspend the account.
- Every campaign carries one-click unsubscribe. RFC 8058 List-Unsubscribe-Post, aligned From and DKIM, DMARC on the sending subdomain.
- Marketing and transactional never share an identity. A newsletter that goes badly cannot take your order confirmations down with it.
An API for your app, a relay for everything else
Order confirmations, password resets and invoices go out through the same account, the same suppression list and the same event feed as your campaigns. If a platform only speaks SMTP — WooCommerce, WP Mail SMTP, an ERP from 2011 — point it at the relay and it inherits every rule the API enforces.
# send one message curl https://api.sendrill.com/v1/messages \ -H "X-API-Key: $SENDRILL_KEY" \ -H "Content-Type: application/json" \ -d '{ "from": "[email protected]", "to": ["[email protected]"], "subject": "Your order #4182", "html": "<p>Thanks, Maria.</p>", "tags": ["order", "shop"] }' # 202 Accepted # { "messages": [ { "id": "msg_7Kq2…", # "to": "[email protected]", # "status": "sent" } ] }
use Illuminate\Support\Facades\Http; Http::withHeaders(['X-API-Key' => config('services.sendrill.key')]) ->post('https://api.sendrill.com/v1/messages', [ 'from' => '[email protected]', 'to' => [$order->email], 'subject' => "Your order #{$order->number}", 'template' => 'order-confirmation', 'vars' => ['total' => $order->formattedTotal()], ]) ->throw(); // Suppressed recipients come back as "skipped" — never // as an error, and never as a second send.
const res = await fetch('https://api.sendrill.com/v1/messages', { method: 'POST', headers: { 'X-API-Key': process.env.SENDRILL_KEY, 'Content-Type': 'application/json', }, body: JSON.stringify({ from: '[email protected]', to: [customer.email], subject: `Your order #${order.number}`, html: render('order-confirmation', order), }), }); const { messages } = await res.json();
SMTP relay
Webhooks
Signed with a shared secret, retried for 24 hours, and fired for every state a message can reach.
deliveredthe provider accepted itopened clickedmachine opens flagged, not countedbounced complainedaddress suppressed automaticallyunsubscribedfrom the one-click header or the preference pagePay for volume. Nothing else is locked.
Every tier gets every feature — A/B tests, automations, provider-level statistics, campaign comparison, the transactional API, unlimited contacts and unlimited sender domains. The tiers differ by how many emails you send, and that is all.
- Every feature, no tiers
- Unlimited contacts & sender domains
- Inbox placement monitored on 1 domain
- Every feature, no tiers
- Unlimited contacts & sender domains
- Inbox placement monitored on 3 domains
- Every feature, no tiers
- Unlimited contacts & sender domains
- Inbox placement monitored on 10 domains
- Every feature, no tiers
- Priority support
- Inbox placement monitored on 50 domains
How much would you pay?
Most email platforms put link-level analytics, campaign comparison, A/B testing and automation behind their top plan. Sendrill doesn't gate any of it. If you can send, you can measure — and the only reason to move up a tier is that you are sending more.
The things people ask before they move
Do I need an AWS account?
Will this interfere with my normal company email?
How soon can I send?
Where does my data live?
Can I bring an existing list?
What happens if I go over my monthly allowance?
Does it work with WordPress and WooCommerce?
Is there a free plan?
Run by the people who built it
Sendrill is built and operated by eSolutions Softhouse in Greece — the team behind CookieTrust, ComplianceMonitor, ThreadDesk, ImgHaste and Domainwise. Deliverability questions, a domain that won't verify, an invoice: one team answers, in Greek or English.
Part of the CookieTrust ecosystem
One login covers cookie consent, live chat, image delivery, .gr domains — and now the email you send. Contacts collected through your cookie banner or a ThreadDesk chat arrive with their consent already recorded, which is something an outside email platform cannot do for you.
Send from your own domain. Today.
Add a subdomain, paste four DNS records, and your first campaign goes out this afternoon — warmed up, authenticated and measured.