Skip to content
New 1.0 Free Docker Image + 7 Industry Packages (.eap) included. Render.com Deploy Guide → ⚡ Try Live Demo ☕ Buy me a coffee

Multi-Tenant Workspaces & Model Management

Large enterprises and consulting firms frequently manage multiple business subsidiaries, regional units, or client engagements requiring strict architectural segregation.

EasyEA’s Admin Hub provides native Multi-Workspace and Multi-Model capabilities ensuring complete graph isolation alongside controlled resource governance.


1. The Workspace Isolation Model

A Workspace is a dedicated logical boundary encapsulating:

  • Independent element and relationship catalogs.
  • Dedicated schemas and business views.
  • Dedicated Architecture Decision Records (ADRs).
  • Local .eap package installations.
graph TD
Root[Enterprise EasyEA Instance] --> WS1[Workspace: Corporate Banking]
Root --> WS2[Workspace: Retail & Wealth Management]
Root --> WS3[Workspace: Cloud Infrastructure Transformation]
WS1 --> M1[Independent Catalogs & Schemas]
WS2 --> M2[Independent Catalogs & Schemas]
WS3 --> M3[Independent Catalogs & Schemas]

System administrators configure workspaces from Admin Hub ➔ Workspace Management (models.py):

  • Unique Name & Code: Slug used in API URLs and routing.
  • Scope & Mission: Narrative describing the governance scope.
  • Default Workspace: Target landing space for newly provisioned users.

2. As-Is, To-Be, and Sandbox Models

Within each workspace, teams maintain parallel baseline states:

  • As-Is Baseline (Current Production): Mirroring the operational reality of deployed systems.
  • To-Be Target (Strategic Horizon): Documenting the 2-5 year target state.
  • Sandbox / Initiative Models: Isolated scratchpads allowing project architects to iterate without polluting golden production data before formal review.

3. Export, Cloning, and Lifecycle Operations

  • Full Workspace Export: Ingest or export complete environments including elements, schemas, SaC files, and APM metrics.
  • 1-Click Model Cloning: Duplicate an existing model to instantiate a baseline for new transformation programs.
  • Guarded Purge: Controlled deletion of obsolete scratch models requiring administrative verification.