Python & DjangoOne-time
Fieldnote
Schema-per-tenant Django kit for B2B products with strict data isolation
About this starter
Fieldnote uses django-tenants to give every customer their own Postgres schema, which some regulated buyers require. It includes tenant signup with subdomain provisioning, per-tenant users and roles, SSO through SAML, Stripe seat billing, a tenant-aware Celery setup, audit logging, and a platform admin for managing tenants and running migrations across them.
It is opinionated about isolation over convenience, and the docs explain clearly when that trade is worth it. The limitation is operational: migrations run once per tenant, so a schema change with 500 customers takes minutes rather than seconds, and cross-tenant reporting needs a separate analytics pipeline the kit does not include.
Highlights
- 01One Postgres schema per customer
- 02Platform admin runs migrations across tenants
- 03Tenant-aware Celery tasks and audit log