Platform Administration & Deployment
How FaburAI is deployed, operated, and administered across SaaS, private cloud, and air-gapped environments.
- AI-authored curated content. Every claim is anchored to a derived fact, but the wording, emphasis, and pedagogy are unreviewed product judgment.
FaburAI splits into two planes, and the split is the reason the same product runs as SaaS and inside an air-gapped network.
Control Plane
Central management: tenants, cluster registration, provisioning, fleet health, and deployment coordination. In SaaS this is operated by FaburAI. In a private or on-premises install you run it yourself.
Data Plane
Tenant-local, and where the product actually lives — catalog, policy authoring and evaluation, enforcement, telemetry, AI Graph, and Cockpit. Governed traffic and discovered inventory stay in the Data Plane.
This is what makes air-gapped deployment possible rather than merely claimed: the Data Plane does not need to reach the Control Plane to evaluate policy. It holds its own catalog, its own policies, and its own decision history.
Deployment models
SaaS, PaaS, private cloud, on-premises, and air-gapped are the supported operating models. They differ in who runs the Control Plane and how images and documentation reach the cluster — not in how governance behaves.
Provenance
This page is derived from the following implementation sources.
docs/corpus/narrative/concept-platform-administration.md
Last verified at commit b61836e.