yotta_bot

Yotta Artifact Registry

Store, version, and serve the images, packages, prompts, model assets, and bundles your agents depend on

Book a demo →
What it is

What is Yotta Artifact Registry?

Yotta Artifact Registry is the registry product for agent and workflow dependencies. The code models local repositories hosted by Yotta, remote repositories proxied from upstreams, and virtual repositories that aggregate both. The planned product extends that catalog toward containers, packages, model weights, sealed prompts, and agent bundles with Yotta identity, policy, and audit attached.

Capabilities

What Artifact Registry gives your team

These capabilities are grounded in the current repo surfaces and the planned product updates for the yotta_bot control plane

  1. 01Local repositoriesHost artifacts in Yotta-managed repositories for account-scoped use
  2. 02Remote proxiesProxy and cache upstream sources such as OCI registries or model repositories
  3. 03Virtual repositoriesExpose one logical repository that aggregates local and remote sources
  4. 04Agent bundlesOrganize deployable agent bundles, prompts, tools, and runtime assets
  5. 05Governed consumptionApply identity, permissions, and audit trails to artifact access
  6. 06Supply-chain contextConnect artifacts to agents, workflows, runs, and operational telemetry
Comparison

Artifact Registry compared with similar products

Traditional registries are optimized for packages and containers. Yotta Artifact Registry follows the local, remote, and virtual repository pattern while making agent bundles, prompts, model assets, and workflow dependencies part of the same governed control plane.

Capability Artifact Registry JFrog Artifactory Google Artifact Registry Amazon ECR GitHub Packages
Repository model Local, remote, and virtual repositories Universal repository manager Multiple package formats Container registry Package registries tied to GitHub
Agent artifacts Agent bundles, prompts, model assets, and runtimes AI and ML artifact support Container and language packages Container images and artifacts Packages and containers
Upstream proxying Remote proxy catalog planned from repo model Core strength Remote repositories supported Pull-through cache patterns Limited by package ecosystem
Virtual aggregation Virtual repos for one client endpoint Core strength Virtual repositories supported Not primary pattern Not primary pattern
Control-plane context Connected to agents, workflows, identity, logs, and alerts Supply-chain platform context Google Cloud context AWS container context GitHub repository context
Deployment posture Cloud or self-hosted control plane SaaS or self-managed Google Cloud AWS cloud GitHub cloud/enterprise
  1. 1Yotta capability descriptions combine current code surfaces with planned product updates in the repo.
  2. 2Similar-product summaries are based on public vendor positioning and documentation reviewed in June 2026.

Try it for yourself

Schedule a demo with someone on our team. We’ll explore your use cases, answer your questions, and find the deployment model that best fits your needs.

Book a demo →