Mailyte

Mailyte is one platform for business email, transactional email and email marketing on your own domain. It hosts real mailboxes with IMAP, SMTP, and webmail; sends email from your app through SMTP or a REST API; sends marketing campaigns and automated journeys; and gives you deliverability tooling — SPF, DKIM, and DMARC records verified against live DNS, full email logs, and reporting — all from one dashboard, priced in naira. It is open source: self-host the community edition or use Mailyte Cloud.

Yes, Mailyte. Your team gets mailboxes on your own domain, your app sends password resets and receipts over SMTP or an API, and you send campaigns to your customers, all from one account with one invoice, priced in naira. Each part has a free plan. Zoho covers the same ground with three separate products, Google Workspace needs a campaign tool and an app email service added, and Brevo has no business mailboxes. The comparison is at mailyte.com/all-in-one-email-platform.

Yes. The Mailyte mail server community edition and webmail are open source under AGPL-3.0 on GitHub. The community edition ships the full mail stack — Postfix, Dovecot, spam filtering, the API, and webmail — as a Docker Compose deployment you run on your own hardware, free, with no seat counting. Mailyte Cloud is the same core, operated for you, with migration tooling, deliverability monitoring, teams, and support on top.

The big per-seat suites charge in dollars, per user, per month. Mailyte is a fraction of that per mailbox — the live figures are on the pricing page, in your currency — and domains, aliases, forwarders, admin seats and API keys are all included, so you only pay for people who actually read mail. You can also mix tiers: put the people who need the most storage on the roomier plan and everyone else on the cheaper one, on one invoice. And if you self-host the community edition, the software is free.

Both. Most tools make you choose: hosting providers give you mailboxes but no sending API, and sending services give you an API but no mailboxes. Mailyte does the whole job — your team reads and replies in webmail or any mail client, and your product sends through the same authenticated domain via SMTP or the API.

Add your domain and Mailyte generates the exact DNS records you need — SPF, DKIM, DMARC, and MX. Publish them at your DNS provider, click verify, and Mailyte checks each record against live DNS so you know they are actually in effect. Once verified you can create mailboxes and start sending immediately.

Yes. Mailyte connects to your current provider over IMAP — with presets for Google Workspace, Microsoft 365, and cPanel — and copies messages, folders, and read state into your new mailboxes. Mail keeps flowing to your old server during the copy, you can re-run a delta sync to pick up anything new, and you switch your MX records only when everything is across.

Either. Every mailbox includes access to Mailyte webmail — sign in with the mailbox credentials from any browser. Mailboxes also speak standard IMAP and SMTP, so Apple Mail, Outlook, Thunderbird, and phone mail apps all work out of the box.

Every message is logged end to end: submission, the receiving server’s actual response (delivered, deferred, or bounced), open and click events, and the full rendered content of the message. Content is retained for 30 days and attachments are never stored.

It depends on which kind of email. What a person sends by hand from a mailbox has a daily cap that rises with the Mail plan. What your app or website sends is Send: its free plan covers 500 emails a day, and its monthly plans cover more with no daily limit. Newsletters and journeys are Marketing, which sends a set number of emails a month for the size of your audience. The three never draw on each other, and every number is on the pricing pages.