The tenancy model, and what isolation actually means here.
Updated
Dash4Devs runs two tenant systems side by side:
| Organization | Platform | |
|---|---|---|
| What it is | A storefront business | A white-label vertical |
| Its people | Shoppers / customers of the store | Platform customers + platform operators (staff) |
| Key namespace |
pk_ / sk_ |
dfd-platform-* and dfd-site-* |
| Data model | Products, orders, carts… | Record types you declare + module data |
| Created by | Self-serve | Dash4Devs superadmin only — no self-serve path, by design |
The namespaces are deliberately disjoint so a leaked credential is instantly identifiable, and a platform key can never be mistaken for (or used as) a storefront key.
status = suspended is the kill switch: every key stops working on its next request, and the data stays put. That makes offboarding reversible and disputes auditable — nothing about a paying-then-leaving-then-returning platform involves data loss.