Sign up and send today on CleverlyBox's own sending infrastructure — no AWS console, no DNS wrangling, no third invoice. When your volume justifies your own provider, plug it in. Nine of them are supported, and you can run several at once.
You sign up, and before a single email leaves the building you're told to open an Amazon account, request production access, verify an identity, wait for a review, and paste three keys into a form. That is not onboarding. That is a chore list.
CleverlyBox sends on its own shared infrastructure by default. Import a list, build the campaign, hit send. The sending server is already there, already warm, already authenticated. You do nothing.
Shared sending is included on every plan. Bring-your-own provider unlocks from the Business tier.
There comes a point where you want your own reputation, your own IPs and your own per-thousand rate negotiated directly with a vendor. That is when bring-your-own earns its keep — not before. Connect any of these from the Business tier upward.
Each provider is configured as a sending server. Add as many as you like. Every one gets a test connection button and a test send button — you find out it works before a campaign does.
Add more than one sending server and CleverlyBox spreads the volume across them using a weighted distribution. Set one as primary. Give a brand-new IP a small share while it warms and let the established servers carry the rest.
Every server also carries its own sending limits — per-hour and per-day caps you define. The platform respects them. A vendor quota is a wall you find out about at 2am; a limit you set is a schedule.
CleverlyBox will issue you SMTP credentials. Any application that can speak SMTP — your WordPress site, an n8n workflow, a Laravel app, a cron script, a printer if you insist — can hand its mail to CleverlyBox instead of to a mail server you have to run.
Host smtp.cleverlybox.com Port 587 (STARTTLS) Username issued in-app Password issued in-app From hello@your-verified-domain.com
Illustrative. Real host and credentials are generated for your account.
Mail arriving over the relay is signed with your sending domain's DKIM key — the same key CleverlyBox generated for you — then relayed through your sending server. Transactional mail from your app inherits the authentication you already built.
The relay will not sign mail for a domain you have not proven you own. Verify the domain first — OWNERSHIP, DKIM, SPF, DMARC — and the relay follows.
SMTP relay is a plan feature, not a universal one. It's included on Business and Agency — the pricing page breaks down the included volume, credentials and top-ups before you rewire your stack around it.
Included volume, credential limits, rate ceilings, prepaid top-ups, and a setup guide for Laravel, WordPress, Nodemailer and PHPMailer.
Nothing about this is a one-way door. The three stages are all valid destinations — plenty of accounts never leave the first.
Included from the free tier. Shared sending infrastructure, already configured. You import a list and send. Most senders stay here indefinitely, and that is a perfectly good outcome.
Volume grows, or you want your own IP reputation, or your vendor rate beats ours. Add an SES or SendGrid or Mailgun server, run a test send, make it primary. The rest of the platform does not change.
Several servers, weighted, each with its own daily quota, one of them a fresh IP working through a warm-up schedule. Campaigns are routed across the fleet without you thinking about it.
No. That is the entire point of this page. Sending is included by default on CleverlyBox's own infrastructure. You can create an account, import contacts and send a campaign without touching a provider console. Bringing your own provider is an option that unlocks from the Business tier, for people who have outgrown the default.
Nine: Amazon SES, SendGrid, Mailgun, Elastic Email, SparkPost, Blastengine, generic SMTP (any host), Sendmail, and Gmail via OAuth. Most support both an API and an SMTP variant — pick whichever your vendor plan favours.
Yes. Add as many as you want, mark one as primary, and volume is spread across them with weighted distribution. Each server has its own sending limits, so you can throttle a new IP down to a trickle while the established ones do the work.
Every sending server has a test connection check and a test send. Run both. If the credentials are wrong or the host is unreachable, you find out in the settings screen rather than in a bounce report.
Pointing other software at CleverlyBox. We issue you SMTP credentials; your WordPress site, n8n instance or application uses them as its outbound mail host. The mail gets DKIM-signed with your sending domain and relayed through your sending server. It requires a verified sending domain and a plan that includes the relay entitlement.
No. Deliverability tooling, warm-up, auto-pause, bounce handling, analytics and the API all work identically whether the mail leaves via our infrastructure or yours. The provider is a transport choice, not a different product.
2,900+ businesses, 13.5M+ emails delivered. Most of them started sending before they ever opened a provider console.