DNS that checks itself and warns you
SPF, DKIM, DMARC, bounce and tracking records are re-checked in the background. If SPF or DKIM breaks, we email you right away, and the portal shows the exact value to set.
Send through one API call or SMTP, then follow every message to the inbox. Delivered, deferred or rejected, each event carries the receiving server's own answer.
Built exclusively for transactional email. Transparent pricing, honest limits, no surprises.
| Mailverick | Typical email provider | |
|---|---|---|
| Email validation | Included in every plan | Separate paid product |
| Dedicated IPs | Included, with managed warmup | Paid add-on |
| Features by plan | Every feature on every plan | Locked behind higher tiers |
| Contacts | Unlimited on every plan | Capped on free and lower tiers |
| What it sends | Transactional email only | Mixed with marketing campaigns |
| Where your data lives | EU only, no Cloud Act exposure | US-owned cloud |
DNS checks, IP reputation, address validation: the parts that usually need a second vendor ship on every plan.
SPF, DKIM, DMARC, bounce and tracking records are re-checked in the background. If SPF or DKIM breaks, we email you right away, and the portal shows the exact value to set.
Dedicated IPs are added as your sending volume grows. We warm them up and watch their reputation, so there is nothing to manage and no add-on on your bill.
At a kiosk or a self-checkout, nobody corrects their address once they have left. Validate it while they are still at the screen and suggest the fix. Signup forms work the same way.
One REST endpoint or our SMTP relay. Service accounts with scoped API keys.
Tracking links, return-path and BIMI on your own domain. No Mailverick branding on any plan.
Delivery, bounce, open and click rates at a glance. Readable DMARC reports are coming soon.
Owner, Admin and Member roles, plus separate organizations with their own domains, IP pools and analytics.
One REST call, the Node.js SDK or plain SMTP. Use whatever your stack already speaks.
import { Mailverick } from "@bytewise-solutions/mailverick";
const client = new Mailverick("mvk_id_xxx", "mvk_sec_xxx");
await client.sendEmail({
from: { email: "you@yourdomain.com" },
to: [{ email: "user@example.com" }],
subject: "Hello",
body: { html: "<p>Hello!</p>" },
}); # 1. Get a token
curl -X POST https://api.mailverick.com/v1/token \
-H "Content-Type: application/json" \
-d '{
"api_key_id": "mvk_id_xxx",
"api_key_secret": "mvk_sec_xxx"
}'
# 2. Send
curl -X POST https://api.mailverick.com/v1/send-email \
-H "Authorization: Bearer <access_token>" \
-H "Content-Type: application/json" \
-d '{
"requests": [{
"from": { "email": "you@yourdomain.com" },
"to": [{ "email": "user@example.com" }],
"subject": "Hello",
"body": { "html": "<p>Hello!</p>" }
}]
}' SMTP_HOST=smtp.mailverick.com
# Use 587 with STARTTLS, or 465 with implicit TLS. Cleartext auth is refused.
# Django and Spring need their TLS setting enabled explicitly.
SMTP_PORT=587
SMTP_USER=mvk_id_xxxxxxxxxx
SMTP_PASS=mvk_sec_xxxxxxxxxx Each email reports what happened to it, with a clear reason, and the event is pushed straight to your own stack.
Every plan gets the same product. Drag to your monthly volume to see what it costs.
Prices shown exclude VAT. The final amount at checkout may include VAT depending on your country.
The short version of who we built this for, and what we do not carry.
Developers and product teams sending email their application generates: a SaaS sending password resets and invoices, a store sending order and shipping confirmations, a marketplace sending booking details or support replies. If your email is triggered by your code rather than scheduled by your marketing team, you are in the right place.
One question settles it: did the recipient's own action, just now, make this specific message necessary? A password reset exists because someone clicked the forgot-password link. An order confirmation exists because someone bought something. The recipient is usually waiting for it. If you chose the moment and the audience, it is a campaign.
Read the full breakdownNo. Our Terms of Service prohibit campaigns and unsolicited bulk email, and there is no template editor or campaign builder to send them with. This is a product decision. Campaign mail draws complaints at many times the rate of transactional mail, and that reputation damage would land on the same IPs and domains carrying everyone's password resets.
Yes, for the transactional half. Send campaigns through a platform built for them, on a separate subdomain, so their reputation stays separate from the mail your users actually need. That separation is worth doing whichever providers you pick.
Yes. Mailverick is a REST API and an SMTP relay, so sending means writing code or pointing an existing integration at us. There is no drag-and-drop editor, no contact lists, and no campaign scheduling, because those are the tools of a different job.
Yes. The free plan sends 1,000 emails a month to unlimited recipients, and every feature is included on every plan: you choose a volume, not a tier.
1,000 free emails/month to unlimited recipients. All features included. Upgrade when you're ready.