diff --git a/docs/.vitepress/theme/components/Home.vue b/docs/.vitepress/theme/components/Home.vue index a3603a77..1101bd54 100644 --- a/docs/.vitepress/theme/components/Home.vue +++ b/docs/.vitepress/theme/components/Home.vue @@ -57,9 +57,9 @@ onUnmounted(() => {
The only model registry that works anywhere containers run — from public cloud to the most locked‑down air‑gapped environments.
+The only AI registry that packages and governs models, agent skills, and MCP servers as OCI artifacts — from public cloud to the most locked‑down air-gapped environments.
Enterprise AI teams face three problems with traditional model registries: security gaps, vendor lock‑in, and deployment friction.
KitOps solves them all.
Unlike proprietary registries that trap you in closed ecosystems, KitOps stores models, datasets, code, and configs as OCI artifacts in your container registries — Docker Hub, ECR, GCR, Harbor, Artifactory, and beyond.
+Enterprise AI is no longer just models. Teams are deploying agents, MCP servers, skills, and policies — all of which need the same versioning, security, and governance as container images. KitOps packages them all as standard OCI artifacts in the registries you already run.
+From proprietary repos that trap your AI artifacts in closed ecosystems to fragile ad‑hoc approaches that bypass your security toolchain — KitOps brings models, agent skills, MCP servers, datasets, and configuration under one governed workflow.
With 100,000+ downloads and 18+ months in production, KitOps is trusted by organizations that can’t compromise on security, compliance, or uptime.
Bundle models, datasets, code, agent skills, MCP servers, guardrail configs, and policies into a single versioned OCI artifact. No more scattered repos, zip files, or git submodules for your AI components.
Sign with Cosign. Scan before promotion. Generate SBOMs. Every component is SHA‑256 hashed and tamper‑evident — the same security posture you apply to container images, now applied to your agents and MCP servers.
Store ModelKits in Docker Hub, ECR, GCR, Harbor, Artifactory, or Jozu Hub. No proprietary registry required. Your existing access controls, scanning, and compliance workflows just work.
Every model, agent skill, and MCP server is a versioned, immutable OCI artifact. What you deployed is exactly what was tested.
SHA-256 digests for every component. Tamper detection works the same way it does for your container images — because it is the same infrastructure.
Package Your First Model
+Package Your First Agent
+Bundle a model, MCP server config, and agent skills into a signed ModelKit in under 5 minutes.
kit pack . -t myregistry.com/my-model:latest
Enterprise support for ModelKits and the Kit CLI is available from Jozu.
+ +Yes. KitOps packages any AI/ML component — models, datasets, code, configuration, MCP server definitions, agent skills, guardrail configs, and policies — as a single versioned OCI artifact. MCP servers and agent skills get the same cryptographic signing, scanning, and governance as your models.
+OCI artifacts give you immutable versioning, cryptographic signatures, supply chain scanning, and content-addressable storage — the same infrastructure you already use for container images. Git repos work for source code, but production AI deployments need the tamper-evidence, provenance, and policy gating that OCI provides.
+KitOps is the reference implementation of ModelPack, the CNCF specification for vendor-neutral AI/ML packaging. KitOps also supports its own ModelKit format with broader artifact coverage including MCP servers, agent skills, and policies.
+