An email provider is a company that gives you the service you need to send, receive or store email. The phrase covers three quite different things: a mailbox provider that hosts your inbox, a business email host that gives a company mailboxes on its own domain, and a sending provider that delivers email from your website, app or campaigns. People searching "email provider" usually mean the first, but a business often needs two of the three. This guide explains each type, the differences, how to choose, and how the pieces fit together.
What is an email provider?
Email works because several systems cooperate. A mail server accepts messages, other servers pass them along, and an inbox stores them for you to read. An email provider runs some of those systems for you, so you do not have to operate servers, keep them patched, or manage how receiving mail systems treat your messages.
Providers differ by what they run and who they serve. A free personal service gives you an address and an inbox. A business host gives your whole team mailboxes at a domain you own, such as name@yourcompany.example. A sending provider takes messages from your software and delivers them at volume, with tools to measure the result. Mixing these categories is the main reason choosing an email provider feels confusing.
The three main types of email provider
| Type | What it does | Who it is for | Examples of the category |
|---|---|---|---|
| Mailbox provider (personal) | Hosts an inbox and address for an individual | Individuals, family, personal use | Gmail, Outlook.com, Yahoo Mail, Proton Mail |
| Business email host | Hosts mailboxes on your own domain, with shared calendars, admin controls and security settings | Companies, teams, agencies | Google Workspace, Microsoft 365, Zoho Mail |
| Sending provider (SMTP relay or email API) | Delivers email sent by software: receipts, password resets, alerts, newsletters | Developers, product teams, marketers | MigoSMTP and other SMTP and API services |
The names in the last column only show what each category looks like; the right provider for you depends on your needs. We are a sending provider, so we know that side best, and we are open about it. Compare any provider against your own requirements.
Mailbox provider vs sending provider
A mailbox is designed for people. It has a user interface, folders, search, calendar integration and sensible limits for person-to-person mail. A sending provider is designed for machines and campaigns. It accepts mail from your application over SMTP or an API, signs it with your domain, handles retries when a recipient server is busy, and reports bounces and complaints.
Using a mailbox for application email is a common mistake. Personal and business mailboxes have sending limits, they are not built to report delivery results to your software, and a burst of automated mail can get the account restricted. Our guide to choosing between SMTP and an email API explains how applications connect to a sending provider.
How to choose an email provider
Start with what you need the email for. These questions narrow the field quickly.
- Who sends, and who reads? If people need an inbox, you need a mailbox or business email host. If software sends, you need a sending provider. If both, you need both.
- Do you need your own domain? A professional address on your domain builds trust and keeps you in control of it. Free personal addresses are fine for individuals, but weaker for a business.
- How much will you send? Estimate the daily and peak volume. Check the provider's published limits and what happens when you exceed them.
- How strong is the authentication support? The provider should help you publish SPF, DKIM and DMARC for your domain. Our guides on SPF, DKIM and DMARC show what that involves.
- What security options are offered? Look for encrypted connections, two-factor sign-in for account access and scoped credentials. Our article on email SSL and TLS explains the connection side.
- How is deliverability handled? Ask how the provider manages sender reputation, bounces, complaints and suppression lists. Read our guide to deliverability metrics so you know what to ask for.
- What does it cost, and how is it priced? Mailbox hosts usually charge per user. Sending providers usually charge by volume or by plan. Check what is included, what is extra, and what a plan change costs.
- How good is support? You will need help once, at a bad moment. Check how to reach support and what is documented.
- Can you leave? Pick a provider whose data you can export and whose records you control. Keep your domain registered in your own name.
Free vs paid email providers
Free providers fund themselves in other ways, usually by showing ads or by offering paid tiers. They are fine for personal mail. They are a weak base for a business because you cannot use your own domain on most free tiers, support is limited, and sending limits are tight. Paid business hosts give you your domain, admin controls, more storage and support. For sending, paid plans give you dedicated settings, reporting and the chance to fix problems with a person, rather than a forum.
What a business actually needs: a simple setup
Most small and mid-sized companies end up with the same shape, and it is worth planning it from the start.
- A business email host for staff mailboxes on your domain.
- A sending provider for everything your systems send: sign-up emails, receipts, password resets, notifications and marketing.
- DNS records that tie them together. One SPF record that lists every service allowed to send for your domain, a DKIM key for each service, and one DMARC policy for the domain. Using a subdomain for application mail, for example mail.yourcompany.example, keeps reputation separate from your staff mailboxes.
Do not publish two SPF records. A domain must have a single SPF record, and every sending service has to be listed in it. Two records make SPF fail with a permanent error. Our SPF guide shows how to combine them.
Warning signs when comparing providers
- Promises of guaranteed inbox placement. No sender can guarantee that every message reaches the inbox, because receiving systems make the final decision.
- No clear information about how complaints, bounces and abuse are handled.
- No way to authenticate your own domain.
- Pricing that hides the limits that matter to you.
- No exit path for your data.
Moving to a new email provider
Switching is easier if you plan it. Lower the DNS TTL values on the records you will change a day or two ahead, set up the new provider and authenticate your domain, send a test message to several mailbox providers, move traffic in stages, and monitor bounces and complaints as you go. If you send at volume, warm up gradually, as our IP warm-up guide explains. Our article on migrating to a new email provider without losing deliverability goes through the steps in detail.
Shared or dedicated infrastructure
Sending providers usually offer shared IP addresses, where many customers send from the same pool, and dedicated IP addresses that only you use. Shared pools are managed by the provider and suit lower volumes. A dedicated address gives you control of your reputation and suits steady, higher volume. Read dedicated IP vs shared IP before you decide.
Looking for a sending provider for your application? Tell us what you send and roughly how much, and we will tell you plainly whether we are a good fit, and how to set up the domain and connection.
References and further reading
Frequently asked questions
What is an email provider?
An email provider is a company that runs the systems for sending, receiving or storing email so you do not have to. Some host your inbox, some host mailboxes on your own domain, and some deliver email that your software sends.
What is the difference between an email provider and an email service provider?
The first term often means a mailbox host such as a personal inbox service. An email service provider (ESP) usually means a company that sends email for you, such as transactional or marketing email, over SMTP or an API.
Can I use my normal mailbox to send newsletters or app emails?
It is not a good idea. Mailboxes have low sending limits, do not report delivery results to your software and can be restricted for bulk or automated sending. Use a sending provider instead.
Do I need more than one email provider?
Many businesses do. One service hosts staff mailboxes, and a sending provider delivers email from the website and applications. Publish SPF, DKIM and DMARC records that cover both.
What should I check before choosing a sending provider?
Check your expected volume against the limits, whether you can authenticate your own domain, how bounces and complaints are handled, the support options, pricing and whether your data can be exported.