I can confirm that having the data in the same database is the prefered way to implement multi-tenancy. If separate databases are an unavoidable requirement, things can get a bit nightmarish, but only the kind where you’re late for an exam, not the kind that makes you wake up screaming. Things only get really tricky if you share the same model across all tenants and you require separate databases and you also want an API on top of that. We had that problem and came to a somewhat undjangonic solution, as described here: Struggling with application structure for multi-tenant system