Bring your own provider

Use the provider you already have.

Connect Amazon SES, Postmark, Mailgun, SendGrid, custom SMTP or any of 18 more, and set the order PostFrame tries them in. A failed send moves on to the next provider.

Connecting your own provider is on the Team plan and above, or with any PostFrame add-on.

23 providers, your credentials.

Each connection is yours: its own credentials, its own priority.

Amazon SES

Your own AWS account, in one of six regions.

Postmark

A server token and an optional message stream.

Mailgun

An API key and a sending domain, US or EU.

SendGrid

One API key. Templates and tracking stay in PostFrame.

Custom SMTP

Any server that speaks SMTP, with tracking kept.

18 more

SparkPost, Brevo, Mailjet, MailerSend, Mailtrap, MailPace, SMTP2GO, SocketLabs, Elastic Email, SendPulse, Mandrill, Netcore, Customer.io, Loops, MessageBird, Amazon Pinpoint, Plivo, turboSMTP.

How a send picks a provider.

  1. 1

    Order

    A provider_id on the send comes first. Next comes the managed pool, unless the platform has turned it off. Then your connections by priority, lowest number first.

  2. 2

    Try

    A failed send moves to the next provider on the same request, up to 3 providers per send.

  3. 3

    Skip

    5 failures in 5 minutes open a connection's circuit. It is skipped for 60 seconds, then tried again.

  4. 4

    Managed pool comes next

    PostFrame's managed pool sits right after any provider you name on the send and ahead of your own connections. A send never tries more than 3 providers, so a workspace with 3 connections of its own does not reach the last one while the pool is on.

Which providers can I bring?

Amazon SES, Postmark, Mailgun, SendGrid, SparkPost, Brevo, Mailtrap and more: 23 in all, including any SMTP server.

Do I have to bring a provider at all?

No. PostFrame sends through its managed pool, which runs on Amazon SES. Bring your own only when you want to send from an account, region or reputation you already own.

How does failover decide which provider to use?

A provider_id on the send is tried first. Next comes PostFrame's managed pool, unless the platform has turned it off, then your connections by priority, lowest number first. A failed send moves to the next provider on the same request, trying up to 3 providers per send. After 5 failures in 5 minutes a connection's circuit opens and it is skipped for 60 seconds.

Can I choose the provider for a specific email?

Yes. Pass a provider_id on the send call and that message goes through the named connection first, then the managed pool and your other connections by priority.

Does tracking depend on the provider?

No. PostFrame adds its open pixel and rewrites links before the message reaches any provider, so opens and clicks report the same way on every connection.

Run your business from one place.

Five plans, 25 launch apps, one dashboard. Change tiers any time.

From $0 · Basic $9.95/mo · Upgrade or downgrade any time