Get started
Get started with Smart Kubaba documentation
Access product guides, verified capabilities, installation guidance, and procedures from one versioned documentation tree.
What does this documentation cover?
Smart Kubaba combines artifact management, software supply-chain visibility, and policy decisions at the repository boundary in one self-hosted platform.
- Product-area responsibilities and the data flow between them
- Capabilities verified in the source project and explicit boundaries
- Deployment components and organizational responsibilities
- Procedures for workflows backed by evidence
How should you proceed?
Read the core concepts and product areas first, then continue to the capability, installation, and procedure pages relevant to your evaluation.
- Platform team: review installation architecture, data layers, identity and network design, and high-availability boundaries.
- Repository administrator: follow format coverage, repository workflows, cleanup, and storage procedures.
- Security team: validate OSV and SBOM flows, policy decisions, risk acceptance, and audit evidence.
- Acceptance team: begin with the evaluation guide and evidence every result in the acceptance checklist.
Read the content statuses
Each page status explains how to use the content; it is not a product release or commercial-entitlement marker.
- Verified in source: the published scope has implementation or acceptance evidence in the audited source tree.
- Evaluation guidance: planning steps that require target-environment decisions and do not constitute a product promise.
- Awaiting validation: do not use as production instruction until repeatable commands, acceptance results, or operational evidence are complete.
Version and evidence boundary
The Latest option represents the source-evidence snapshot shown on the page, not a public product release number. Before a production decision, reconcile that snapshot with the target image, chart, database schema, and acceptance date.