Tutorial series

Multi-tenant SaaS with Stripe Connect, end to end

Build a platform that many separate companies use without ever seeing each other's data, and that takes payments on their behalf without the money passing through you. One worked example, from an empty schema to a system you can put a support team behind.

10 chapters · 1 sections

Start with chapter 1 →

The example we build

Meridian, a platform where independent software vendors sell seat-based licences to their own business customers. Each vendor is a tenant with its own catalogue, customers, pricing and payouts; Meridian charges a platform fee on every transaction and never holds a vendor's money.

1. Foundations

What multi-tenancy actually commits you to, the three isolation models, and which of these decisions you cannot cheaply reverse.

  1. 01What multi-tenancy actually commits you to6 min read
  2. 02The three isolation models6 min read
  3. 03Choosing an isolation model7 min read
  4. 04Whether you need multi-tenancy at all7 min read
  5. 05The platform's relationship to money6 min read
  6. 06What you are building7 min read
  7. 07The smallest version worth shipping6 min read
  8. 08The data model on day one7 min read
  9. 09The decisions that are expensive to reverse7 min read
  10. 10How this series is verified7 min read