C3 AI Documentation Home

Artifact Hub and Package Store

Artifact Hub is the C3 Agentic AI Platform's central repository for versioned packages. In the context of Package Store, Artifact Hub serves as the distribution mechanism that stores packages as Pkg.Store.Zip archives. This guide explains how Artifact Hub fits into the package storage system.

Artifact Hub in the package lifecycle

Artifact Hub bridges development and production in the package lifecycle:

graph LR A[Development<br/>Pkg.Store.Db] --> B[Build & Publish<br/>ZIP Artifact] B --> C[Artifact Hub<br/>Repository] C --> D[Download as<br/>Pkg.Store.Zip] D --> E[Production<br/>Read-only]
  1. Development: Packages are editable in Pkg.Store.Db.
  2. Publishing: Packages are built as ZIP archives and uploaded to Artifact Hub.
  3. Distribution: Other packages declare these packages as dependencies.
  4. Consumption: Package Store downloads ZIPs and serves them through Pkg.Store.Zip.

How Artifact Hub uses Pkg.Store.Zip

When you declare a package as a dependency, the platform automatically:

  1. Queries Artifact Hub for the package and version.
  2. Downloads the ZIP artifact if not already cached.
  3. Configures Pkg.Store.Zip to serve the package.
  4. Makes the package available as a read-only dependency.

This integration ensures that production deployments use immutable, versioned packages. Since Pkg.Store.Zip is read-only, packages downloaded from Artifact Hub cannot be modified, ensuring consistency across all environments.

Publish to Artifact Hub

Publishing makes your package available for others to use as a dependency. The platform packages your code as a ZIP archive and uploads it to Artifact Hub with version metadata.

For step-by-step publishing instructions, see:

Browse Artifact Hub

Artifact Hub provides a UI for discovering available packages. In C3 AI Studio:

  1. Select Releases from the navigation panel.
  2. Select Artifacts in the sidebar.

The Artifacts page shows:

  • Library: Latest applications, plug-ins, and quickstart packages.
  • Versions: All artifacts with filtering and statistics.

Moving artifacts between clusters

You may need to move artifacts between clusters (for example, from development to QA). Artifact Hub provides workflows for:

  1. Downloading artifacts as ZIP files.
  2. Transferring to the target cluster.
  3. Uploading and registering in the target cluster.

For complete instructions, see Registering Artifacts to External Clusters.

See also

Artifact Hub documentation:

Package Store documentation:

Was this page helpful?