All projects
web
A multi-tenant SaaS skeleton
One codebase, many organisations, and no way for one to read another's data.
Why it matters
Almost every startup job is B2B SaaS. Having already thought about tenant isolation puts you ahead of candidates who have only built single-user apps.
What you build
- Organisations with members and roles
- Data isolation enforced at the query layer
- An invitation flow
- A test that proves cross-tenant reads fail
If you want more
- Add per-tenant subdomains
- Add usage-based billing hooks
Build it
- Build the invite and accept flow
Material for the whole build
Shows you can build the authorisation model a business product needs, and that you test the negative case.
Get a plan built around projects like this