The Multi-Tenant Containment Challenge
Multi-tenant architectures require rigorous containment boundaries. Under no circumstances should any tenant be capable of querying, leaking, or modifying database records belonging to another tenant. In standard frameworks, developers are forced to write manual database filters (e.g. site_id = ?) in every controller query to enforce this isolation.
Automating Isolation via IsModel Active-Record
To enforce absolute data separation natively, Zero CMS database models utilize the static IsModel Active-Record trait. This trait automatically scopes all database operations by injecting active tenant scoping filters (site_id = ?) behind the scenes on runtime, preventing data cross-pollution and mitigating unauthorized field injection vectors completely.
By automating multi-tenant scoping via `IsModel`, Zero CMS achieves complete security inside cascading view templates. If a custom theme view is missed or misconfigured, there is no risk of leaking cross-tenant data because the database query itself is fully sandboxed on runtime. Whether managing store variants inside the Luxe Shop or reading published articles inside the blog engine, Zero CMS isolates database entries with absolute, zero-trust precision, providing an enterprise-grade multi-tenant containment firewall on bare metal.