Multi-tenant

One platform, separate workspaces.

PostFrame runs on EternalEngine's workspace model. Each workspace has its own providers, domains, templates, suppression list, API keys and analytics, and Postgres row-level security limits each query to its own rows.

Workspace separation is the same on every plan.

How the separation is enforced.

  • The workspace comes from the authenticated key or session, never from the request body.
  • Each query runs in a database transaction scoped to that workspace, under Postgres row-level security.
  • Bounce and complaint rates, suppression lists and provider circuits are worked out per workspace.
  • The platform operator's views show usage counts and set-up details, never subjects, sender addresses or recipients.
How is workspace isolation enforced?

The workspace ID is set inside each database transaction from the authenticated key or session, never from the request, under Postgres row-level security. A query can only see that workspace's rows.

Does one workspace's bad sending affect another?

Bounce and complaint rates, suppression lists and provider circuits are computed per workspace. Mail sent through the managed pool does share Amazon SES infrastructure with other workspaces.

Can workspaces share a sending domain?

No. A domain is claimed by exactly one workspace platform-wide, and a second workspace that adds it is refused. DKIM tokens are issued per domain.

Who can see across workspaces?

The platform operator, through an admin scope that a workspace cannot grant itself. Those views show usage counts and set-up details, not message content.

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