Sending infrastructure, with an agent on the front.
Raechly is a cold email platform that sends through your own Amazon SES identity, verifies warmup before it trusts it, and exposes every capability to your AI assistant. Here is the whole thing, in order.
Setup, step by step
- 01
Register a sending domain
Raechly creates the Amazon SES identity in your region and hands back every DNS record you need: three DKIM CNAMEs, the MAIL FROM MX and SPF pair, and DMARC. Use a dedicated domain, never the one your company runs on.
create_domain → - 02
Verify, then create mailboxes
Publish the records and poll until DKIM verification succeeds. Sending stays blocked until it does. Mailboxes created on a verified domain get their inbound reply-capture rule provisioned at the same time.
check_domain → - 03
Warm on inboxes you own
Register pool accounts — real inboxes you control — and start the ramp. Mailboxes move pending → warming → ready on a schedule. Any mailbox whose reply path is unverified is blocked from sending entirely.
start_warmup → - 04
Import leads and build the sequence
Bulk import upserts by email and never resurrects a suppressed address. Campaigns are created with every step, the send window and the daily cap in one call, and start as drafts so you read the copy first.
create_campaign → - 05
Let the pipeline run
An hourly pass handles warmup progression, warmup sends and every due campaign lead. Send windows are evaluated per lead in the campaign timezone. Failures land in the send log with the verbatim error.
trigger_send →
The four decisions underneath it
Agent-native
Run outbound from your AI assistant
All 22 tools are exposed over the Model Context Protocol. Connect Claude, Claude Code or Cursor once and drive the entire product in plain language — register domains, read DNS records, warm mailboxes, import leads, build sequences, fire the pipeline, read the send log.
Own your reputation
Your Amazon SES identity, not a shared pool
Raechly sends through your own verified SES identity in your own AWS region. Your domain reputation is yours: it survives platform churn, it is not diluted by whoever else is on a shared IP, and you can take it with you.
Verified warmup
Warmup that proves replies actually landed
Most warmup is unfalsifiable — you are told threads happened. Raechly provisions an inbound routing rule per mailbox and refuses to send until replies are demonstrably being captured. A mailbox with no verified inbound path does not send.
Built to the RFCs
One-click unsubscribe, done correctly
Every message carries List-Unsubscribe with RFC 8058 one-click POST, Precedence: bulk and a stable Message-ID. That is what Gmail and Yahoo bulk-sender rules ask for, and it is why the raw MIME path exists at all.
What it refuses to do
Read these as product features, because that is what they are. Full reasoning in the four caps that keep a sending domain alive.
Timezone-aware send windows
Per campaign: IANA timezone, allowed weekdays, start and end hour. A lead in Berlin is not emailed at 3am because your server is in Virginia.
Four layers of daily caps
Per mailbox, per domain, per campaign, plus a hard 30/day ceiling that overrides any per-mailbox limit set higher. Volume is the fastest way to burn a domain, so the floor is low by default.
Suppression that holds
Unsubscribed and bounced leads are never resurrected by a re-import. Bulk imports upsert by email and skip anyone already suppressed.
Single-flight pipeline
The send pipeline takes a lock. A manual trigger during the hourly run returns busy instead of double-sending your sequence.
Product questions
What do I need before I start?
An AWS account with SES access, a dedicated sending domain you can add DNS records to, and at least one real inbox to use as a warmup pool account. That is the whole list.
How long until I can send real campaign mail?
DNS verification is usually minutes. Warmup is the honest constraint: a new domain should ramp for two to three weeks before it carries meaningful cold volume. Anyone promising same-day sending on a fresh domain is selling you a reputation problem.
Does the dashboard do everything the MCP server does?
Both surfaces hit the same API. The dashboard covers campaigns, leads, mailboxes, warmup, activity and settings. The MCP server exposes all 22 tools, which is the fuller surface, and it is the faster path for setup and debugging.
What happens when a lead replies?
Replies land in the mailbox you sent from, which is a real inbox on your domain. Raechly does not put itself between you and the conversation.
Can I use AI to write the campaigns?
Yes. Campaign generation is built in, and because the whole product is exposed over MCP, your assistant can read your leads and draft the sequence against them rather than producing generic copy.
Point your assistant at it and see.
Connect the MCP server, register a domain, publish the DNS records it hands you. You will know inside an hour whether this is the setup you want.