Multi-tenant

Isolated providers

Each workspace connects its own providers with its own credentials and priority order. A provider failing for one workspace opens a circuit for that connection only.

Per-workspace provider setup

  • Your own credentials

    Each workspace stores its own SES, Postmark, Mailgun, SendGrid or SMTP credentials, 23 provider types in all. They are never shared with another workspace.

  • Your own order

    Priority and failover are set per workspace. One workspace's outage does not change another's order.

  • A circuit per connection

    Circuit breakers are keyed by connection, so a failing account elsewhere never opens a circuit on yours.

  • The managed pool is shared

    PostFrame's managed pool is shared infrastructure by design. It is tried right after any provider you name on the send, ahead of the connections you set up.

What is per workspace

Credentials
Entered by the workspace, used only for its own sends.
Priority
The order your connections are tried in.
Health check
An on-demand check against the provider's API, per connection.
Circuit breaker
One per connection. It is skipped for a short time after repeated failures.
Questions

PostFrame, answered

Which providers can a workspace connect?

Amazon SES, Postmark, Mailgun, SendGrid, SparkPost, Brevo, Mailtrap and more: 23 in all, including any SMTP server. Every connection is private to the workspace that created it.

If another workspace's provider fails, does it affect mine?

No. Circuit breakers are keyed per provider connection, and each workspace has its own connections, so a failing account elsewhere never opens a circuit on yours.

Is any sending infrastructure shared between workspaces?

The managed pool is. It runs on Amazon SES and every workspace can use it. Your own provider connections are yours alone.

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