CleverlyBox - Features
EMAIL INFRASTRUCTURE

Send with confidence.
Build for inboxes, not spam.

CleverlyBox gives you the infrastructure, insights, and control to land in the inbox — every time you send.

Get Lifetime Access See it in action

14

Sending providers built in

$0.10

Per 1,000 emails on your own SES

200×

Cheaper at scale than Mailchimp

∞

Subscribers, no per-contact tax

The hosted-ESP trap

"Unlimited" is a marketing word. Per-1,000 is the real one

Mailchimp doesn't actually own its sending infrastructure either it sits on top of providers like Mandrill (now an add-on) and resells you the capacity at a markup. CleverlyBox cuts the middleman out.

The Mailchimp markup

Roughly $20 per 1,000 emails on a typical Standard plan. Same emails on Amazon SES: $0.10 per 1,000. That's a 200× markup for the privilege of using their dashboard.

The shared-IP risk

Your sender reputation lives on a shared IP pool. One spammy neighbour, one false abuse flag, and your delivery tanks for everyone on that IP including you.

The lock-in

Templates, automations, list segments, custom fields all proprietary. Switching ESPs means rebuilding everything. They count on it. Your replacement cycle is their retention strategy.

The roster

All 14 providers. API + SMTP variants. Pick your weapon

Every major transactional + marketing email provider, plus self-host options for teams that want zero third-party dependency. Connect by API key (cleaner) or SMTP (universal). Mix and match across pools.

Amazon SES
SendGrid
Mailgun
Elastic Email
SparkPost
Brevo
Blast Engine
Postal
Generic SMTP
Sendmail
+ Provider rotation
+ Failover routing
+ Sub-account isolation
+ Custom warmup
The flagship setup

From AWS console to first send in under 15 minutes.

Everything you need to send more, land more, and grow with confidence.

Step 1

create IAM user with AmazonSESFullAccess in your AWS console

Step 2

paste access key + secret into CleverlyBox · Sending Domains

Step 3

copy the SPF + DKIM records into your DNS, hit verify

Step 4

request production access from AWS (out of sandbox), send your first campaign

Multi-provider routing

Run multiple providers. Rotate. Failover. Never lose a send.

Real operators don't bet on one IP. Set Amazon SES as your primary, SendGrid as the failover, Mailgun for transactional. CleverlyBox routes each campaign to the right pool — and reroutes automatically when reputation drops.

Rotation · pool config

Multi-pool sending, native to the platform.

Define pools per use case. Run "marketing-primary" on SES us-east-1 with a $50/day cap. Spillover to "marketing-backup" on SendGrid when SES throttles. Send transactional on a third pool entirely. Each pool has its own warmup curve, daily cap, and reputation tracking.

  • Per-pool daily send caps — match your warmup schedule, not a hardcoded limit
  • Reputation-aware failover — auto-shift traffic when bounce rate exceeds threshold
  • Per-campaign pool override — assign a campaign to a specific pool from the send screen
  • Mix providers inside a single pool — SES + SendGrid splitting load 70/30
Build a segment →
Domains · DNS

SPF, DKIM, custom Return-Path, tracking domains wired into the UI.

Every sending domain is paired with a tracking domain on HTTPS by default. Add a CNAME, hit verify, and CleverlyBox handles the rest including FBL handlers for ISP feedback loops, bounce processors that update subscriber state, and IP warmup webhooks for new IPs.

  • SPF + DKIM record generator — copy-paste into your DNS, one click to verify
  • Custom tracking domain on HTTPS (track.yourdomain.com) — no shared CleverlyBox URLs
  • Custom Return-Path / bounce inbox — ISP-level deliverability requirement
  • FBL handlers — auto-process Yahoo/AOL feedback loop complaints
  • IP warmup webhooks — call your warmup service after every successful send
Agency feature tour →
For agencies

SendGrid sub-account isolation. One client's spam doesn't taint another's inbox

If you're running 12 client lists through one shared SendGrid account, you're one bad complaint away from killing all 12. CleverlyBox's SubAccountSendGrid model wires each client to its own SendGrid sub-account isolated reputation, isolated quotas, isolated billing.

Sub-account · SendGrid

Each client gets its own sender reputation

The SendGrid sub-account API lets you provision isolated sending environments under one parent account. CleverlyBox surfaces this natively: when you create a client sub-account in CleverlyBox, you can wire it to its own SendGrid sub-account in two clicks credentials stored encrypted, reputation isolated forever.

  • One CleverlyBox sub-account → one SendGrid sub-account → one isolated IP pool
  • Per-client send quotas, IP allocations, and reputation scores
  • Spam complaint on Client A's list never touches Client B's deliverability
  • Single SendGrid bill at the agency level, multi-tenant isolation underneath
Build a segment →
The long tail

Blast Engine, Postal, Sendmail the providers other ESPs ignore.

Most platforms ship 3 integrations and call it "integrations." CleverlyBox supports the providers that actually matter for compliance, regional sending, and self-hosted operations.

Blast Engine · Japan

Regional providers that mainstream ESPs forget exist

Selling into Japan? Blast Engine handles Japanese ISP requirements (line-break encoding, Subject MIME B-encoding, NTT DOCOMO carrier rules) natively. Selling into the EU and need GDPR data residency? Mailgun EU + SparkPost EU. Selling into India? Brevo's Indian region. CleverlyBox covers them all without forking your stack.

  • Blast Engine — Japan-native ESP with carrier-mail compliance (api + smtp variants)
  • Mailgun EU + SparkPost EU — GDPR data residency for European audiences
  • Brevo (formerly Sendinblue) — strong in India, France, Spain
  • Elastic Email — Eastern European ESP, low-cost transactional
Build a segment →
Postal · self-hosted

Self-host Postal. Pay zero per-send. Forever.

For teams that want zero third-party dependency: CleverlyBox plugs straight into Postal, the open-source mail server. Run Postal on your own VPS, point CleverlyBox at it, and you've built a fully owned email stack — sending infrastructure included. The only cost is the $20/mo server bill.

  • Connect to any Postal instance via API key
  • No per-email charge — server cost only
  • Full IP and reputation ownership at the MTA level
  • Pair with SES as warmup-failover for production reliability
Agency feature tour →
Side-by-side

CleverlyBox vs hosted ESPs sending infrastructure

The numbers behind the sales pitch. Use Mailchimp's own pricing
page to verify each row.

Capability Mailchimp Std ActiveCampaign
BEST
CleverlyBox
Bring your own SES / SendGrid / Mailgun ✕ ✕ ✓ 14 providers
Cost per 1,000 emails (250K plan equivalent) ~$20 ~$15 $0.10 (own SES)
Provider rotation / multi-pool sending ✕ ~ enterprise ✓ built-in
Reputation-based failover ✕ ✕ ✓
SendGrid sub-account isolation for clients ✕ ✕ ✓ native
Custom tracking domain on HTTPS ~ paid add-on ✓ ✓ built-in
Self-hosted MTA option (Postal, Sendmail) ✕ ✕ ✓
Per-subscriber pricing penalty Yes Yes No • flat lifetime
FAQ

Questions people ask

No. You can start on generic SMTP, Brevo's free tier, or Elastic Email's free tier on day 1. SES is the cheapest at scale, but it requires AWS production access (out of sandbox), which can take 24–48 hours. Most operators provision SES in week 1 and migrate their main sends after warm-up.

No. CleverlyBox is a one-time license fee. The only sending cost is what your provider charges you directly — Amazon SES at $0.10/1,000, Mailgun at $0.80/1,000, or zero if you self-host Postal. CleverlyBox takes nothing per send.

For pure cost: Amazon SES. For setup speed: Brevo or Elastic Email (free tiers, no production-access waitlist). For B2C transactional + marketing on the same stack: Mailgun. For agencies running 5+ clients: SendGrid (only provider with native sub-account isolation). For Japan: Blast Engine. Most operators run SES + SendGrid as a primary/failover pair.

API integrations use the provider's official REST/HTTPS endpoint — generally faster, cleaner error handling, better for high-volume sends. SMTP integrations use port 587 with TLS — universal, works with any provider on the planet, slightly slower at high concurrency. Most providers ship both. CleverlyBox supports both for SES, SendGrid, Mailgun, Elastic Email, SparkPost, Brevo, and Blast Engine.

You define a primary pool (e.g., SES) and a failover pool (e.g., SendGrid). CleverlyBox watches the primary pool's bounce rate, complaint rate, and API error rate in real time. When any threshold trips — bounce rate over 2%, API throttle, AWS outage — in-flight sends reroute to the failover pool. The campaign continues without manual intervention. Once the primary recovers, traffic shifts back automatically.

Yes — and it's a common use case. Cold email requires aggressive warm-up, sub-account isolation, and the ability to rotate domains and IPs. CleverlyBox supports all three. Use a separate sending pool for cold outreach, never mix it with your transactional or marketing pool, and follow the warmup playbook in the use-cases section.

Your subscriber list lives in CleverlyBox's database — not in SES. If AWS suspends SES (rare, usually for repeated abuse complaints), you connect a different provider, point your sending pool at it, and keep going. Your list, automations, templates, segments, and analytics are all unaffected. This is the entire reason "bring your own provider" exists as a feature.
STOP OVERPAYING

Send the right message. To the right people. Every send.

CleverlyBox segments are dynamic, conditional, and reusable across campaigns and automations. Buy lifetime access for $49 — every operator and every signal is unlocked on day one.

Get Lifetime Access See it in action