For agencies & freelancers
Raechly writes, personalises and sends client outreach from your own Amazon SES identity. Every one of its 22 tools is exposed to Claude over MCP, so the whole product runs in conversation. Warmup only counts when replies actually come back, and Raechly will not send until they do.
› Set up mail.acme.com for outbound, warm two mailboxes, and draft a 3-step sequence for agency owners.
✓ create_domain · mail.acme.com · us-east-1
→ 3 DKIM CNAMEs, MAIL FROM MX + SPF, DMARC
✓ check_domain · verified
✓ create_mailbox ×2 · reply capture on
✓ start_warmup ×2 · pending → warming
✓ create_campaign · 3 steps · draft
Domain verified and both mailboxes are warming. I left the campaign in draft so you can read the copy first.
Why it is built this way
Agent-native
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.
Streamable HTTP MCP server, bearer-auth per organization.
Own your reputation
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.
Hand-rolled SES v2 client, SigV4-signed, raw MIME per message.
Verified warmup
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.
Per-mailbox reply_capture flag, reconciled hourly; sends gated on it.
Built to the RFCs
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.
RFC 8058 POST endpoint live; SES bounce/complaint webhook verified by SNS signature.
Guardrails
Anyone can send more email. The hard part is sending enough to matter without burning the domain you spent three weeks warming. Raechly takes some choices away from you on purpose.
How deliverability works here →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.
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.
Unsubscribed and bounced leads are never resurrected by a re-import. Bulk imports upsert by email and skip anyone already suppressed.
The send pipeline takes a lock. A manual trigger during the hourly run returns busy instead of double-sending your sequence.
Honest comparisons
Each comparison says plainly who should pick the competitor. If you need a bundled lead database or LinkedIn steps, we will tell you where to go.
All-in-one
Unlimited mailboxes, a bundled lead database and a unified inbox.
$37/mo (Growth)
All-in-one
Best per-mailbox economics, built for agencies running many clients.
$39/mo (Basic)
Data-first
A 275M-contact B2B database with sequencing attached.
$49/seat/mo (Basic, annual)
Sales engagement
Multichannel sequences with email, LinkedIn and calling in one flow.
$39/user/mo (Email Outreach)
Deliverability, explained
RFC 8058 one-click unsubscribe lets a mailbox provider opt a recipient out with a single POST request, no landing page and no confirmation step. Gmail and Yahoo require it from bulk senders.
Email warmup gradually increases sending from a new mailbox while generating positive engagement, so mailbox providers build a reputation for the address before it sends cold volume.
Inbox placement is the share of delivered messages that reach the primary inbox rather than spam or a promotions tab. It is distinct from delivery rate, which only counts acceptance by the server.
Sending reputation is the trust score mailbox providers assign to your domain and IP based on complaint rate, bounce rate, engagement and authentication history. It determines inbox placement.
Every capability is exposed over the Model Context Protocol — all 22 of them. Your assistant registers domains, reads back DNS records, warms mailboxes, imports leads, writes sequences, fires the pipeline and reads the send log. The dashboard is the optional surface, not the primary one.
Yes. Raechly sends through a verified Amazon SES identity in your AWS region, which is the whole point: the sending reputation accrues to an identity you own. Setup is two tool calls and a set of DNS records, and your assistant can walk you through both.
Those platforms send on their own infrastructure, so your reputation is a position inside their system. Raechly sends on yours. The second difference is warmup: Raechly runs the loop on pool inboxes you register and refuses to send from any mailbox whose inbound path is unverified.
Yes, in bulk, upserted by email. Unsubscribed and bounced addresses are never resurrected by a re-import, which is the mistake that generates complaints.
Four caps, applied per mailbox, per domain and per campaign, plus a hard 30/day ceiling that overrides any per-mailbox limit configured higher. Send windows are evaluated per lead in the campaign timezone.
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.