Platform scope — pick a tenant host to enter an environment.

SaaS factory ecosystem

Healthy

Template intelligence, stack profiles, feature packs, and inheritance — operational topology without wiring diagrams.

Factory intelligence

Registry-backed posture: what stack you run, which modules apply, and how layers merge before tenant overrides.

Global registry

Stack profiles and versioned feature packs shared across projects.

Healthy

Policy v12 applied

Drift check scheduled nightly.

Inheritance chain

Deterministic merge: platform → stack profile → project → template cut → feature packs → governance.

Pending

Bind a project

Configure API URL and server auth headers.

Modular packs

Enable CRM, logistics, education modules with dependency and stack gates — not flat toggles.

Syncing

Versioned modules

Rollout hints live on each pack row

Factory bindings

Attach a stack profile and enable feature packs in merge order. Each layer may expose metadata.runtime / metadata.branding (and template intelligence.runtime) — merged into effective tenant config before env and tenant overrides.

Set NEXT_PUBLIC_DEFAULT_PROJECT_ID to load the ecosystem overview.

Resolved topology

What ROOTK believes about this project’s factory posture (metadata — no live infra discovery yet).

Set NEXT_PUBLIC_DEFAULT_PROJECT_ID to load the ecosystem overview.