Skip to main content
Solved

The End of Free MinIO: Explaining Recent Regressions and Missing Features in Ataccama ONE

  • February 24, 2026
  • 4 replies
  • 155 views
O
Data Pioneer L2
Forum|alt.badge.img

Hi everyone,

I’ve personally noticed quite a regression recently—after one of the newer Ataccama updates (even in our Cloud environments!), we lost access to the MinIO GUI admin console and several useful storage management features.

I was wondering what caused this until I came across a report that explains everything: MinIO has officially killed off its free version (Community Edition). On February 12, 2026, their GitHub repository was updated with a final, definitive message: "THIS REPOSITORY IS NO LONGER MAINTAINED".

What exactly happened:

  • For the past 18 months, the creators of MinIO have been systematically stripping features from the free version (which explains the missing GUI we are now experiencing).

  • Public Docker images and binaries have been completely removed, halting the ability to patch security vulnerabilities (CVEs).

  • The only supported option left is their commercial product, AIStor, with a starting price of $96,000 a year.

Since Ataccama uses MinIO under the hood as its built-in S3-compatible storage, these upstream component updates have had a direct knock-on effect on us users. We are now left with an abandoned, unpatchable infrastructure component that has also been stripped of its administrative tools.

I'm posting this as an FYI, but I also want to open up a discussion and hopefully get an official stance from the Ataccama R&D team:

  1. What is the roadmap going forward? Given the abandonment of MinIO CE, are you planning to replace it with another open-source alternative (e.g., SeaweedFS, Garage) in the Ataccama ONE architecture?

  2. What about security? How will current environments (both Cloud and On-Prem) be secured going forward, since free MinIO is no longer receiving security patches?

  3. Is there a workaround? Will there be a built-in tool or workaround within Ataccama to compensate for the loss of the MinIO management console?

Let me know if you guys are also missing the old GUI and how you're handling file management right now.

(Link to the full article: How MinIO went from open source darling to cautionary tale)

Best answer by Jiri Tejkl

Hi Onufry,

Thanks for raising this. I understand the concern, especially around security and operational visibility.

For the time being, MinIO remains an internal backend component of the Ataccama ONE platform. The removal of the MinIO Admin Console/GUI does not prevent MinIO from fulfilling its current role in our architecture (S3-compatible object storage used by the platform), and it does not change how Ataccama ONE interacts with object storage.

On the security side: we don’t rely on “public images/binaries” being available at runtime in customer environments to remain secure. Our platform ships with the required components, and we track and address vulnerabilities as part of our standard maintenance process. MinIO is distributed under an open-source license that provides access to the source code, which means we can apply fixes ourselves if a vulnerability is discovered and an upstream patch is unavailable.

Regarding day-to-day storage administration: the MinIO GUI was convenient, but it was never the only way to manage buckets/objects. You can still manage content via standard S3 tooling (e.g., S3-compatible clients/SDKs) or through Ataccama ONE features where applicable, depending on what you’re trying to achieve (inspection, cleanup, lifecycle management, etc.). A GUI inside MinIO is helpful, but it’s not a requirement for secure operation or functionality.

As for the roadmap: it’s fair to ask what we’ll do if the upstream ecosystem changes significantly. At the moment, MinIO continues to be used as a backend component, and we’ll communicate any changes in supported components or architecture through official release notes and platform documentation.

Best regards,

Jiri Tejkl
Head of Data Quality & Catalog

    4 replies

    KylieF
    Community Manager
    • KylieFCommunity Manager
    • Community Manager
    • February 26, 2026

    Hi ​@onufry !

    This is a very fair set of questions and we appreciate you raising them on the Community. Unfortunately these are a bit complicated to fully answer at this point, but our product team is actively working on resolving the issue raised by MinIO’s recent changes.

    So I wanted to let you know we have seen this and we’re working on a resolution actively. We’ll report in again once our product team can provide clearer answers for all three of your questions. 

    Ataccama Community Manager
      O
      Data Pioneer L2
      Forum|alt.badge.img
      • onufryData Pioneer L2
      • Author
      • Data Pioneer L2
      • February 26, 2026

      Okay, thanks, so I think that this post can be open and I will be waiting for some new answers. :)

      J
      Ataccamer
      • Jiri TejklAtaccamer
      • Ataccamer
      • Answer
      • March 5, 2026

      Hi Onufry,

      Thanks for raising this. I understand the concern, especially around security and operational visibility.

      For the time being, MinIO remains an internal backend component of the Ataccama ONE platform. The removal of the MinIO Admin Console/GUI does not prevent MinIO from fulfilling its current role in our architecture (S3-compatible object storage used by the platform), and it does not change how Ataccama ONE interacts with object storage.

      On the security side: we don’t rely on “public images/binaries” being available at runtime in customer environments to remain secure. Our platform ships with the required components, and we track and address vulnerabilities as part of our standard maintenance process. MinIO is distributed under an open-source license that provides access to the source code, which means we can apply fixes ourselves if a vulnerability is discovered and an upstream patch is unavailable.

      Regarding day-to-day storage administration: the MinIO GUI was convenient, but it was never the only way to manage buckets/objects. You can still manage content via standard S3 tooling (e.g., S3-compatible clients/SDKs) or through Ataccama ONE features where applicable, depending on what you’re trying to achieve (inspection, cleanup, lifecycle management, etc.). A GUI inside MinIO is helpful, but it’s not a requirement for secure operation or functionality.

      As for the roadmap: it’s fair to ask what we’ll do if the upstream ecosystem changes significantly. At the moment, MinIO continues to be used as a backend component, and we’ll communicate any changes in supported components or architecture through official release notes and platform documentation.

      Best regards,

      Jiri Tejkl
      Head of Data Quality & Catalog

      O
      Data Pioneer L2
      Forum|alt.badge.img
      • onufryData Pioneer L2
      • Author
      • Data Pioneer L2
      • March 7, 2026

       

      Hi Onufry,

      Thanks for raising this. I understand the concern, especially around security and operational visibility.

      For the time being, MinIO remains an internal backend component of the Ataccama ONE platform. The removal of the MinIO Admin Console/GUI does not prevent MinIO from fulfilling its current role in our architecture (S3-compatible object storage used by the platform), and it does not change how Ataccama ONE interacts with object storage.

      On the security side: we don’t rely on “public images/binaries” being available at runtime in customer environments to remain secure. Our platform ships with the required components, and we track and address vulnerabilities as part of our standard maintenance process. MinIO is distributed under an open-source license that provides access to the source code, which means we can apply fixes ourselves if a vulnerability is discovered and an upstream patch is unavailable.

      Regarding day-to-day storage administration: the MinIO GUI was convenient, but it was never the only way to manage buckets/objects. You can still manage content via standard S3 tooling (e.g., S3-compatible clients/SDKs) or through Ataccama ONE features where applicable, depending on what you’re trying to achieve (inspection, cleanup, lifecycle management, etc.). A GUI inside MinIO is helpful, but it’s not a requirement for secure operation or functionality.

      As for the roadmap: it’s fair to ask what we’ll do if the upstream ecosystem changes significantly. At the moment, MinIO continues to be used as a backend component, and we’ll communicate any changes in supported components or architecture through official release notes and platform documentation.

      Best regards,

      Jiri Tejkl
      Head of Data Quality & Catalog

      Thanks for the answer, it is all i wanted to hear :)

      Community Terms of Use & ConditionsCookie settingsAccessibility statement