# Multi-Tenant Architecture **Entity class:** Technology, method, or technical system Multi-tenant architecture lets one shared application serve multiple independently configured accounts or organizations while separating their content, identity, settings, and resources. AutoSites uses a filesystem-visible tenancy model: the request host selects a domain-named account folder while common modules, themes, libraries, and publishing machinery are reused. Related: [[wiki/Folder-Native Architecture|Folder-Native Architecture]], [[wiki/Convention over Configuration|Convention over Configuration]], [[projects/AutoSites - Folder-Native Publishing and Distribution|AutoSites]]. ## Relationships <!-- BEGIN HUMANIZED RELATIONSHIPS 2026-09-11 --> This entry's documented connections are expressed in its definition and related-work routes, with provenance retained in the source-linked material. <!-- END HUMANIZED RELATIONSHIPS 2026-09-11 --> ## Related Work in the Corpus <!-- BEGIN HUMANIZED CORPUS ROUTES 2026-09-11 --> - In [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]], **Host-infrastructure crosswalk** provides the narrative context for **Multi-Tenant Architecture**: The remaining cross-links make the boundary conditions explicit. <!-- END HUMANIZED CORPUS ROUTES 2026-09-11 -->