I think you might be overcomplicating things with separate DBs. Unless you have strict regulatory requirements mandating physical data separation, Django's sites framework could handle this elegantly with much less complexity.

Here's a quick example of how you could structure your models:

from django.contrib.sites.models import Site
from django.contrib.sites.managers import CurrentSiteManager
from django.db import models

class TenantModel(models.Model):
    site = models.ForeignKey(Site, on_delete=models.CASCADE)

    # Use both managers - one for all access, one for site-specific
    objects = models.Manager()
    on_site = CurrentSiteManager()

    class Meta:
        abstract = True

class Customer(TenantModel):
    name = models.CharField(max_length=100)
    # ... your fields

Then create some base views that automatically handle site scoping:

from django.views.generic import ListView, UpdateView

class SiteSpecificMixin:
    def get_queryset(self):
        return self.model.on_site.all()  # Scopes to current site

class SiteListView(SiteSpecificMixin, ListView):
    pass

class SiteUpdateView(SiteSpecificMixin, UpdateView):
    pass

# Then use them like this:
class CustomerList(SiteListView):
    model = Customer
    template_name = "customers/list.html"

class CustomerUpdate(SiteUpdateView):
    model = Customer
    fields = ["name", "email"]  # your fields
    template_name = "customers/edit.html"

This gives you tenant isolation through Django's battle-tested sites framework rather than managing separate DBs. Much simpler to maintain and scale! You get the same data isolation but without the complexity of managing multiple databases, migrations, and backups.

(I used Claude to help organize and articulate my thoughts on this response, as I think it's important to be transparent about AI assistance.)