bernardopires/django-tenant-schemas

Health v2 · maintenance only

Adoption not part of the score

1520 stars · 426 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A Django app that provides multi-tenancy using PostgreSQL schemas, letting a single project instance serve many tenants with shared and tenant-specific data. Tenants are identified by hostname and routed to their own schema via middleware.

Use cases

• build a SaaS where each customer gets isolated data on one Django instance
• serve multiple tenants from a single database using separate PostgreSQL schemas
• route requests to tenant-specific schemas based on subdomain
• share some data across tenants while keeping tenant-specific tables separate
• avoid running one copy of the app per customer

When to choose

• you use Django with PostgreSQL and want schema-based multitenancy
• you want minimal code changes to add tenant isolation
• you prefer one database with per-tenant schemas over one database per tenant

When to avoid

• you don't use PostgreSQL
• you need the shared-schema approach with a tenant foreign key
• your project is not Django

Facets

library · maturity maintenance

middleware routing database orm web-development backend databases python django postgresql-schemas multitenancy saas host-based-routing multi-tenancy web-server

Member repositories

For agents

markdown · JSON · MCP: product_card(name="bernardopires/django-tenant-schemas")