> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# turboSMTP Alternatives: Compare Email Providers Side by Side

> See how turboSMTP compares to SendGrid, Mailgun, and other email providers on regional endpoints, SMTP settings, API formats, and migration requirements.

turboSMTP offers an SMTP relay and a JSON email API with Global and EU sending endpoints. Compare the request formats, credentials, regional setup, and plan requirements before migrating.

## Evaluate turboSMTP

> [card] [Global and EU Endpoints](/docs/api-reference/base-urls.md)
>
> Use `api.eu.turbo-smtp.com` for API sending or `pro.eu.turbo-smtp.com` for SMTP in the EU region. Review processing terms for your requirements.

> [card] [Plan Features](https://serversmtp.com/pricing/)
>
> Check sending allowances, analytics retention, webhooks, and support channels for your plan.

> [card] [Support](https://serversmtp.com/contact-us/)
>
> Chat and ticket support are listed for Free and Basic. Pro and Enterprise also list phone support.

> [card] [SMTP and JSON API](/docs/sending/email-api.md)
>
> Send with a Consumer Key and Consumer Secret through an SMTP client or an HTTPS request.

## Comparisons

> [card] [turboSMTP vs SendGrid](/docs/compare/turbosmtp-vs-sendgrid.md)
>
> Compare regional endpoints, API payloads, and SMTP credentials.

> [card] [turboSMTP vs Mailgun](/docs/compare/turbosmtp-vs-mailgun.md)
>
> Compare regional setup, JSON and form data, and message limits.

## Migration guides

> [card] [Migrate from SendGrid](/docs/migrate/from-sendgrid.md)
>
> Map SMTP settings and v3 Mail Send requests to turboSMTP.

> [card] [Migrate from Mailgun](/docs/migrate/from-mailgun.md)
>
> Map SMTP settings and form-data requests to turboSMTP.

## Plan your migration

**1. Check your plan and credentials**

Review [current pricing](https://serversmtp.com/pricing/) and create [API keys](/docs/get-started/api-keys.md) with the sending permissions you need.

**2. Authenticate your domain**

Add turboSMTP to your existing single SPF record and publish its DKIM record. Keep your current provider authorized during cutover. See [SPF, DKIM, and DMARC](/docs/deliverability/spf-dkim-dmarc.md).

**3. Move settings and suppression data**

Update SMTP or API configuration, import suppressions, and adapt webhook handling. Verify regional and feature availability before moving traffic.

**4. Ramp up and cut over**

Move a share of traffic first and inspect [Analytics](/docs/analytics/statistics-dashboard.md). Retire the old provider after its queue has drained.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.