MSK Core Concepts (6)
The starting point for understanding Multi-SaaS Kit (MSK). Six core concepts define how you build it (0) → what it operates (1) → who operates it (2) → in which mode (3) → what fills it (4) → how it extends (5). Each concept's details are in the linked pages below.
MSK is not a single app but a kit that mass-produces multiple SaaS and maintains them with one hand. Its identity is captured in six concepts.
Concept 0 — Kit Meta-structure (how you build)
Copy one template to create a project (make create), and share Core·Plugin so a single fix propagates to all projects.
⭐ Top directive — Backport-friendliness: Whatever layer you implement in — Core, Plugin, template, or an individual project — every implementation must be structured so the change cleanly propagates to all projects (or does not break incoming propagation). This is what lets MSK maintain many SaaS with one hand.
→ Project Structure · Monorepo Approach · Development Philosophy
Concept 1 — Structure (what it operates)
| Axis | Summary | Detail |
|---|---|---|
| Multi-SaaS + independent sites | One project operates multiple SaaS and sites | Project Structure |
| Permission hierarchy | Platform > SaaS > Tenant > Org > Member (fixed backbone + flexible tree) | Permission Hierarchy |
| Site model | Independent + Mirror (2 types) + Primary (role) — ADR-090 | Site Operating Model |
| Data isolation | A DB physical boundary separate from permissions (RLS) — data won't leak even if a permission bug occurs | Data Isolation |
Concept 2 — Admin·Permission·Audit (who operates)
The main admin is optional (a parent can manage directly / impersonate). Sub-admins see only the features they are granted (fail-closed). All admin activity is tracked in the audit log; audit viewing is available only on an independent site or Platform.
→ Permission System · Multi-tenancy
Concept 3 — Multi-SaaS Operation·Migration (in which mode)
Integrated (1 project, N SaaS) vs Isolated (1:1) operating modes. You can migrate between them based on scale, compliance, or team separation (official default = 1:1 isolated).
Concept 4 — Site Management Details (what fills it)
An independent site manages company info · terms/policies · signup policy · ads·analytics · built-in board, and more. Individual features keep expanding, but the storage (settings namespace) and exposure (site-management gate) frames stay consistent.
Concept 5 — Plugin System (how it extends)
Functionality is assembled selectively as Plugins on top of the Core. Plugins are designed to be domain-neutral (not tied to a specific SaaS) and license-safe (default distribution ships only permissive licenses).
Hierarchy: Concept 0 (meta) is the foundation, 1·2 the operating structure, 3·4·5 the operation·content·extension. Every detailed feature and ADR·architecture document implements or deepens these six concepts.