Stop Thinking “User Signup”. Start Thinking “New Tenant”

In multi-tenant SaaS, data isn’t global, it’s tenant-scoped. Data belongs to accounts. Permissions derive from accounts. We made a conscious decision early: treat account creation as the root of the architecture.

In any multi-tenant SaaS product, the moment a new user signs up is more than just adding a row in a “users” table. That user represents a new team, a new data boundary, and a new permission structure.

We made a conscious decision early: treat account creation as the root of the architecture.

Instead of bolting on organizations after user creation or storing org data as just another field on the user we made the account the primary object. Users belong to accounts. Data belongs to accounts. Permissions derive from accounts.

That framing influenced every piece of our backend from schema design to billing logic to RBAC.

Here’s how we built ...