STRATEGIC TECHNOLOGY PARTNER · MINIO AISTOR
Use MinIO AIStor to support object and AI data workloads with performance, governance and open-data architecture in mind. Bassirah designs the storage layer as part of the complete platform.
MinIO is one of Bassirah’s Strategic Technology Partners for MinIO AIStor. Our relationship is subject to the applicable MinIO program and agreement. Implementation scope, resell rights and support entitlements are confirmed in each customer engagement. AIStor capabilities are matched to the customer’s license and deployed release.
WHY MINIO AISTOR
Establish scalable S3-compatible access and, where product and architecture requirements align, an Apache Iceberg-based lakehouse foundation.
AI and analytics platforms are only as dependable as the storage beneath them. Training datasets, model artifacts, lakehouse tables, logs and long-term analytical history all need durable, secure and well-governed storage that many engines can reach through a common interface.
MinIO AIStor is MinIO’s commercial object storage platform for AI and data workloads, built around S3-compatible access. Where the selected release and table interface support it, AIStor can also provide native Apache Iceberg table services for open lakehouse designs. Bassirah designs AIStor as part of the complete platform: capacity and network, data protection, access policies, and the query engines, catalogs and pipelines that use it.
WHAT BASSIRAH DELIVERS
Our AIStor engagements treat storage as an engineered platform, not a commodity purchase.
USE CASES
Solution concepts. Each design is validated against your workload.
Store and serve datasets, checkpoints, feature files and model artifacts for AI pipelines running on your infrastructure.
Hold raw files and curated Apache Iceberg tables that Trino OSS or Starburst can query, where integrations are validated.
Retain analytical history, logs and telemetry durably, and share governed datasets across teams and engines.
ARCHITECTURE DISCIPLINE
Object storage outcomes depend on infrastructure and policy design. We document each decision and test it before production.
| Design area | What we decide | How we validate |
|---|---|---|
| Capacity and layout | Nodes, drives, data protection settings and expansion approach | Capacity model at target retention and growth |
| Network and throughput | Network bandwidth, client concurrency and workload separation | Throughput test with representative object sizes |
| Access and identity | Identity provider integration, bucket policies, service accounts and tenancy | Access tests for each role |
| Encryption and keys | Encryption at rest and in transit, key management integration | Key rotation and recovery rehearsal |
| Lifecycle and retention | Versioning, lifecycle rules, immutability where required | Policy tests on sample datasets |
| Resilience | Replication between sites, failure-domain design, recovery objectives | Site or node failure drill with agreed RPO and RTO |
OPEN DATA ARCHITECTURE
Many lakehouse designs combine raw object storage with Apache Iceberg tables, a catalog, a SQL engine, transformation tooling and a metadata platform. AIStor can serve as the object and, where supported by the selected release, native Iceberg table foundation for that design. Bassirah validates every connection: the catalog interface, authentication, engine version and feature behavior.
Iceberg table services, catalog interfaces and engine interoperability vary by AIStor release and license. Bassirah confirms compatibility in a project-specific architecture before relying on it.
We will validate AIStor, catalog and query-engine compatibility for your target design.
WORKS WELL WITH
SQL over supported lakehouse tables, through the partner-led or independent OSS route.
Transformations and data tests over lakehouse tables, where adapters support the engine.
SEE IT IN CONTEXT
AIStor for objects and, where supported, native Iceberg tables, with Trino OSS or Starburst, dbt Core / dbt OSS and DataHub Core.
Durable history: raw files and curated Iceberg tables for network data.
S3-compatible storage for Langfuse event payloads and multimodal assets.
HOW WE ENGAGE
MinIO AIStor is MinIO’s commercial object storage platform for AI and data workloads, with S3-compatible access. Depending on the release and license, it also offers additional capabilities such as native Apache Iceberg table services. Bassirah matches capabilities to your entitlement and deployed release.
Trino OSS and Starburst provide connectors for S3-compatible storage and Apache Iceberg tables. The exact AIStor configuration, catalog, network setup and connector compatibility must be validated in the target architecture.
No. Object storage holds files, objects and table data for engines to read. Transactional workloads still need an operational database, and low-latency analytical serving may need an engine such as ClickHouse. AIStor provides the durable foundation beneath them.
AIStor is designed to run on infrastructure you control. Isolated deployment patterns are designed and validated per engagement, including dependencies, license activation requirements, upgrade paths and telemetry egress.
We design encryption at rest and in transit with your key management system, least-privilege access policies, versioning and immutability where required, replication between sites and tested recovery procedures.
Features depend on the AIStor release you deploy and the license you purchase. We confirm entitlement during design and do not plan around capabilities that are not included.
Licensing & Naming
Community MinIO is archived and no longer maintained. What changed, the AIStor editions, the one-way upgrade procedure, and how to choose a path forward.
MinIOMinIO AIStor
Read article : MinIO Community Edition Archived: Planning the Move to AIStor or Elsewhere→
Tell us about your data, workloads and resilience requirements. We will help you design and operate the right AIStor architecture.
