yotta_bot

Yotta Blob Storage

Durable, tenant-isolated object storage for the inputs, outputs, exports, and intermediate state agents produce

Book a demo →
What it is

What is Yotta Blob Storage?

Yotta Blob Storage is the object-storage product for the control plane. The code describes an S3-shaped bucket and object catalog backed by MinIO in the first implementation, with folders treated as key prefixes. The product gives agents and workflows a governed place for raw data, generated files, intermediate state, and exports without confusing that data with versioned build artifacts.

Capabilities

What Blob Storage gives your team

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

  1. 01Bucket catalogCreate and track account-scoped buckets with ownership and metadata
  2. 02Object indexList and search objects by key, prefix, size, content type, and modified time
  3. 03Prefix browsingExpose folder-like navigation while preserving S3-style object semantics
  4. 04Agent outputsStore generated files, datasets, exports, and intermediate workflow state
  5. 05Provider bridgeStart with MinIO-backed storage and keep room for cloud object providers
  6. 06Access governanceApply Yotta identity, audit, and policy controls to object access
Comparison

Blob Storage compared with similar products

Object stores are already mature. Yotta Blob Storage is not trying to out-S3 S3; it gives agents a governed, product-native object surface that can run in Yotta, self-hosted environments, or through provider integrations.

Capability Blob Storage Amazon S3 Google Cloud Storage Azure Blob Storage MinIO
Primary scope Agent and workflow object storage General-purpose object storage Managed unstructured data storage Azure object storage S3-compatible object store
Storage model Buckets, objects, prefixes, and metadata catalog Buckets, objects, prefixes Buckets and objects Containers and blobs Buckets and objects
Agent outputs Native home for generated content and intermediate state Application-defined Application-defined Application-defined Application-defined
Provider posture Yotta-native with MinIO-backed first implementation AWS cloud Google Cloud Azure cloud Self-hosted or cloud
Governance context Identity, policy, audit, logs, and workflows together AWS IAM and S3 controls Google IAM and storage controls Microsoft Entra/RBAC controls MinIO IAM and policies
Registry separation Separate from Artifact Registry by design Separate service families Separate Artifact Registry product Separate ACR/Azure Artifacts products Object storage only
  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 →