# MinIO (/docs/runtime/components/minio)



Component Category [#component-category]

Data and storage / object storage

Component Description [#component-description]

MinIO is an S3-compatible object storage platform used to store artifacts, files, and binary assets. In the platform it acts as the main object storage layer for data that does not belong in a relational database.

Why It Is Used [#why-it-is-used]

In BullSequana AI Runtime, MinIO provides object storage for platform artifacts and operational data that need scalable, API-driven storage outside of a relational database. It is useful for model artifacts, uploaded documents, event-driven file workflows, and other storage-heavy AI and data operations that benefit from an S3-compatible interface.

Learn More [#learn-more]

* [minio/minio on GitHub](https://github.com/minio/minio)

Practical Notes [#practical-notes]

The platform is rolling out [Rook-Ceph](/docs/runtime/components/rook-ceph) as the long-term S3-compatible object storage substrate. MinIO and Rook-Ceph run side by side during the migration; new workloads should target Rook-Ceph where possible.

Interacts With [#interacts-with]

* `Keycloak`, which MinIO waits on during startup as part of the identity setup.
* `NGINX`, `External DNS`, and `cert-manager`, to expose and secure the API and console endpoints.
* `Argo Events`, `Argo Workflows`, `Tempo`, and `KubeAI`, which receive dedicated MinIO users, buckets, or credentials in the platform manifests.
* Higher-layer services such as `MLflow`, RAG pipelines, `Airbyte`, and `Milvus`, which also consume MinIO storage.