Every email API will sell you sub-tenancy. Mailgun calls it subaccounts — $90/month, Scale plan minimum.
What that price actually tells you: multi-tenancy was built on top, not into the data model. Things bolted on afterwards are expensive to run, so they get sold to the customers who can absorb it.
But if you send email on behalf of your customers, you inherit their behaviour. One tenant imports a dirty list, your whole domain eats the complaint, and every other customer's password resets start landing in spam.
That isn't an enterprise problem. It's your first problem — day one, ten customers, before you have any revenue to justify a $90 line item.
So the tier structure gets it exactly backwards: the people who most need a tenant boundary are the ones priced out of having one until after it's already gone wrong.
I built Rootmail with the boundary in the schema. Not as a plan. Closed beta at https://rootmail.io/beta — 8 seats, free, for people who'll tell me where it breaks.
If you run a platform that sends as your customers — when did sub-tenancy stop being optional for you?
Follow along if you build platforms that send as their customers. Tomorrow: "A silent failure is not best-effort," the first entry in a weekly commit log.
Top comments (0)